From: Jonathan Cameron <jic23@kernel.org>
To: "Guido Günther" <agx@sigxcpu.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,
devicetree@vger.kernel.org,
Andy Shevchenko <andy.shevchenko@gmail.com>,
Nishant Malpani <nish.malpani25@gmail.com>
Subject: Re: [PATCH v4 4/5] iio: vcnl4000: Export near level property for proximity sensor
Date: Sat, 18 Apr 2020 19:05:08 +0100 [thread overview]
Message-ID: <20200418190508.49cc05ee@archlinux> (raw)
In-Reply-To: <cfd5373665c4d314764c4dbe20b55de14fb6ba34.1586094535.git.agx@sigxcpu.org>
On Sun, 5 Apr 2020 15:50:31 +0200
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>
Applied. Thanks,
> ---
> drivers/iio/light/vcnl4000.c | 25 +++++++++++++++++++++++++
> 1 file changed, 25 insertions(+)
>
> diff --git a/drivers/iio/light/vcnl4000.c b/drivers/iio/light/vcnl4000.c
> index ec803c1e81df..985cc39ede8e 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 {
> @@ -343,6 +344,25 @@ 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 = "nearlevel",
> + .shared = IIO_SEPARATE,
> + .read = vcnl4000_read_near_level,
> + },
> + { /* sentinel */ }
> +};
> +
> static const struct iio_chan_spec vcnl4000_channels[] = {
> {
> .type = IIO_LIGHT,
> @@ -351,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,
> }
> };
>
> @@ -440,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, "proximity-near-level",
> + &data->near_level))
> + 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-04-18 18:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-05 13:50 [PATCH v4 0/5] iio: vcnl4000: Export near level property for proximity sensor Guido Günther
2020-04-05 13:50 ` [PATCH v4 1/5] dt-bindings: iio: vcnl4000: convert bindings to YAML format Guido Günther
2020-04-05 13:50 ` [PATCH v4 2/5] dt-bindings: iio: Introduce common properties for iio sensors Guido Günther
2020-04-12 11:28 ` Jonathan Cameron
2020-04-14 21:49 ` Rob Herring
2020-04-18 18:03 ` Jonathan Cameron
2020-04-05 13:50 ` [PATCH v4 3/5] dt-bindings: iio: light: vcnl4000: Add proximity-near-level Guido Günther
2020-04-14 21:50 ` Rob Herring
2020-04-18 18:04 ` Jonathan Cameron
2020-04-05 13:50 ` [PATCH v4 4/5] iio: vcnl4000: Export near level property for proximity sensor Guido Günther
2020-04-18 18:05 ` Jonathan Cameron [this message]
2020-04-05 13:50 ` [PATCH v4 5/5] Documentation: ABI: document IIO in_proximity_nearlevel file Guido Günther
2020-04-18 18:06 ` 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=20200418190508.49cc05ee@archlinux \
--to=jic23@kernel.org \
--cc=agx@sigxcpu.org \
--cc=andy.shevchenko@gmail.com \
--cc=angus@akkea.ca \
--cc=devicetree@vger.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=nish.malpani25@gmail.com \
--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).