diff options
| author | Jonathan Cameron <jic23@kernel.org> | 2013-03-24 16:58:00 +0000 |
|---|---|---|
| committer | Jonathan Cameron <jic23@kernel.org> | 2013-04-02 18:36:24 +0100 |
| commit | aa9922579fee20ac4f2bb959a79bbfbff2c04585 (patch) | |
| tree | ccbd00def5fc4076f4c46a95181b4ad78f9c95c6 /drivers/staging/iio | |
| parent | dea120e665712a9be41a6c846e73c6af19e00af7 (diff) | |
staging:iio:magnetometer:ak8975 drop I2C_M_NOSTART flag in read_data
This flag makes no sense whatsoever where it is.
Documentation/i2c/i2c-protocol states:
If you set the I2C_M_NOSTART variable for the first partial message,
we do not generate Addr, but we do generate the startbit S. This will
probably confuse all other clients on your bus, so don't try this.
This is exactly what is going on here. Likelihood given that the
driver never checked for this protocol mangling being available is that
it wasn't present on the test boards and hence this flag was simply
ignored. No indication of why it would be necessary has been found in
the datasheets.
Signed-off-by: Jonathan Cameron <jic23@kernel.org>
Acked-by: Laxman Dewangan <ldewangan@nvidia.com>
Diffstat (limited to 'drivers/staging/iio')
| -rw-r--r-- | drivers/staging/iio/magnetometer/ak8975.c | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/drivers/staging/iio/magnetometer/ak8975.c b/drivers/staging/iio/magnetometer/ak8975.c index 8726ea1de08..1428849fd5a 100644 --- a/drivers/staging/iio/magnetometer/ak8975.c +++ b/drivers/staging/iio/magnetometer/ak8975.c @@ -132,7 +132,6 @@ static int ak8975_read_data(struct i2c_client *client, struct i2c_msg msg[2] = { { .addr = client->addr, - .flags = I2C_M_NOSTART, .len = 1, .buf = ®, }, { |