On 29 July 2015 at 23:39, Hartmut Knaack <knaack.h@xxxxxx> wrote: > Revision 1.2 of the datasheet recommends on page 22 to only write non-zero > values read from OTP register 0x70 into AFECTRL register. > > Signed-off-by: Hartmut Knaack <knaack.h@xxxxxx> > Reviewed-by: Tiberiu Breana <tiberiu.a.breana@xxxxxxxxx> > --- > drivers/iio/accel/stk8312.c | 2 ++ > 1 file changed, 2 insertions(+) > > diff --git a/drivers/iio/accel/stk8312.c b/drivers/iio/accel/stk8312.c > index c2bd1444d6da..6592be8e6377 100644 > --- a/drivers/iio/accel/stk8312.c > +++ b/drivers/iio/accel/stk8312.c > @@ -150,6 +150,8 @@ static int stk8312_otp_init(struct stk8312_data *data) > goto exit_err; > > ret = i2c_smbus_read_byte_data(client, STK8312_REG_OTPDATA); > + if (ret == 0) > + ret = -EINVAL; This seems fishy. We have a macro value written to client which cannot really give us EINVAL, except if we are checking the client, but then this would only fail if we had some other i2c device on the line with stk8312 address, which would ack other i2c commands above this. > if (ret < 0) > goto exit_err; > > -- > 2.4.6 > > -- > To unsubscribe from this list: send the line "unsubscribe linux-iio" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe linux-iio" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
