Re: FW: [PATCH 10/16] i2c-designware: Do dw_i2c_pump_msg's jobs in the interrutp handler

2009-10-13 Thread Ben Dooks
...@tkos.co.il; linux-i2c@vger.kernel.org > Cc: ben-li...@fluff.org; linux-m...@linux-mips.org; > linux-arm-ker...@lists.infradead.org > Subject: [PATCH 10/16] i2c-designware: Do dw_i2c_pump_msg's jobs in the > interrutp handler Please don't forward patches to the list we

FW: [PATCH 10/16] i2c-designware: Do dw_i2c_pump_msg's jobs in the interrutp handler

2009-10-13 Thread Olivares, Ricardo Perez
...@lists.infradead.org Subject: [PATCH 10/16] i2c-designware: Do dw_i2c_pump_msg's jobs in the interrutp handler Symptom: When we're going to send/receive the data with bigger size than the Tx FIFO length, the I2C transaction will be divided into several separated transaction

FW: [PATCH 10/16] i2c-designware: Do dw_i2c_pump_msg's jobs in the interrutp handler

2009-10-13 Thread Olivares, Ricardo Perez
...@lists.infradead.org Subject: [PATCH 10/16] i2c-designware: Do dw_i2c_pump_msg's jobs in the interrutp handler Symptom: When we're going to send/receive the data with bigger size than the Tx FIFO length, the I2C transaction will be divided into several separated transaction

FW: [PATCH 10/16] i2c-designware: Do dw_i2c_pump_msg's jobs in the interrutp handler

2009-10-13 Thread Olivares, Ricardo Perez
...@lists.infradead.org Subject: [PATCH 10/16] i2c-designware: Do dw_i2c_pump_msg's jobs in the interrutp handler Symptom: When we're going to send/receive the data with bigger size than the Tx FIFO length, the I2C transaction will be divided into several separated transaction

[PATCH 10/16] i2c-designware: Do dw_i2c_pump_msg's jobs in the interrutp handler

2009-10-12 Thread Shinya Kuribayashi
Symptom: When we're going to send/receive the data with bigger size than the Tx FIFO length, the I2C transaction will be divided into several separated transactions, limited by the Tx FIFO length. Details: As a hardware feature, DesignWare I2C core emits a STOP condition wheneve