Re: [PATCH v2 0/8] i2c mux cleanup and locking update

Hi Antti, On 2016-01-06 18:17, Antti Palosaari wrote: > On 01/05/2016 05:57 PM, Peter Rosin wrote: >> From: Peter Rosin >> >> Hi! >> >> I have a pair of boards with this i2c topology: >> >> GPIO ---| -- BAT1 >> | v / >> I2C

Re: [PATCH v2 0/8] i2c mux cleanup and locking update

Hi Antti, On 2016-01-06 18:17, Antti Palosaari wrote: > On 01/05/2016 05:57 PM, Peter Rosin wrote: >> From: Peter Rosin >> >> Hi! >> >> I have a pair of boards with this i2c topology: >> >> GPIO ---| -- BAT1 >> | v / >>

Re: [PATCH v2 0/8] i2c mux cleanup and locking update

On 01/05/2016 05:57 PM, Peter Rosin wrote: From: Peter Rosin Hi! I have a pair of boards with this i2c topology: GPIO ---| -- BAT1 | v / I2C -+--B---+ MUX | \ EEPROM

Re: [PATCH v2 0/8] i2c mux cleanup and locking update

Hi Wolfram and Peter, I will give my opinion about the path chosen although it should be taken lightly. I can see that hardware guys missed the software guys again on the development path, but since this happens more often than not, I would say it seems OK to have support for this as long as it

Re: [PATCH v2 0/8] i2c mux cleanup and locking update

Hi Wolfram and Peter, I will give my opinion about the path chosen although it should be taken lightly. I can see that hardware guys missed the software guys again on the development path, but since this happens more often than not, I would say it seems OK to have support for this as long as it

Re: [PATCH v2 0/8] i2c mux cleanup and locking update

On 01/05/2016 05:57 PM, Peter Rosin wrote: From: Peter Rosin Hi! I have a pair of boards with this i2c topology: GPIO ---| -- BAT1 | v / I2C -+--B---+ MUX | \

Re: [PATCH v2 0/8] i2c mux cleanup and locking update

Hi Wolfram, On 2016-01-05 19:48, Wolfram Sang wrote: > Peter, > >> PS. needs a bunch of testing, I do not have access to all the involved hw > > First of all, thanks for diving into this topic and the huge effort you > apparently have put into it. Yeah, I started with dipping just the toes,

Re: [PATCH v2 0/8] i2c mux cleanup and locking update

Peter, > PS. needs a bunch of testing, I do not have access to all the involved hw First of all, thanks for diving into this topic and the huge effort you apparently have put into it. It is obviously a quite intrusive series, so it needs careful review. TBH, I can't really tell when I have the

[PATCH v2 0/8] i2c mux cleanup and locking update

From: Peter Rosin Hi! I have a pair of boards with this i2c topology: GPIO ---| -- BAT1 | v / I2C -+--B---+ MUX | \ EEPROM -- BAT2 (B denotes the

[PATCH v2 0/8] i2c mux cleanup and locking update

From: Peter Rosin Hi! I have a pair of boards with this i2c topology: GPIO ---| -- BAT1 | v / I2C -+--B---+ MUX | \ EEPROM -- BAT2 (B

Re: [PATCH v2 0/8] i2c mux cleanup and locking update

Peter, > PS. needs a bunch of testing, I do not have access to all the involved hw First of all, thanks for diving into this topic and the huge effort you apparently have put into it. It is obviously a quite intrusive series, so it needs careful review. TBH, I can't really tell when I have the

Re: [PATCH v2 0/8] i2c mux cleanup and locking update

Hi Wolfram, On 2016-01-05 19:48, Wolfram Sang wrote: > Peter, > >> PS. needs a bunch of testing, I do not have access to all the involved hw > > First of all, thanks for diving into this topic and the huge effort you > apparently have put into it. Yeah, I started with dipping just the toes,