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

03.09.2020 17:44, Wang, Jiada пишет: > Hi Dmitry > ... >> Is it really possible to get a positive ret != 2 from i2c_transfer()? >> >> Maybe it's better to keep the old code behaviour by returning the "ret" >> value directly if it's not equal to ARRAY_SIZE(xfer)? >> > I think, theoretically i2c_tra

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

Hi Dmitry On 2020/08/28 17:19, Dmitry Osipenko wrote: 21.08.2020 11:22, 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 D

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

21.08.2020 11:22, 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 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