drivers: usb: hbm: Disable async scheduler when init a pipe

When we touch the HBM we need to make sure that the async
scheduler is not running. Otherwise it might stuck the controller
sooner or later. Since the controller uses the BAM for direct access
if anything gets stuck with the HBM, it might get the whole
controller unresponsive. (even endpoints unrelated to HBM, like
the control endpoint).
This change also adds the correct reset sequence steps
to the HBM pipes.

CRs-fixed: 613557, 591930
Change-Id: I13069909aafd682f52178f11debb95af45be28f4
Signed-off-by: Lena Salman <esalman@codeaurora.org>
Signed-off-by: Ido Shayevitz <idos@codeaurora.org>
Merge "drivers: usb: hbm: Disable async scheduler when init a pipe"
[PATCH] Staging: android: binder: More offset validation.

Make sure offsets don't point to overlapping flat_binder_object
structs.

Change-Id: I425ab0c46fbe2b00ed679c5becf9e8140395eb40
Signed-off-by: Arve HjÃ¸nnevÃ¥g <arve@android.com>
[media] v4l2-ioctl.c: handle PREPARE_BUF like QUERYBUF

The core code for PREPARE_BUF didn't take the multiplanar case into
account, which might cause page faults. Handle PREPARE_BUF just like
QUERYBUF and QBUF/DQBUF.

Change-Id: Ida7f712edec32568a8c2651d54b160121009a9c4
Signed-off-by: Hans Verkuil <hans.verkuil@cisco.com>
Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
Signed-off-by: Srinu Gorle <sgorle@codeaurora.org>
CRs-Fixed: 637365
Merge "[media] v4l2-ioctl.c: handle PREPARE_BUF like QUERYBUF"
Merge "[PATCH] Staging: android: binder: More offset validation."
ASoC: msm: qdsp6v2: Copy frame data based on frame length

Copying data based on count will result in copying
uninitialized data to userspace which can potentially
disclose sensitive data. Fix by copying data based on
frame instead.

CRs-Fixed: 552528, 552531
Change-Id: I307b285ef2aefe00b953cf650582e9ff7e03ceb1
Signed-off-by: Shiv Maliyappanahalli <smaliyap@codeaurora.org>
Signed-off-by: Gopal G Goberu <ggober@codeaurora.org>
ASoC: msm: qdsp6v2: Add timestamp in voip frame header

Uplink timestamp needs to propagate to userspace for AV sync.
timestamp field is added in voip frame header to
capture the timestamp from LPASS for each uplink packet.

Change-Id: Id701df56e5a3d36bf83771ba9731c61a03dae3ba
Signed-off-by: Helen Zeng <xiaoyunz@codeaurora.org>
ASoC: msm: qdsp6v2: Add timestamp in voip frame header

Uplink timestamp needs to propagate to userspace for AV sync.
timestamp field is added in voip frame header to
capture the timestamp from LPASS for each uplink packet.

Change-Id: I99cb214630e78a3b8086874b3e6d32cd6ff00ef4
Signed-off-by: Helen Zeng <xiaoyunz@codeaurora.org>
Merge "ASoC: msm: qdsp6v2: Copy frame data based on frame length"
Merge "ASoC: msm: qdsp6v2: Add timestamp in voip frame header"
Merge "ASoC: msm: qdsp6v2: Add timestamp in voip frame header"
msm: ocmem: Call restore_sec_config() after every power collapse.

As the QRIB is enabled, after every power collapse of ocmem, the
QRIB is reset to the maximum security state. Due to this the apps
processor cannot access the ocmem register space.

The restore_sec_config() scm call needs to be called before any
register is accessed after a power collapse to ensure that the
security configuration is restored. The clocks need to be turned
on before every call that is made into TZ to ensure that there
is no power collapse.

CRs-Fixed: 651324, 660089

Conflicts:
	arch/arm/mach-msm/ocmem_core.c

Change-Id: Ieb6b635142057e219de29e811c93749f6500cec5
Signed-off-by: Neeti Desai <neetid@codeaurora.org>
Signed-off-by: Natiq Ahmed <mnatiq@codeaurora.org>
msm: camera: make sure num_buf is not out of bound.

V4L2 only allow 32 buffers. Check the num_buf to make sure that
user space passed value is not out of bound.

Change-Id: I662ec1eb998ed8bfb2a7f188e645410aa78c83b0
Signed-off-by: Hariram Purushothaman <hpurus@codeaurora.org>
Signed-off-by: Natiq Ahmed <mnatiq@codeaurora.org>
arm: mach-msm: Remove the unused rmt_storage code.

The rmt_storage module is no longer used.
Remove the unused module and cleanup the makefile and kconfig.

CRs-Fixed: 549951

Conflicts:
	arch/arm/mach-msm/Kconfig
	arch/arm/mach-msm/Makefile

Change-Id: Ie9ebaa2209ea9fa0df05dc892504fcb882f00f29
Signed-off-by: Nikhilesh Reddy <reddyn@codeaurora.org>
Signed-off-by: Natiq Ahmed <mnatiq@codeaurora.org>
msm: kgsl: Enable protected mode for A3XX

Enable protected register mode for A3XX with these commits from
msm-3.10:

msm: kgsl: Enable protected register mode for A3XX
msm: kgsl: Print the register that causes a protected mode error
msm: kgsl: Unprotect the VBIF performance counters

Change-Id: Ic0dedbad950ffbd063fd861d9440bb5dce8d5fb1
Signed-off-by: Jordan Crouse <jcrouse@codeaurora.org>
msm: kgsl: Protect SMMU registers from being written by the GPU

Put the SMMU register range in protected mode to shield them from
IB1/IB2 writes from userspace.

CRs-Fixed: 599971
Change-Id: Ic0dedbad8c03fc1c54ff73221231e2440d3c34dd
Signed-off-by: Jordan Crouse <jcrouse@codeaurora.org>
Merge "msm: camera: make sure num_buf is not out of bound."
Merge "msm: ocmem: Call restore_sec_config() after every power collapse."
Merge "msm: kgsl: Enable protected mode for A3XX"