Honored Contributor
Honored Contributor<div class='quotetop'>QUOTE (mschnell @ Aug 5 2009, 03:19 PM) <{post_snapback}> (index.php?act=findpost&pid=23416)</div>
--- Quote Start --- <div class='quotetop'>QUOTE (hippo @ Aug 5 2009, 04:29 AM) <{post_snapback}> (index.php?act=findpost&pid=23414) --- Quote End --- --- Quote Start --- I have ds1307/ds1338 worked on NEEK. Please see the wiki, http://www.nioswiki.com/gpio (http://www.nioswiki.com/gpio)[/b] --- Quote End --- - Is there a cause why, on the NEEK hardware, bit baning on a GPIO port is implemented instead of using some I²C ipCore ? - Does this I²C interface-driver support an I²C "subsystem" so that I²C "chip driver" Kernel modules can be created that use these hardware pins as a common bus for multiple different I²C enabled chips ? -Michael [/b] --- Quote End --- GPIO is simple, low LE count and easy to debug. Bit banging i2c is used on almost every PC. Unless you will have high i2c traffic, gpio i2c is the better choice in term of LE usage. There is no difference in 2c chip drivers, other than the the low level interface. You can have multiple i2c devices on a i2c bus. Each device usually have wired i2c address. On neek, there are three independent i2c buses. Beside kernel i2c chip drivers, user space drivers through /dev/i2c-x are also supported, such as i2c-tools utility. Cheer, Hippo
