i2c: s3c2410: Add SMBus emulation for block read
Subsystems (2)
PATCH 1/1 i2c: s3c2410: Add SMBus emulation for block read
From: Jaemin Yoo <[email protected]>
SMBus read and write are supported by the emulation layer of i2c framework if the controller doesn't have SMBus features.
I2C_M_RECV_LEN flag is used to let i2c drivers know rx length is not yet determined but will be read to the first byte in rx buffer.
s3c2410 doesn't handle this flag. So only one byte is read from slave. There fore following two features are added to the driver code.
1. skip rx length check if I2C_M_RECV_LEN is set and the length is 1.
2. add actual bytes to the rx length after reading first bytes if I2C_M_RECV_LEN.
I2C_M_RECV_LEN is only set for SMBus command. So this code does not affect legacy codes which only use i2c command for s3c2410.
--- drivers/i2c/busses/i2c-s3c2410.c | 9 +++++++++ 1 file changed, 9 insertions(+)
drivers/i2c/busses/i2c-s3c2410.c +9 -0
@@ -309,6 +309,12 @@ static inline int is_lastmsg(struct s3c24xx_i2c *i2c)static inline int is_msglast (struct s3c24xx_i2c *i2c) { +/* msg->len is always 1 for the first byte of smbus block read. +* Actual length will be read from slave. More bytes will be +* read according to the length then. */ +if (i2c->msg->flags &I2C_M_RECV_LEN && i2c->msg->len ==1 ) +return 0 ; +return i2c->msg_ptr == i2c->msg->len-1 ; }
@@ -448,6 +454,9 @@ static int i2c_s3c_irq_nextbyte(struct s3c24xx_i2c *i2c, unsigned long iicstat) byte =readb (i2c->regs +S3C2410_IICDS ); i2c->msg->buf[i2c->msg_ptr++] = byte; +/* Add actual length to read for smbus block read */ +if (i2c->msg->flags &I2C_M_RECV_LEN && i2c->msg->len ==1 ) + i2c->msg->len += byte; prepare_read:if (is_msglast (i2c)) {/* last byte of buffer */
Signature · 1 line
1.7.10.4
Wolfram Sang
AppliedPATCH 1/1 i2c: s3c2410: Add SMBus emulation for block read
Quoted 15 lines · Prasanna Kumar
From: Jaemin Yoo <[email protected]>
SMBus read and write are supported by the emulation layer of i2c framework if the controller doesn't have SMBus features.
I2C_M_RECV_LENflag is used to let i2c drivers know rx length is not yet determined but will be read to the first byte in rx buffer.s3c2410 doesn't handle this flag. So only one byte is read from slave. There fore following two features are added to the driver code.
1. skip rx length check if
I2C_M_RECV_LENis set and the length is 1.
2. add actual bytes to the rx length after reading first bytes ifI2C_M_RECV_LEN.
Quoted 5 lines
I2C_M_RECV_LENis only set for SMBus command. So this code does not affect legacy codes which only use i2c command for s3c2410.Signed-off-by Jaemin Yoo <[email protected]>Tested-by Prasanna Kumar <[email protected]>
Applied to for-next, thanks!
PATCH 1/1 i2c: s3c2410: Add SMBus emulation for block read
In reply to Prasanna KumarHello,
Quoted 18 lines · Prasanna Kumar
drivers/i2c/busses/i2c-s3c2410.c +6
-0@@ -309,6 +309,12 @@ static inline int is_lastmsg(struct s3c24xx_i2c *i2c)static inline int is_msglast (struct s3c24xx_i2c *i2c) { +/* msg->len is always 1 for the first byte of smbus block read. +* Actual length will be read from slave. More bytes will be +* read according to the length then. */ +if (i2c->msg->flags &I2C_M_RECV_LEN && i2c->msg->len ==1 ) +return 0 ; +return i2c->msg_ptr == i2c->msg->len-1 ; }
drivers/i2c/busses/i2c-s3c2410.c static int i2c_s3c_irq_nextbyte(struct s3c24xx_i2c *i2c, unsigned long iicstat) · line 461
Quoted 8 lines
drivers/i2c/busses/i2c-s3c2410.c +3
-0@@ -448,6 +454,9 @@ static int i2c_s3c_irq_nextbyte(struct s3c24xx_i2c *i2c, unsigned long iicstat) byte =readb (i2c->regs +S3C2410_IICDS ); i2c->msg->buf[i2c->msg_ptr++] = byte; +/* Add actual length to read for smbus block read */ +if (i2c->msg->flags &I2C_M_RECV_LEN && i2c->msg->len ==1 ) + i2c->msg->len += byte; prepare_read:if (is_msglast (i2c)) {
I don't know if that can happen, but if the block has length 0 (that is, only consists of a single byte that is read as 0) the is_msglast() test returns 0 which might be wrong. Maybe even if it cannot regularily happen handle it in a sane way?
Also I wonder if error checking for byte > I2C_SMBUS_BLOCK_MAX would be needed to prevent a buffer overrun?
Best regards
Uwe
Signature · 2 lines
Pengutronix e.K. | Uwe Kleine-K?nig | Industrial Linux Solutions | http://www.pengutronix.de/ |
PATCH 1/1 i2c: s3c2410: Add SMBus emulation for block read
Quoted 5 lines
I don't know if that can happen, but if the block has length 0 (that is, only consists of a single byte that is read as 0) the
is_msglast()test returns 0 which might be wrong. Maybe even if it cannot regularily happen handle it in a sane way?
Length of 0 is illegal according to the specs, but a check won't hurt.
Quoted 2 lines
Also I wonder if error checking for byte >
I2C_SMBUS_BLOCK_MAXwould be needed to prevent a buffer overrun?
Yes. Although I have seen devices able to send more than that, yet adding support for that is a seperate issue.