Re: [PATCH] i2c: uniphier-f: correct error recovery

2023-01-06 Thread Tom Rini
On Fri, Dec 09, 2022 at 08:38:27PM +0900, Dai Okamura wrote: > The uniphier i2c block can recognize some handshake errors. > But driver handles all error detections as no error if no timeout. > So this makes unrecoverable state. > > This replaces the return values with the right ones to tell the

Re: [PATCH] i2c: uniphier-f: correct error recovery

2023-01-01 Thread Tom Rini
On Sun, Jan 01, 2023 at 08:45:44AM +0100, Heiko Schocher wrote: > Hello Dai Okamura, > > On 09.12.22 12:38, Dai Okamura wrote: > > The uniphier i2c block can recognize some handshake errors. > > But driver handles all error detections as no error if no timeout. > > So this makes unrecoverable stat

Re: [PATCH] i2c: uniphier-f: correct error recovery

2022-12-31 Thread Heiko Schocher
Hello Dai Okamura, On 09.12.22 12:38, Dai Okamura wrote: > The uniphier i2c block can recognize some handshake errors. > But driver handles all error detections as no error if no timeout. > So this makes unrecoverable state. > > This replaces the return values with the right ones to tell the i2c

Re: [PATCH] i2c: uniphier-f: correct error recovery

2022-12-25 Thread Kunihiko Hayashi
On 2022/12/09 20:38, Dai Okamura wrote: The uniphier i2c block can recognize some handshake errors. But driver handles all error detections as no error if no timeout. So this makes unrecoverable state. This replaces the return values with the right ones to tell the i2c framework the errors: - ED

[PATCH] i2c: uniphier-f: correct error recovery

2022-12-09 Thread Dai Okamura
The uniphier i2c block can recognize some handshake errors. But driver handles all error detections as no error if no timeout. So this makes unrecoverable state. This replaces the return values with the right ones to tell the i2c framework the errors: - EDEADLK for arbitration lost error - ENODATA