Re: [PATCH v3 1/2] staging: iio: isl29028: correct proximity sleep times

2017-04-25 Thread Jonathan Cameron
On 25/04/17 02:34, Brian Masney wrote: > The sysfs attribute in_proximity_sampling_frequency_available currently > shows the values 1 3 5 10 13 20 83 100. These values are supposed to > correspond to the sleep values 800 400 200 100 75 50 12.5 0 (all in ms). > When passing in a sampling frequency

Re: [PATCH v3 1/2] staging: iio: isl29028: correct proximity sleep times

2017-04-25 Thread Jonathan Cameron
On 25/04/17 02:34, Brian Masney wrote: > The sysfs attribute in_proximity_sampling_frequency_available currently > shows the values 1 3 5 10 13 20 83 100. These values are supposed to > correspond to the sleep values 800 400 200 100 75 50 12.5 0 (all in ms). > When passing in a sampling frequency

[PATCH v3 1/2] staging: iio: isl29028: correct proximity sleep times

2017-04-24 Thread Brian Masney
The sysfs attribute in_proximity_sampling_frequency_available currently shows the values 1 3 5 10 13 20 83 100. These values are supposed to correspond to the sleep values 800 400 200 100 75 50 12.5 0 (all in ms). When passing in a sampling frequency of 3, it actually uses a sleep time of 200ms

[PATCH v3 1/2] staging: iio: isl29028: correct proximity sleep times

2017-04-24 Thread Brian Masney
The sysfs attribute in_proximity_sampling_frequency_available currently shows the values 1 3 5 10 13 20 83 100. These values are supposed to correspond to the sleep values 800 400 200 100 75 50 12.5 0 (all in ms). When passing in a sampling frequency of 3, it actually uses a sleep time of 200ms