Re: [PATCH 2/2] i2c-mux-gpio: eliminate i2c channel order assumptions

2013-10-11 Thread Ionut Nicu
Hi, On 10.10.2013 12:34, Alexander Sverdlin wrote: > Hi! > > On 10/10/2013 10:39 AM, Ionut Nicu wrote: >> The i2c-mux driver uses the chan_id parameter provided >> in i2c_add_mux_adapter as a parameter to the select >> and deselect callbacks while the i2c-mux-gpio driver >> uses the chan_id as

Re: [PATCH 2/2] i2c-mux-gpio: eliminate i2c channel order assumptions

2013-10-11 Thread Ionut Nicu
Hi, On 10.10.2013 12:34, Alexander Sverdlin wrote: Hi! On 10/10/2013 10:39 AM, Ionut Nicu wrote: The i2c-mux driver uses the chan_id parameter provided in i2c_add_mux_adapter as a parameter to the select and deselect callbacks while the i2c-mux-gpio driver uses the chan_id as an index in

Re: [PATCH 2/2] i2c-mux-gpio: eliminate i2c channel order assumptions

2013-10-10 Thread Alexander Sverdlin
Hi! On 10/10/2013 10:39 AM, Ionut Nicu wrote: > The i2c-mux driver uses the chan_id parameter provided > in i2c_add_mux_adapter as a parameter to the select > and deselect callbacks while the i2c-mux-gpio driver > uses the chan_id as an index in the mux->data.values > array. > > A simple example

[PATCH 2/2] i2c-mux-gpio: eliminate i2c channel order assumptions

2013-10-10 Thread Ionut Nicu
The i2c-mux driver uses the chan_id parameter provided in i2c_add_mux_adapter as a parameter to the select and deselect callbacks while the i2c-mux-gpio driver uses the chan_id as an index in the mux->data.values array. A simple example of where this doesn't work is when we have a device tree

[PATCH 2/2] i2c-mux-gpio: eliminate i2c channel order assumptions

2013-10-10 Thread Ionut Nicu
The i2c-mux driver uses the chan_id parameter provided in i2c_add_mux_adapter as a parameter to the select and deselect callbacks while the i2c-mux-gpio driver uses the chan_id as an index in the mux-data.values array. A simple example of where this doesn't work is when we have a device tree like

Re: [PATCH 2/2] i2c-mux-gpio: eliminate i2c channel order assumptions

2013-10-10 Thread Alexander Sverdlin
Hi! On 10/10/2013 10:39 AM, Ionut Nicu wrote: The i2c-mux driver uses the chan_id parameter provided in i2c_add_mux_adapter as a parameter to the select and deselect callbacks while the i2c-mux-gpio driver uses the chan_id as an index in the mux-data.values array. A simple example of