From: Andreas Klinger <ak@it-klinger.de>
To: Jonathan Cameron <jic23@kernel.org>
Cc: knaack.h@gmx.de, lars@metafoo.de, pmeerw@pmeerw.net,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
ktsai@capellamicro.com, wsa@the-dreams.de, robh+dt@kernel.org,
pawel.moll@arm.com, mark.rutland@arm.com,
ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
trivial@kernel.org, mranostay@gmail.com,
linux-i2c@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v3 3/3] iio: distance: srf08: add driver ABI documentation
Date: Sun, 22 Jan 2017 21:41:10 +0100 [thread overview]
Message-ID: <20170122204110.GA1840@andreas> (raw)
In-Reply-To: <2e87aeed-a611-e160-c245-f5b16f2ef304@kernel.org>
Hi Jonathan,
see question below.
Andreas
Jonathan Cameron <jic23@kernel.org> schrieb am Sun, 22. Jan 13:41:
> On 17/01/17 13:50, Andreas Klinger wrote:
> > Add sysfs-bus-iio-distance-srf08 for individual attributes of the driver,
> > especially:
> > - sensitivity which the device documentation calls gain for amplifying the
> > signal
> > - max_range for limiting the maximum distance for expected echos and
> > therefore limiting the time waiting for telegrams
> >
> > Signed-off-by: Andreas Klinger <ak@it-klinger.de>
> > ---
> > .../ABI/testing/sysfs-bus-iio-distance-srf08 | 27 ++++++++++++++++++++++
> > 1 file changed, 27 insertions(+)
> > create mode 100644 Documentation/ABI/testing/sysfs-bus-iio-distance-srf08
> >
> > diff --git a/Documentation/ABI/testing/sysfs-bus-iio-distance-srf08 b/Documentation/ABI/testing/sysfs-bus-iio-distance-srf08
> > new file mode 100644
> > index 000000000000..e96c28064748
> > --- /dev/null
> > +++ b/Documentation/ABI/testing/sysfs-bus-iio-distance-srf08
> > @@ -0,0 +1,27 @@
> > +What /sys/bus/iio/devices/iio:deviceX/in_distance_raw
> > +Date: January 2017
> > +KernelVersion: 4.11
> > +Contact: linux-iio@vger.kernel.org
> > +Description:
> > + Get the current distance in meters between the sensor and
> > + the first object recognized
> Generally no need to document what are effectively standard elements.
> Just leads to the possibility of disagreements in the docs!
> Still no harm here really.
> > +
> > +What /sys/bus/iio/devices/iio:deviceX/sensor_sensitivity
> > +Date: January 2017
> > +KernelVersion: 4.11
> > +Contact: linux-iio@vger.kernel.org
> > +Description:
> > + Show or set the gain boost of the amp, from 0-31 range.
> > + default 31
> > +
> > +What /sys/bus/iio/devices/iio:deviceX/sensor_max_range
> > +Date: January 2017
> > +KernelVersion: 4.11
> > +Contact: linux-iio@vger.kernel.org
> > +Description:
> > + Show or set the maximum range between the sensor and the
> > + first object echoed in millimeters.
> > + This setting limits the time the driver is waiting for a
> > + echo.
> > + Can be set between 43 and 11008 in a grid of 43 mm.
> > + default 6020
> This needs to be in the same units as the range - so m.
Just to clarify:
There should be a floating point number be passed to the driver and being parsed
there, e. g.:
0.043 or 6.020
right?
Or should this number be passed using the scale attribute like the raw value
does? So that the scale is used by both the value itself and the attribute.
> I'm not 100% sure this is the best ABI we can do for this. However, supporting
> this as a legacy abi if we come up with something more general will be a very
> small burden, so lets not stall the driver on this!
>
> Jonathan
> >
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-iio" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
next prev parent reply other threads:[~2017-01-22 20:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-17 13:50 [PATCH v3 3/3] iio: distance: srf08: add driver ABI documentation Andreas Klinger
2017-01-22 13:41 ` Jonathan Cameron
2017-01-22 20:41 ` Andreas Klinger [this message]
2017-01-22 22:11 ` Jonathan Cameron
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170122204110.GA1840@andreas \
--to=ak@it-klinger.de \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=jic23@kernel.org \
--cc=knaack.h@gmx.de \
--cc=ktsai@capellamicro.com \
--cc=lars@metafoo.de \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mranostay@gmail.com \
--cc=pawel.moll@arm.com \
--cc=pmeerw@pmeerw.net \
--cc=robh+dt@kernel.org \
--cc=trivial@kernel.org \
--cc=wsa@the-dreams.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).