Re: [PATCH v2 1/1] Input: atmel_mxt_ts - implement I2C retries

Hi Andy Thanks for your comment On 2020/09/06 3:02, Andy Shevchenko wrote: On Thursday, September 3, 2020, Jiada Wang > wrote: From: Nick Dyer mailto:nick.d...@itdev.co.uk>> Some maXTouch chips (eg mXT1386) will not respond on the first I2C request

Re: [PATCH v2 1/1] Input: atmel_mxt_ts - implement I2C retries

05.09.2020 21:02, Andy Shevchenko пишет: ... >  #define MXT_CRC_TIMEOUT                1000    /* msec */ >  #define MXT_FW_RESET_TIME      3000    /* msec */ >  #define MXT_FW_CHG_TIMEOUT     300     /* msec */ > +#define MXT_WAKEUP_TIME                25      /* msec */ > > > Ca

Re: [PATCH v2 1/1] Input: atmel_mxt_ts - implement I2C retries

03.09.2020 18:59, Jiada Wang пишет: > From: Nick Dyer > > Some maXTouch chips (eg mXT1386) will not respond on the first I2C request > when they are in a sleep state. It must be retried after a delay for the > chip to wake up. > > Signed-off-by: Nick Dyer > Acked-by: Yufeng Shen > (cherry pick

[PATCH v2 1/1] Input: atmel_mxt_ts - implement I2C retries

From: Nick Dyer Some maXTouch chips (eg mXT1386) will not respond on the first I2C request when they are in a sleep state. It must be retried after a delay for the chip to wake up. Signed-off-by: Nick Dyer Acked-by: Yufeng Shen (cherry picked from ndyer/linux/for-upstream commit 63fd7a2cd03c3