From: Waqar Hameed <waqar.hameed@axis.com>
To: Jonathan Cameron <jic23@kernel.org>,
Lars-Peter Clausen <lars@metafoo.de>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>
Cc: <kernel@axis.com>, <linux-kernel@vger.kernel.org>,
<linux-iio@vger.kernel.org>, <devicetree@vger.kernel.org>
Subject: [PATCH 0/3] Add driver for Nicera D3-323-AA PIR sensor
Date: Fri, 9 May 2025 17:03:02 +0200 [thread overview]
Message-ID: <cover.1746802541.git.waqar.hameed@axis.com> (raw)
Nicera D3-323-AA is a PIR sensor for human detection. It has support for
raw data measurements and detection notification. The communication
protocol is custom made and therefore needs to be GPIO bit banged.
Previously, there has been an attempt to add a driver for this device
[1]. However, that driver was written for the wrong sub-system. `hwmon`
is clearly not a suitable framework for a proximity device.
In this series, we add a driver for support for event notification for
detections through IIO (the more appropriate sub-system!). The various
settings have been mapped to existing `sysfs` ABIs in the IIO framework.
The public datasheet [2] is quite sparse. A more detailed version can be
obtained through the company.
[1] https://lore.kernel.org/lkml/20241212042412.702044-2-Hermes.Zhang@axis.com/
[2] https://www.endrich.com/Datenbl%C3%A4tter/Sensoren/D3-323-AA_e.pdf
Waqar Hameed (3):
dt-bindings: vendor-prefixes: Add Nicera
dt-bindings: iio: proximity: Add Nicera D3-323-AA PIR sensor
iio: Add driver for Nicera D3-323-AA PIR sensor
.../iio/proximity/nicera,d3323aa.yaml | 67 ++
.../devicetree/bindings/vendor-prefixes.yaml | 2 +
drivers/iio/proximity/Kconfig | 9 +
drivers/iio/proximity/Makefile | 1 +
drivers/iio/proximity/d3323aa.c | 868 ++++++++++++++++++
5 files changed, 947 insertions(+)
create mode 100644 Documentation/devicetree/bindings/iio/proximity/nicera,d3323aa.yaml
create mode 100644 drivers/iio/proximity/d3323aa.c
base-commit: d76bb1ebb5587f66b0f8b8099bfbb44722bc08b3
--
2.39.5
next reply other threads:[~2025-05-09 15:03 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-09 15:03 Waqar Hameed [this message]
2025-05-09 15:03 ` [PATCH 2/3] dt-bindings: iio: proximity: Add Nicera D3-323-AA PIR sensor Waqar Hameed
2025-05-09 15:06 ` Krzysztof Kozlowski
2025-05-16 17:15 ` Waqar Hameed
2025-05-20 6:36 ` Krzysztof Kozlowski
2025-05-20 12:00 ` Waqar Hameed
2025-05-09 15:03 ` [PATCH 3/3] iio: Add driver for " Waqar Hameed
2025-05-11 7:57 ` Christophe JAILLET
2025-05-16 17:16 ` Waqar Hameed
2025-05-11 12:14 ` Jonathan Cameron
2025-05-16 17:16 ` Waqar Hameed
2025-05-18 17:38 ` Jonathan Cameron
2025-05-20 11:27 ` Waqar Hameed
2025-05-25 9:30 ` Jonathan Cameron
2025-05-27 14:48 ` Waqar Hameed
2025-05-31 15:10 ` Jonathan Cameron
2025-06-02 15:09 ` Waqar Hameed
2025-06-14 22:05 ` Waqar Hameed
2025-05-09 15:09 ` [PATCH 0/3] " Krzysztof Kozlowski
2025-05-16 17:14 ` Waqar Hameed
-- strict thread matches above, loose matches on Subject: below --
2025-06-14 21:56 Waqar Hameed
2025-06-14 22:09 ` Waqar Hameed
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=cover.1746802541.git.waqar.hameed@axis.com \
--to=waqar.hameed@axis.com \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=kernel@axis.com \
--cc=krzk+dt@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@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).