diff options
author | 2010-03-01 13:24:24 +0100 | |
---|---|---|
committer | 2010-03-07 22:10:09 +0000 | |
commit | ad0194e8d624df67a970a36e8ef9e61514e25553 (patch) | |
tree | 0a6ca637423c97d98599d5e17a0f5af4bd03bc39 /drivers/base/platform.c | |
parent | i2c/imx: don't add probe function to the driver struct (diff) | |
download | wireguard-linux-ad0194e8d624df67a970a36e8ef9e61514e25553.tar.xz wireguard-linux-ad0194e8d624df67a970a36e8ef9e61514e25553.zip |
i2c-pnx: fix setting start/stop condition
The start/stop condtions are set in different places repetedly in the i2c-pnx
driver. Beside in i2c_pnx_start and i2c_pnx_stop the start/stop bit are also
set during the transfer of a i2c message in the master_xmit/rcv calls. This is
wrong since we can't set the start/stop condition during the transaction of a
single message any way. As a matter of fact, the driver will sometimes set both
the start and the stop bits at one time. This can be easily reproduced by
sending a simple read request like e.g
struct i2c_msg msgs[] = {
{ addr, 0, 1, buf },
{ addr, I2C_M_RD, offset, buf }
};
While processing the first message the i2c_pnx_master_xmit will set both the
start_bit and the stop_bit, which will eventually confuse the slave.
Fixed by remove setting start/stop condition from the transmit routines.
Signed-off-by: Luotao Fu <l.fu@pengutronix.de>
Signed-off-by: Ben Dooks <ben-linux@fluff.org>
Diffstat (limited to 'drivers/base/platform.c')
0 files changed, 0 insertions, 0 deletions