lkml.org 
[lkml]   [2015]   [Jun]   [16]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH 1/2] iio: ABI: Clarify proximity output value
Hello,

> Current description for proximity measurement is ambiguous. While
> the first part says that proximity is measured by observing
> reflectivity, the second part incorrectly infers that reported values
> should behave like a distance.
>
> This is because of AS3935 lightning sensor which uses the proximity
> API, while not being a true proximity sensor.

Acked-by: Peter Meerwald <pmeerw@pmeerw.net>

> Fixes: 614e8842ddf ("iio: ABI: add clarification for proximity")
> Signed-off-by: Daniel Baluta <daniel.baluta@intel.com>
> ---
> Documentation/ABI/testing/sysfs-bus-iio | 6 ++----
> 1 file changed, 2 insertions(+), 4 deletions(-)
>
> diff --git a/Documentation/ABI/testing/sysfs-bus-iio b/Documentation/ABI/testing/sysfs-bus-iio
> index bbed111..70c9b1a 100644
> --- a/Documentation/ABI/testing/sysfs-bus-iio
> +++ b/Documentation/ABI/testing/sysfs-bus-iio
> @@ -1234,10 +1234,8 @@ Description:
> object is near the sensor, usually be observing

> reflectivity of infrared or ultrasound emitted.
> Often these sensors are unit less and as such conversion
> - to SI units is not possible. Where it is, the units should
> - be meters. If such a conversion is not possible, the reported
> - values should behave in the same way as a distance, i.e. lower
> - values indicate something is closer to the sensor.
> + to SI units is not possible. Higher proximity measurements
> + indicate closer objects, and vice versa.
>
> What: /sys/.../iio:deviceX/in_illuminance_input
> What: /sys/.../iio:deviceX/in_illuminance_raw
>

--

Peter Meerwald
+43-664-2444418 (mobile)


\
 
 \ /
  Last update: 2015-06-16 23:21    [W:0.096 / U:0.176 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site