diff options
author | 2023-01-03 11:59:12 -0600 | |
---|---|---|
committer | 2023-01-10 16:56:27 -0800 | |
commit | 3689abfc4e369a643d758a02fb9ad0b2403d6d6d (patch) | |
tree | 794d1f532f12cb0a86767e93c38a3d9103f841b0 /tools/perf/scripts/python/export-to-postgresql.py | |
parent | Input: iqs269a - increase interrupt handler return delay (diff) | |
download | wireguard-linux-3689abfc4e369a643d758a02fb9ad0b2403d6d6d.tar.xz wireguard-linux-3689abfc4e369a643d758a02fb9ad0b2403d6d6d.zip |
Input: iqs269a - configure device with a single block write
Unless it is being done as part of servicing a soft reset interrupt,
configuring channels on-the-fly (as is the case when writing to the
ati_trigger attribute) may cause GPIO3 (which reflects the state of
touch for a selected channel) to be inadvertently asserted.
To solve this problem, follow the vendor's recommendation and write
all channel configuration as well as the REDO_ATI register field as
part of a single block write. This ensures the device has been told
to re-calibrate itself following an I2C stop condition, after which
sensing resumes and GPIO3 may be asserted.
Fixes: 04e49867fad1 ("Input: add support for Azoteq IQS269A")
Signed-off-by: Jeff LaBundy <jeff@labundy.com>
Reviewed-by: Mattijs Korpershoek <mkorpershoek@baylibre.com>
Link: https://lore.kernel.org/r/Y7Rs8GyV7g0nF5Yy@nixie71
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Diffstat (limited to '')
0 files changed, 0 insertions, 0 deletions