summaryrefslogtreecommitdiff
path: root/doc/README.sh
diff options
context:
space:
mode:
authorShaveta Leekha <shaveta@freescale.com>2014-04-24 14:51:23 +0530
committerHeiko Schocher <hs@denx.de>2014-04-29 07:10:58 +0200
commita405764c1ec835a41ccda943b9156aee25e15d5e (patch)
tree9a54a9bd16b888e3c6f95f30090afbb36133868e /doc/README.sh
parentdec1861be90c948ea9fb771927d3d26a994d2e20 (diff)
downloadu-boot-imx-a405764c1ec835a41ccda943b9156aee25e15d5e.zip
u-boot-imx-a405764c1ec835a41ccda943b9156aee25e15d5e.tar.gz
u-boot-imx-a405764c1ec835a41ccda943b9156aee25e15d5e.tar.bz2
drivers/i2c/fsl_i2c: modify i2c_read to handle multi-byte write
Most of the I2C slaves support accesses in the typical style that is : read/write series of bytes at particular address offset. These transactions look like:" (1) START:Address:Tx:Offset:RESTART:Address[0..4]:Tx/Rx:data[0..n]:STOP" However there are certain devices which support accesses in terms of the transactions as follows: (2) "START:Address:Tx:Txdata[0..n1]:Clock_stretching: RESTART:Address:Rx:data[0..n2]" Here Txdata is typically a command and some associated data, similarly Rxdata could be command status plus some data received as a response to the command sent. Type (1) transactions are currently supportd in the i2c driver using i2c_read and i2c_write APIs. I2C EEPROMs, RTC, etc fall in this category. To handle type (2) along with type (1) transactions, i2c_read() function has been modified. Signed-off-by: Shaveta Leekha <shaveta@freescale.com> Signed-off-by: Poonam Aggrwal <poonam.aggrwal@freescale.com>
Diffstat (limited to 'doc/README.sh')
0 files changed, 0 insertions, 0 deletions