diag: dci: Add DCI support for APSS logs and events and cmd/rsp

Currently, Diag DCI supports only modem. Add DCI functionality
to support logs and events generated on the apss processor. Also
add the command response support for DCI on apps processor. It
also handles dedicated commands that are handled exclusively by
the Apps processor.

Change-Id: I8019ed61b9696b62de9db142ebd84ccb12bf19d4
Signed-off-by: Katish Paran <kparan@codeaurora.org>
[media] media: info leak in __media_device_enum_links.()

These structs have holes and reserved struct members which aren't
cleared.  I've added a memset() so we don't leak stack information.

Conflicts:

	drivers/media/media-device.c

Change-Id: Ia22c66d36c0a7bcaee60e65a7db406a40f973006
Git-commit: c88e739b1fad662240e99ecbd0bdaac871717987
Git-repo: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
Signed-off-by: Deva Ramasubramanian <dramasub@codeaurora.org>
Signed-off-by: Abhinav Gurram <c_abhina@codeaurora.org>
ARM: dts: msm: revert max-hw-load to fix concurrency usecases

This reverts commit 8da43bfcfa577e54ab516e06ec63ea99d611ca08.
The commit 8da43bfcfa577e54ab516e06ec63ea99d611ca08 was reducing
the maximum load which fails the concurrent usecase 1080p WFD with
4096*2160 playback.
During concurrency usecase 4096*2160 24fps Decode + 1080p 30fps WFD encode,
the MBs/sec is calculated based on default fps i.e. 30 with resolution
as 4096*2160. So eventually it becomes 4096*2160 30fps Decode + 1080p 30fps
WFD encode. This exceeds the max supported load and playback is aborted.

Change-Id: I699f2dbbb5d7807cc5800b47f7616c52b6fac11b
CRs-Fixed: 668061
Signed-off-by: Balamurugan Alagarsamy <balaga@codeaurora.org>
platform: msm: fix PFT when using direct-io

When we read/write a file using dircet-io (O_DIRECT),
we can't get the inode from a bio by walking the path
bio->bi_io_vec->bv_page->mapping->host
since the page is anonymous and not mapped.
On the other more typical cases when not using O_DIRECT,
the page cache is used and the bv_page is available.

Change-Id: I349cad54a978ed9919f960d55f0f95c1e53262e5
Signed-off-by: Amir Samuelov <amirs@codeaurora.org>
Merge "platform: msm: fix PFT when using direct-io"
Merge "Merge "platform: msm: fix PFT when using direct-io""
Merge "ARM: dts: msm: revert max-hw-load to fix concurrency usecases"
Merge "diag: dci: Add DCI support for APSS logs and events and cmd/rsp"
Merge "Merge "diag: dci: Add DCI support for APSS logs and events and cmd/rsp""
tspp: fix bam irq request preventing sleep

Registering and resetting BAM device upon initialization of tspp
driver requests bam irq resource, which prevents entering sleep.
Instead, BAM device is now initialized only when first needed which
is when the first channel is opened. BAM device is uninitialized
when channel is closed.

Change-Id: I056acea721fae164b91a2a5e3946028b4c2b6df2
Signed-off-by: Gilad Broner <gbroner@codeaurora.org>
Merge "tspp: fix bam irq request preventing sleep"
Merge "Merge "tspp: fix bam irq request preventing sleep""
spi_qsd: Fix bug in multi-xfer bam mode transaction

Spi doesn't handle multiple xfer per message scenario
(eg:Rd->Wr or Wr->Rd) correctly and spi request
stuck indefinetly in while loop when total byte count
is not 0.

increment both(rx,tx) references so next bam
transaction will be queued correctly. Flush the
bam pipes after each transactions.

CRs-Fixed: 637693
Change-Id: I455df38be2f9687b1eb2a704466f6974dfb83a22
Signed-off-by: Alok Chauhan <alokc@codeaurora.org>
msm: mdss: synchronize recovery handler access

The recovery handler is used in the dsi event thread, and
the recovery handler variable was configured from a different
thread.  Earlier, there is no synchronization between the two
threads accessing the recovery handler, causing kernel panics.

Change-Id: Iee990276fdabd65e2e1f2e3c21ad574fc0d8a7bc
Signed-off-by: Xiaoming Zhou <zhoux@codeaurora.org>
Signed-off-by: Shivaraj Shetty <shivaraj@codeaurora.org>
Revert "Revert "ARM: dts: msm: Limit DDR to 200MHz for APSS freVquency""

This reverts commit c08168c57970ef7fed2f587acee64e7011ebadf0

Change-Id: Id6ef5580e3956e39dc9485f5921d0db5eefa85fc
Merge "spi_qsd: Fix bug in multi-xfer bam mode transaction"
USB: dwc3: otg: Fix stop endpoint command timeout issue

Currently HSPHY SUSP bit is set while starting host mode and
it is not cleared till stopping host mode. As part of urb dequeue,
xhci stack will queue stop endpoint command for flushing endpoint
which is getting timedout due to this HSPHY SUSP bit. Hence clear
this bit before queuing stop endpoint command and set it back after
stop endpoint command completion. Otherwise xhci stack treats this
timeout as fatal error and halts host controller.

Crs-Fixed: 580268
Change-Id: I784407386e6f87bcabd8569fcbae4e3af167144d
Signed-off-by: Vijayavardhan Vennapusa <vvreddy@codeaurora.org>
Merge "Revert "Revert "ARM: dts: msm: Limit DDR to 200MHz for APSS freVquency"""
Merge "USB: dwc3: otg: Fix stop endpoint command timeout issue"
Merge "Merge "spi_qsd: Fix bug in multi-xfer bam mode transaction""