tegra: trimslice: usb2sata: (optionally) limit SCSI request size to 16K in order to prevent
	the device from hanging when processing scatter-gather list.

	Currently the only usb2sata / SSD pair that is known to require this fix is
	GL830 / SanDisk SSD P4 32GB

	Apply the fix adding to kernel bootargs:
	max_hw_sectors=32

Change-Id: Ia666dd9034f0407fb26dcc913261cb0b07027251
Signed-off-by: Andrey Gelman <andreyg@compulab.co.il>
Revert "HACK: don't allow disconnection of USB-SATA on TrimSlice"

This reverts commit 3e7c3aa781017b642dfb44472b1860fbe5b3c408.

Signed-off-by: Andrey Gelman <andreyg@compulab.co.il>
Support network tunneling:
'tun' module

Change-Id: Iaea112e10e068931782cb7e50a1123dea8ef1b64
tegra: trimslice: led: enable front panel leds, for accessing through /sys/class/gpio

Change-Id: Icd14cec84c63e053a4b4af02c6d6beb9d967580e
Signed-off-by: Andrey Gelman <andrey.gelman@compulab.co.il>
ARM: tegra: make HDMI audio error messages more comprehensive

Change-Id: I82103c0ae21f0eade01814dc15936d3935f7a898
video: tegra: hdmi: change the way hdmi bottom half is cancelled

Calling sychronous function cancel_delayed_work from interrupt context will put it
on hold till work is cancelled, which is not recommended in ISR. Using similar
function __cancel_delayed_work which works asynchronouly.

Bug 885275

Change-Id: I356af7bf8a22f14aceda4b0171466884e0080da2
Signed-off-by: Sanjay Singh Rawat <srawat@nvidia.com>
Reviewed-on: http://git-master/r/67681
Reviewed-by: Varun Colbert <vcolbert@nvidia.com>
Tested-by: Varun Colbert <vcolbert@nvidia.com>
Signed-off-by: Andrey Gelman <andrey.gelman@compulab.co.il>
Revert "ARM: vfp: Prevent process migration"

This reverts commit 547dce03b0b1b02bd556975fdac86590aec8b673,
that caused:
VFP support v0.3:
BUG: sleeping function called from invalid context at /home/andrey/Work/ics-4-tegra/kernel/kernel/mutex.c:85
in_atomic(): 1, irqs_disabled(): 0, pid: 1, name: swapper
[<c00454a4>] (unwind_backtrace+0x0/0xf0) from [<c04bdb24>] (mutex_lock+0x18/0x38)
[<c04bdb24>] (mutex_lock+0x18/0x38) from [<c04aeec0>] (register_cpu_notifier+0xc/0x2c)
[<c04aeec0>] (register_cpu_notifier+0xc/0x2c) from [<c000a064>] (vfp_init+0xa4/0x1a8)
[<c000a064>] (vfp_init+0xa4/0x1a8) from [<c003a588>] (do_one_initcall+0x94/0x164)
[<c003a588>] (do_one_initcall+0x94/0x164) from [<c000841c>] (kernel_init+0xa8/0x158)
[<c000841c>] (kernel_init+0xa8/0x158) from [<c00405b8>] (kernel_thread_exit+0x0/0x8)
implementor 41 architecture 3 part 30 variant 9 rev 1
ARM: 7417/1: vfp: ensure preemption is disabled when enabling VFP access

The vfp_enable function enables access to the VFP co-processor register
space (cp10 and cp11) on the current CPU and must be called with
preemption disabled. Unfortunately, the vfp_init late initcall does not
disable preemption and can lead to an oops during boot if thread
migration occurs at the wrong time and we end up attempting to access
the FPSID on a CPU with VFP access disabled.

This patch fixes the initcall to call vfp_enable from a non-preemptible
context on each CPU and adds a BUG_ON(preemptible) to ensure that any
similar problems are easily spotted in the future.

Cc: stable@vger.kernel.org
Reported-by: Hyungwoo Yang <hwoo.yang@gmail.com>
Signed-off-by: Hyungwoo Yang <hyungwooy@nvidia.com>
Signed-off-by: Will Deacon <will.deacon@arm.com>
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>

Conflicts:

	arch/arm/vfp/vfpmodule.c

Change-Id: Ibac75323fc3b1300b4b27e255045e7237b513f89
Signed-off-by: Andrey Gelman <andrey.gelman@compulab.co.il>
trimslice_android_defconfig: remove debugging code from normal kernel build

Change-Id: Ia160d80b47d4c2ba413743ae9899eee7f68769c3
Merge branch 'trimslice-14r13' into upstream