Goodix GT915 driver was provided by vendor and cherry-picked into
our project, it need to be placed to right location.
Change-Id: Idf191144354426233eca41727a41e26ddbf92f95
Signed-off-by: Bingzhe Cai <bingzhec@codeaurora.org>
Signed-off-by: Pan Fang <fangpan@codeaurora.org>
DAPM marks back end dai as dirty during ASoC suspend
which triggers device path teardown. Add ignore suspend
to all back end dais to avoid device path teardown.
CRs-Fixed: 1031932
Change-Id: I89f83feed0702f3a3f3b6141ed73459b8878d2df
Signed-off-by: Sudheer Papothi <spapothi@codeaurora.org>
In general, the IOMMU framework likes to group PCI devices together.
This prevents someone from assigning them to separate VMs using VFIO,
for example. The reason they shouldn't go to separate VMs is because
there could be DMA aliasing between endpoint devices, and because the
root complex device can access anything that endpoint devices can
access.
Unfortunately, this makes things difficult in the DMA layer since the
IOMMU framework freaks out if you try to attach a single device that is
also part of a group. First instinct might be to start using
iommu_attach_group instead of iommu_attach_device in the DMA layer but
that has problems of its own (it attaches *everyone* in the group as
soon as one client attaches). Besides all that, it's also a bit
annoying to have the root complex device in group since, in our
platform, it doesn't actually have any stream IDs assigned to it and it
doesn't do any DMA of its own, so it doesn't really make any logical
sense to attach it.
As a compromise, we can stop grouping PCI devices together by allocating
a new domain for each one. By doing so we no longer need to call
iommu_attach_group in the DMA layer, avoid the issues described above.
It should be noted that with this patch in place we can't securely do
any direct DMA assignment of PCI endpoint devices to separate VMs.
CRs-Fixed: 1036401
Change-Id: I9528b61a695dc7840e1c6f80af18044340f5c6c4
Signed-off-by: Mitchel Humpherys <mitchelh@codeaurora.org>
This Mstar CTP reference driver code is added into a wrong place,
a follow-on patch is created to move the driver to proper path.
Change-Id: I34365ce21659348ad1d1289e3b06b81e778c2648
Signed-off-by: Mao Li <maol@codeaurora.org>
Signed-off-by: Sudhakar Manapati <smanap@codeaurora.org>
Add low power idle mode support in suspend state for ITE tech
touchscreen driver.
Also, execute the touch to wake feature code only when device moves
from idle state to active state.
Change-Id: Ia989d8130bbded4ae5acab0b9c3122998acb2056
Signed-off-by: Shantanu Jain <shjain@codeaurora.org>
Add auto firmware and config upgrade functionality for ITE tech
touchscreen driver.
Add sysfs support for manual fw and cfg upgrade functionality.
Also clean the sysfs function names.
Change-Id: I8912545589cb763c1deb70bebb081e920af69ad2
Signed-off-by: Shantanu Jain <shjain@codeaurora.org>
Changes to support packed 24 bit (SNDRV_PCM_FORMAT_S24_3LE)
CRs-Fixed: 1011048
Change-Id: Id927e9b8894b1bf99e57cc0f04abf126740c6d36
Signed-off-by: Manish Dewangan <manish@codeaurora.org>
Clean ITE tech driver probe function with proper error paths,
call sequence, and return values to release the resources
properly.
Also, release the resource in driver's remove function.
Change-Id: Ia81bb3da7e0b880de6f2ed95d346b533104ed3fc
Signed-off-by: Shantanu Jain <shjain@codeaurora.org>
Add palm-gesture sleep feature for ITE tech touchscreen
driver. When enabled the driver sends a key code to the
user space. Two optional device-tree properties are added
for this: ite,palm-detect and ite,palm-detect-keycode.
Change-Id: I0989cb66ab5edb10769ced9d525bd4f6d7adb02b
Signed-off-by: Shantanu Jain <shjain@codeaurora.org>
Add touch to wake feature in ITE tech touchscreen driver.
The touchscreen interrupt is configured as wakeable interrupt,
so TS can be used to wake the device from suspend state.
Change-Id: I8da53ab4f03237b8652cd5891eadbffa752d72d3
Signed-off-by: Shantanu Jain <shjain@codeaurora.org>
