+Wolfram On Wed, Dec 28, 2022 at 09:01:46AM +0100, Primoz Fiser wrote: > On 16. 12. 22 13:51, Francesco Dolcini wrote: > > On Fri, Dec 16, 2022 at 01:23:29PM +0100, Primoz Fiser wrote: > > > The only solid point in the thread seems to be that in that case we are not > > > covering up the potential i2c hardware issues? > > > > I believe that in this case we should just have a warning in the kernel. > > The retry potentially work-around a transient issue and we do not hide any hardware > > issue at the same time. It seems an easy win-win solution. > > I would agree about throwing a warning message in retry case. > > Not sure how would it affect other i2c bus drivers using retries > 0. > Retries might be pretty rare with i2c-imx but some other drivers set this to > 5 for example. At least using _ratelimited printk is a must using this > approach. Wolfram, Uwe, Oleksij Would it be acceptable to have a warning when we have I2C retries, and with that in place enabling retries on the imx driver? It exists hardware that requires this to work correctly, and at a minimum setting the retry count from user space is not going to solve potential issues during initial driver probe. To me the only reasonable solution is to have the retry enabled with a sensible number (3? 5?), however there is a concern that this might hide real hardware issues. > > > Yeah fair point but on the other hand, goal of this patch would be to > > > improve robustness in case of otherwise good performing hardware. From user > > > perspective I just want it to work despite it retrying under the hood from > > > time to time. I think Francesco had the same idea. > > > > Unfortunately I was missing the exact background that made us do this > > change, we just had it sitting in our fork for too long :-/ > > This is one of the reason I gave up on it. > > > > Quoting Uwe [1] > > > sometimes there is no practical way around such work arounds. I happens > > > from time to time that the reason for problem is known, but fixing the > > > hardware is no option, then you need such workrounds. (This applies to > > > both, retrying the transfers and resetting the bus.) > > I wouldn't say this is exactly a workaround if "retries mechanism" is > standard part of the i2c core. Other drivers use it as well. it is just a > setting to improve bus robustness. > > But OK, I guess we can live with this one-liner in the downstream kernel. To me this is not a good idea. Francesco
