From: Arnaud Ferraris <arnaud.ferraris@collabora.com>
To: Jonathan Cameron <jic23@kernel.org>,
Lars-Peter Clausen <lars@metafoo.de>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>
Cc: linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, kernel@collabora.com
Subject: [PATCH v2 0/2] iio: stk3310: Export near level property for proximity sensor
Date: Wed, 20 Apr 2022 13:25:38 +0200 [thread overview]
Message-ID: <20220420112540.91907-1-arnaud.ferraris@collabora.com> (raw)
Userspace tools like iio-sensor-proxy need to be instructed the value from
which they should consider an object is "near". This threshold can be
exported through the sysfs ABI based on the "proximity-near-level"
device-tree property.
This patchset implements this property for the stk3310 driver and adds the
necessary bits to export its value to userspace. It is based on similar
changes applied to the vcnl4000 and ltr501 drivers.
Changes in v2:
- drop zero-assignment as the variable won't be modified if DT property
is missing
Arnaud Ferraris (2):
dt-bindings: iio: light: stk33xx: Add proximity-near-level
iio: stk3310: Export near level property for proximity sensor
.../bindings/iio/light/stk33xx.yaml | 6 +++++
drivers/iio/light/stk3310.c | 25 +++++++++++++++++++
2 files changed, 31 insertions(+)
--
2.35.1
next reply other threads:[~2022-04-20 11:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-20 11:25 Arnaud Ferraris [this message]
2022-04-20 11:25 ` [PATCH v2 1/2] dt-bindings: iio: light: stk33xx: Add proximity-near-level Arnaud Ferraris
2022-04-21 7:30 ` Krzysztof Kozlowski
2022-04-20 11:25 ` [PATCH v2 2/2] iio: stk3310: Export near level property for proximity sensor Arnaud Ferraris
2022-04-24 16:57 ` [PATCH v2 0/2] " 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=20220420112540.91907-1-arnaud.ferraris@collabora.com \
--to=arnaud.ferraris@collabora.com \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=kernel@collabora.com \
--cc=krzk+dt@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
/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).