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
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
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
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
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
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
6 matches
Mail list logo