diff options
| author | John Keeping <[email protected]> | 2021-10-06 11:06:03 -0700 |
|---|---|---|
| committer | Dmitry Torokhov <[email protected]> | 2021-10-11 18:32:54 -0700 |
| commit | 2667f6b7af99e81958fa97c03bb519fcb09d0055 (patch) | |
| tree | 23a40e1162f578a91d7dbaf8d9204bab37bb3e9e /lib/test_fortify/write_overflow-strncpy.c | |
| parent | a41392e0877a271007e9209e63c34cab7527eb43 (diff) | |
Input: st1232 - increase "wait ready" timeout
I have a ST1633 touch controller which fails to probe due to a timeout
waiting for the controller to become ready. Increasing the minimum
delay to 100ms ensures that the probe sequence completes successfully.
The ST1633 datasheet says nothing about the maximum delay here and the
ST1232 I2C protocol document says "wait until" with no notion of a
timeout.
Since this only runs once during probe, being generous with the timout
seems reasonable and most likely the device will become ready
eventually.
(It may be worth noting that I saw this issue with a PREEMPT_RT patched
kernel which probably has tighter wakeups from usleep_range() than other
preemption models.)
Fixes: f605be6a57b4 ("Input: st1232 - wait until device is ready before reading resolution")
Signed-off-by: John Keeping <[email protected]>
Reviewed-by: Geert Uytterhoeven <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Dmitry Torokhov <[email protected]>
Diffstat (limited to 'lib/test_fortify/write_overflow-strncpy.c')
0 files changed, 0 insertions, 0 deletions