From: "Guido Günther" <agx@sigxcpu.org>
To: Jonathan Cameron <jic23@kernel.org>
Cc: Tomas Novotny <tomas@novotny.cz>,
Hartmut Knaack <knaack.h@gmx.de>,
Lars-Peter Clausen <lars@metafoo.de>,
Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
"Angus Ainslie (Purism)" <angus@akkea.ca>,
Marco Felsch <m.felsch@pengutronix.de>,
Thomas Gleixner <tglx@linutronix.de>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] iio: vcnl4000: Export near level property for proximity sensor
Date: Mon, 16 Mar 2020 18:47:20 +0100 [thread overview]
Message-ID: <20200316174720.GA188762@bogon.m.sigxcpu.org> (raw)
In-Reply-To: <20200221120519.43b72007@archlinux>
Hi,
On Fri, Feb 21, 2020 at 12:05:19PM +0000, Jonathan Cameron wrote:
> On Mon, 17 Feb 2020 14:44:47 +0100
> Guido Günther <agx@sigxcpu.org> wrote:
>
> > When an object can be considered close to the sensor is hardware
> > dependent. Allowing to configure the property via device tree
> > allows to configure this device specific value.
> >
> > This is useful for e.g. iio-sensor-proxy to indicate to userspace
> > if an object is close to the sensor.
> >
> > Signed-off-by: Guido Günther <agx@sigxcpu.org>
>
> I'd like this to sit for a while on the mailing list and hopefully get
> some input from others.
>
> However, it needs documentation and I think this should be in the
> generic docs, or at least proximity specific ones.
>
> Documentation/ABI/testing/sysfs-bus-iio-proximity would be the obvious
> place.
Makes sense, i left that out to gather initial feedback but added the
docs and converted the bindings to yaml for v2.
Cheers,
-- Guido
>
> Thanks,
>
> Jonathan
>
> > ---
> > drivers/iio/light/vcnl4000.c | 26 ++++++++++++++++++++++++++
> > 1 file changed, 26 insertions(+)
> >
> > diff --git a/drivers/iio/light/vcnl4000.c b/drivers/iio/light/vcnl4000.c
> > index 38fcd9a26046..7111118e0fda 100644
> > --- a/drivers/iio/light/vcnl4000.c
> > +++ b/drivers/iio/light/vcnl4000.c
> > @@ -83,6 +83,7 @@ struct vcnl4000_data {
> > struct mutex vcnl4000_lock;
> > struct vcnl4200_channel vcnl4200_al;
> > struct vcnl4200_channel vcnl4200_ps;
> > + uint32_t near_level;
> > };
> >
> > struct vcnl4000_chip_spec {
> > @@ -342,6 +343,26 @@ static const struct vcnl4000_chip_spec vcnl4000_chip_spec_cfg[] = {
> > },
> > };
> >
> > +
> > +static ssize_t vcnl4000_read_near_level(struct iio_dev *indio_dev,
> > + uintptr_t priv,
> > + const struct iio_chan_spec *chan,
> > + char *buf)
> > +{
> > + struct vcnl4000_data *data = iio_priv(indio_dev);
> > +
> > + return sprintf(buf, "%u\n", data->near_level);
> > +}
> > +
> > +static const struct iio_chan_spec_ext_info vcnl4000_ext_info[] = {
> > + {
> > + .name = "near_level",
> > + .shared = IIO_SEPARATE,
> > + .read = vcnl4000_read_near_level,
> > + },
> > + { /* sentinel */ }
> > +};
> > +
> > static const struct iio_chan_spec vcnl4000_channels[] = {
> > {
> > .type = IIO_LIGHT,
> > @@ -350,6 +371,7 @@ static const struct iio_chan_spec vcnl4000_channels[] = {
> > }, {
> > .type = IIO_PROXIMITY,
> > .info_mask_separate = BIT(IIO_CHAN_INFO_RAW),
> > + .ext_info = vcnl4000_ext_info,
> > }
> > };
> >
> > @@ -439,6 +461,10 @@ static int vcnl4000_probe(struct i2c_client *client,
> > dev_dbg(&client->dev, "%s Ambient light/proximity sensor, Rev: %02x\n",
> > data->chip_spec->prod, data->rev);
> >
> > + if (device_property_read_u32(&client->dev, "near-level",
> > + &data->near_level) < 0)
> > + data->near_level = 0;
> > +
> > indio_dev->dev.parent = &client->dev;
> > indio_dev->info = &vcnl4000_info;
> > indio_dev->channels = vcnl4000_channels;
>
next prev parent reply other threads:[~2020-03-16 17:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-17 13:44 [PATCH 0/2] iio: vcnl4000: Export near level property for proximity sensor Guido Günther
2020-02-17 13:44 ` [PATCH 1/2] " Guido Günther
2020-02-21 12:05 ` Jonathan Cameron
2020-03-16 17:47 ` Guido Günther [this message]
2020-02-17 13:44 ` [PATCH 2/2] dt-bindings: iio: light: vcnl4000: Add near-level Guido Günther
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=20200316174720.GA188762@bogon.m.sigxcpu.org \
--to=agx@sigxcpu.org \
--cc=angus@akkea.ca \
--cc=jic23@kernel.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.felsch@pengutronix.de \
--cc=pmeerw@pmeerw.net \
--cc=tglx@linutronix.de \
--cc=tomas@novotny.cz \
/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).