Thank You for answering my question! And, yes, that’s what's I meant ― access I2C bus from kernel driver rather than userspace.
Hay On 6/24/15, 9:59 AM, "Darren Hart" <[email protected]> wrote: > >On 6/18/15, 1:53 PM, "Hay Nguonly" <[email protected]> wrote: >>Hi, >> >>I¹m look for some help on using I2C adapter in kernel mode. >>I plan to access I2C bus in kernel mode and wanted to know the adapter >>number associated to the I2C signal on the Minnow Max board. > >What do you mean by "kernel mode" - as in through a device kernel driver >rather than userspace IOCTL calls? > >> >>There are two I2C buses: >> >>I2C (#5) pin #13 and #15 (Low Speed Expansion top) >>I2C (#6) pin #21 and #23 (High Speed Expansion - bottom) >> >>Which one should I be using? >>Is there a reason for using one vs the other? > >The buses are equivalent for all intents and purposes. Use the one on the >port that fits your application best. If you don't require any of the high >speed signals, the low speed expansion port is more accessible and easier >to prototype with. > >-- >Darren Hart >Intel Open Source Technology Center > > >_______________________________________________ >elinux-MinnowBoard mailing list >[email protected] >http://lists.elinux.org/mailman/listinfo/elinux-minnowboard _______________________________________________ elinux-MinnowBoard mailing list [email protected] http://lists.elinux.org/mailman/listinfo/elinux-minnowboard
