Re: [PATCH 0/4] iio: light: vl6180: Several fixes and enhancements

2017-09-24 Thread Jonathan Cameron
On Tue, 19 Sep 2017 05:11:40 +0200 Stefan Brüns wrote: > Currently, the vl6180 driver reports bogus in_illuminance_scale values > when the integration time or hardware gain are changed from its default > value, i.e. it always reports a fixed value. > > To avoid

Re: [PATCH 0/4] iio: light: vl6180: Several fixes and enhancements

2017-09-24 Thread Jonathan Cameron
On Tue, 19 Sep 2017 05:11:40 +0200 Stefan Brüns wrote: > Currently, the vl6180 driver reports bogus in_illuminance_scale values > when the integration time or hardware gain are changed from its default > value, i.e. it always reports a fixed value. > > To avoid readback of the register values

[PATCH 0/4] iio: light: vl6180: Several fixes and enhancements

2017-09-18 Thread Stefan Brüns
Currently, the vl6180 driver reports bogus in_illuminance_scale values when the integration time or hardware gain are changed from its default value, i.e. it always reports a fixed value. To avoid readback of the register values in case integration time, gain or scale is queried, save the

[PATCH 0/4] iio: light: vl6180: Several fixes and enhancements

2017-09-18 Thread Stefan Brüns
Currently, the vl6180 driver reports bogus in_illuminance_scale values when the integration time or hardware gain are changed from its default value, i.e. it always reports a fixed value. To avoid readback of the register values in case integration time, gain or scale is queried, save the