soc:2017:portrpi
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | Last revision Both sides next revision | ||
|
soc:2017:portrpi [2017/08/28 03:27] nekorobov [Current Status] |
soc:2017:portrpi [2017/08/28 12:00] nekorobov [The I2C driver] |
||
|---|---|---|---|
| Line 54: | Line 54: | ||
| ====The I2C driver==== | ====The I2C driver==== | ||
| - | The new I2C driver is similar with the previous drivers, because the MINIX has the I2C stack, which requires definition of specific functions. The RPI may be as slave or master, but the current version of I2C driver supports only the master mode. It supports the 7 and 10 bits address. Plan - how to add the new I2C driver was added to the README. It's very simple, because the I2C stack was created as portable driver. | + | The new I2C driver is similar with the previous drivers, because the MINIX has the I2C stack, which requires definition of specific functions. The RPI may be as slave or master, but the current version of I2C driver supports only the master mode. It supports the 7 and 10 bits address. Plan - how to add the new I2C driver was added to the README. It's very simple, because the I2C stack was created as portable driver.\\ |
| + | |||
| + | The RPI bus can't generate repeated start bit. It's bit which hardware generate instead of stop bit after the write command transmission, this bit is followed by read transaction. It's a big missing of the Broadcom, cause we can't read from the device's register, because many devices, which uses I2C require repeated start bit. There are exist software methods how work around it, but it may be in race condition, thus these methods are unreliable. | ||
| ====The PCM driver==== | ====The PCM driver==== | ||
soc/2017/portrpi.txt · Last modified: 2017/08/28 14:45 by lionelsambuc
