Skuf use touch panel protocol B for touch event recognition that
needs enable this protocol in driver.
Change-Id: Ic855ed4fb0277a9bc5996bcb310db67b8ccf5c03
Signed-off-by: Bingzhe Cai <bingzhec@codeaurora.org>
Signed-off-by: Sudhakar Manapati <smanap@codeaurora.org>
Add support for FB notifications to trigger suspend/resume
based on FB blank/unblank events.
Change-Id: I61803e3a731e047d0641e3b1ccbae58b9bd1bd89
Signed-off-by: Bingzhe Cai <bingzhec@codeaurora.org>
Signed-off-by: Sudhakar Manapati <smanap@codeaurora.org>
Add power initialization function to request internal and external
LDO depends on device tree configuration. Add power control function
to enable and disable device power.
Change-Id: If063900f8cd61c36c4b200d781c68e742cd6bbaf
Signed-off-by: Bingzhe Cai <bingzhec@codeaurora.org>
Signed-off-by: Sudhakar Manapati <smanap@codeaurora.org>
IT7260 touch controllers are capacitative touch controller ICs
with multi-touch support and can detect upto 3 fingers.
Change-Id: I20a4339639a715111a340b7a607448ec7078549e
Signed-off-by: Abinaya P <abinayap@codeaurora.org>
Currently, on Modem SSR, memshare driver receives notification
in which it free up the allocated memory. Due to timing issue,
free is happening after allocation. This patch synchronize
these operations.
Change-Id: I464d3b82f33ccdfd0988ef33fec8414d4ab4a550
Signed-off-by: Mohit Aggarwal <maggarwa@codeaurora.org>
Add ITE tech touch screen driver for the compilation.
Change-Id: Iee6abc583917968879a19a5e67b4db08d506c794
Signed-off-by: Abinaya P <abinayap@codeaurora.org>
Add pinctrl support for Synaptics S2333 controller so that the irq and
pwr pins could be pulled up when probed and resumed. Furthermore, they
should be pulled down when suspended and removed.
Change-Id: If517747243a605eacd1f6ffd6d1f7c0d45d06c1b
Signed-off-by: Changmin Liu <changmil@codeaurora.org>
Add device tree parser to allow Goodix touchpanel driver to get
board dependent configuration from device tree.
Change-Id: I702400140130fd3b673e0e13a8dbdb7060bba881
Signed-off-by: Bingzhe Cai <bingzhec@codeaurora.org>
Signed-off-by: Sudhakar Manapati <smanap@codeaurora.org>
This avoids potential problems caused by a race where the inode gets
renamed out from its parent directory and the parent directory is
deleted while ext4_d_revalidate() is running.
Change-Id: I28a1f87f236ca97ce28e876265075f1d3bcdca6a
Fixes: 28b4c263961c
Reported-by: Al Viro <viro@ZenIV.linux.org.uk>
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
Cc: stable@vger.kernel.org
Git-commit: 3d43bcfef5f0548845a425365011c499875491b0
Git-repo: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git
Signed-off-by: Andrey Markovytch <andreym@codeaurora.org>
We don't want the writeback triggered from the journal commit (in
data=writeback mode) to cause the journal to abort due to
generic_writepages() returning an ENOMEM error. In addition, if
fsync() fails with ENOMEM, most applications will probably not do the
right thing.
So if we are doing a data integrity sync, and ext4_encrypt() returns
ENOMEM, we will submit any queued I/O to date, and then retry the
allocation using GFP_NOFAIL.
Change-Id: Ib16510f0261275a61c2b6870503e67b4b1189bee
Google-Bug-Id: 27641567
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
Git-commit: c9af28fdd44922a6c10c9f8315718408af98e315
Git-repo: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git
Signed-off-by: Andrey Markovytch <andreym@codeaurora.org>
There is no need to reinit device when spontaneous reset is detected,
touch will recover by itself.
Change-Id: Ifb5b134d0fbeb2f55f16af8806abb9c8e51c35e0
Signed-off-by: Xiaonian Wang <xiaonian@codeaurora.org>
In synaptics_dsx_2.6 touch driver, secure_touch_init tries to get
the QUP clocks for the secure touch functionality. But as these
calls are optional and TZ might get the owenership of these clocks,
this change removes the error return statement, so that the
secure touch can be initialized properly.
Change-Id: I12b5075d484cd397bfb423479589e159a2193f31
Signed-off-by: Shantanu Jain <shjain@codeaurora.org>
These power domains are required by clients to be controlled before any
clock request, so add support for the same.
Change-Id: I7d600648281d2f4375307b0e0dd1bf121d0e6e4f
Signed-off-by: Taniya Das <tdas@codeaurora.org>
Add all the gate clocks which are part of msm8996 global
clock controller(GCC) and would be used by clients to
control these clocks using the clock controller framework.
Change-Id: I16238940798ab5627c04fe050a6daf75f1d54277
Signed-off-by: Odelu Kukatla <okukatla@codeaurora.org>
Remove the RPM controlled clocks and add missing clocks.
Also clean up clock flags and parent info for few clocks.
Change-Id: I7ae55f992be29a28617070ca7792f912592c3628
Signed-off-by: Odelu Kukatla <okukatla@codeaurora.org>
The overflow check is required to ensure that user space data
in kernel may not go beyond buffer boundary.
CRs-Fixed: 1064411
Change-Id: I54c28a8942cf1a6a47a4e8272f3159b35d753ead
Signed-off-by: Karthik Reddy Katta <a_katta@codeaurora.org>
gic_write/read use write/read_relaxed function which will create
lots of RTB logging. Change the API to no_log version to remove
those RTB logs.
Change-Id: Ide59d8c2753364840f8a2b304ef0c169870c8509
Signed-off-by: Runmin Wang <runminw@codeaurora.org>
If the following call chain fails
adf_device_post_nocopy() ->
adf_buffer_map() ->
dma_buf_attach(); dma_buf_map_attachment()
then the attachment returned by dma_buf_attach() will get cleaned up
twice: first during the error-handling path inside adf_buffer_map(), and
again during the error-handling path inside adf_device_post_nocopy().
Fix this by zeroing out the mapping data inside adf_buffer_map()'s
error-handling path. When adf_device_post_nocopy() hands it back to
adf_buffer_mapping_cleanup(), it will deliberately skip over zeroed-out
data.
(The second adf_buffer_mapping_cleanup() call inside
adf_device_post_nocopy() is not a bug; it's intended to clean up after
any *other* buffers we handled as part of this request.)
CVE:CVE-2016-3811
Bug: 28025945
Bug: 28279077
Change-Id: I824d980b208da3a15d35f74970755c8f18500263
Signed-off-by: Greg Hackmann <ghackmann@google.com>
Git-repo: https://android.googlesource.com/kernel/msm.git
Git-commit: 4436de7a92d037599e0d217f16f9c391b6ad866a
Signed-off-by: Ravi Kumar Siddojigari <rsiddoji@codeaurora.org>
Add support to indicate if the switcher is acting in input limited state.
Switcher running in high duty cycle (HDC) mode should also be indicated as
input limited condition.
HDC is a 5uS pulse and sw reading the real time status register may not
indicate that it is active. Basically the presence of the pulses and the
interrupts indicate HDC and conversely their absence indicates no
HDC. Set a flag in the interrupt and clear it in a delayed work queue in
20mS. As long as the interrupts happen this flag will remain set,
indicating HDC.
Change-Id: Ia2e2d02240c36ba982f9e190b88b822b5f1b90f1
Signed-off-by: Abhijeet Dharmapurikar <adharmap@codeaurora.org>
The 'vconn' regulator is spelled with two n's, not one.
Change-Id: I118d4e1dbd1aa26c2637e5ea4f4ba5b6006bebff
Signed-off-by: Jack Pham <jackp@codeaurora.org>
