Re: [PATCH] i2c-mux-pca954x: Force reset on probe if available

2018-05-19 Thread Peter Rosin
On 2018-05-08 10:06, Mike Looijmans wrote: > On 08-05-18 08:36, Peter Rosin wrote: >> On 2018-05-01 13:42, Mike Looijmans wrote: >>> Instead of just hogging the reset GPIO into deactivated state, activate and >>> then de-activate the reset. This allows for better recovery if the CPU was >>> reset h

Re: [PATCH] i2c-mux-pca954x: Force reset on probe if available

2018-05-08 Thread Mike Looijmans
On 08-05-18 08:36, Peter Rosin wrote: On 2018-05-01 13:42, Mike Looijmans wrote: Instead of just hogging the reset GPIO into deactivated state, activate and then de-activate the reset. This allows for better recovery if the CPU was reset halfway through an I2C transaction for example. I can't

Re: [PATCH] i2c-mux-pca954x: Force reset on probe if available

2018-05-07 Thread Peter Rosin
On 2018-05-01 13:42, Mike Looijmans wrote: > Instead of just hogging the reset GPIO into deactivated state, activate and > then de-activate the reset. This allows for better recovery if the CPU was > reset halfway through an I2C transaction for example. I can't see any problems with this, and a re

[PATCH] i2c-mux-pca954x: Force reset on probe if available

2018-05-01 Thread Mike Looijmans
Instead of just hogging the reset GPIO into deactivated state, activate and then de-activate the reset. This allows for better recovery if the CPU was reset halfway through an I2C transaction for example. Signed-off-by: Mike Looijmans --- drivers/i2c/muxes/i2c-mux-pca954x.c | 12 ++-- 1