Hi Michael,
first of all thanks for your answer :-)
On 02/18/2013 11:19 AM, Michael Lawnick wrote:
On my project I do no automatic i2c detection, but all is controlled via
user space. So I always know where and which devices and buses get
connected.
You mean you add devices through sysfs? That's another approach I was
thinking I'd follow, except it still doesn't solve my problem... meaning
I have no reliable way of telling the numbers assigned to the busses added.
devices/platform/i2c-gpio/i2c-0/0-0070/chan-4(=>...i2c-5)/5-0071/chan-0(=>...i2c-9)
devices/platform/i2c-gpio/i2c-0/0-0070/chan-4(=>...i2c-5)/5-0071/chan-1(=>...i2c-10)
devices/platform/i2c-gpio/i2c-0/0-0070/chan-4(=>...i2c-5)/5-0071/chan-2(=>...i2c-11)
devices/platform/i2c-gpio/i2c-0/0-0070/chan-4(=>...i2c-5)/5-0071/chan-3(=>...i2c-12)
Introducing links to sub-buses, named with respective channel id sounds
good for me. Beside that your link example does not reflect your ASCII
graphics of course ;-)
*COUGH...COUGH* Oh, that was on purpose... *COUGH...COUGH* so to see
whether anyone was paying attention. Good catch! :-)
Thanks!
Gerlando
--
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
