Thanks Bob for the quick help.
So at this moment, we do not have a way to explicitly specify the i2c
bus number for pca9548 from modprobe command line, correct?
BR,
Eric
On Thu, May 7, 2015 at 1:24 AM, Bob Feretich
<bob.feretich@xxxxxxxxxxxxxxx> wrote:
> On 5/6/2015 9:35 AM, os user wrote:
>>
>> Hi there,
>>
>> For some reasons, we need to assign bus id for the channels of I2c mux
>> pca9548.
>>
>>> From the code, it seems we can use "adap_id" of
>>
>>
>> struct pca954x_platform_mode {
>> int adap_id;
>> unsigned int deselect_on_exit:1;
>> unsigned int class;
>> };
>>
>> But my questions is, can we assign bus id through device tree and
>> modprobe?
>
> I have been meaning to submit a patch for this to the documentation. I'll
> get to it soon. See attachment on how to assign i2c bus numbers from the DT.
> -Bob
>>
>>
>> Thanks.
>>
>> On Thu, May 7, 2015 at 12:33 AM, os user <gnusercn@xxxxxxxxx> wrote:
>>>
>>> Hi there,
>>>
>>> For some reasons, we need to assign bus id for the channels of I2c mux
>>> pca9548.
>>>
>>> From the code, it seems we can use "adap_id" of
>>>
>>> struct pca954x_platform_mode {
>>> int adap_id;
>>> unsigned int deselect_on_exit:1;
>>> unsigned int class;
>>> };
>>>
>>> But my questions is, can we assign bus id through device tree and
>>> modprobe?
>>>
>>> Thanks.
>>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-i2c" in
>> the body of a message to majordomo@xxxxxxxxxxxxxxx
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>
>
--
To unsubscribe from this list: send the line "unsubscribe linux-i2c" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
