Re: [PATCHv2 2/2] iio: dht11: Use new function ktime_get_resolution_ns()

2015-04-09 Thread Jonathan Cameron
On 07/04/15 12:12, Harald Geyer wrote: > This cleans up the most ugly workaround in this driver. There are no > functional changes yet in the decoding algorithm, but we improve the > following things: > * Get rid of spurious warning messages on systems with fast HRTIMER. > * If the clock is not

Re: [PATCHv2 2/2] iio: dht11: Use new function ktime_get_resolution_ns()

2015-04-09 Thread Jonathan Cameron
On 07/04/15 12:12, Harald Geyer wrote: This cleans up the most ugly workaround in this driver. There are no functional changes yet in the decoding algorithm, but we improve the following things: * Get rid of spurious warning messages on systems with fast HRTIMER. * If the clock is not fast

[PATCHv2 2/2] iio: dht11: Use new function ktime_get_resolution_ns()

2015-04-07 Thread Harald Geyer
This cleans up the most ugly workaround in this driver. There are no functional changes yet in the decoding algorithm, but we improve the following things: * Get rid of spurious warning messages on systems with fast HRTIMER. * If the clock is not fast enough for decoding to work, we give up

[PATCHv2 2/2] iio: dht11: Use new function ktime_get_resolution_ns()

2015-04-07 Thread Harald Geyer
This cleans up the most ugly workaround in this driver. There are no functional changes yet in the decoding algorithm, but we improve the following things: * Get rid of spurious warning messages on systems with fast HRTIMER. * If the clock is not fast enough for decoding to work, we give up