Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755480AbbFPUlS (ORCPT ); Tue, 16 Jun 2015 16:41:18 -0400 Received: from ns.pmeerw.net ([84.19.176.92]:56219 "EHLO pmeerw.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752280AbbFPUlG (ORCPT ); Tue, 16 Jun 2015 16:41:06 -0400 Date: Tue, 16 Jun 2015 22:41:05 +0200 (CEST) From: Peter Meerwald To: Daniel Baluta cc: jic23@kernel.org, vlad.dogaru@intel.com, tiberiu.a.breana@intel.com, knaack.h@gmx.de, lars@metafoo.de, linux-kernel@vger.kernel.org, linux-iio@vger.kernel.org Subject: Re: [PATCH 1/2] iio: ABI: Clarify proximity output value In-Reply-To: <1434037774-22081-2-git-send-email-daniel.baluta@intel.com> Message-ID: References: <1434037774-22081-1-git-send-email-daniel.baluta@intel.com> <1434037774-22081-2-git-send-email-daniel.baluta@intel.com> User-Agent: Alpine 2.02 (DEB 1266 2009-07-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1850 Lines: 47 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 > Fixes: 614e8842ddf ("iio: ABI: add clarification for proximity") > Signed-off-by: Daniel Baluta > --- > 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) -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/