From: Antoniu Miclaus <antoniu.miclaus@analog.com>
To: "Marcelo Schmitt" <marcelo.schmitt@analog.com>,
"Antoniu Miclaus" <antoniu.miclaus@analog.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Michael Hennerich" <Michael.Hennerich@analog.com>,
"Jonathan Cameron" <jic23@kernel.org>,
"David Lechner" <dlechner@baylibre.com>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
linux-iio@vger.kernel.org, linux@analog.com,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v3 0/4] iio: accel: adxl367: add INT2 interrupt pin support
Date: Fri, 21 Aug 2026 21:07:49 +0300 [thread overview]
Message-ID: <20260821180753.4633-1-antoniu.miclaus@analog.com> (raw)
The ADXL367 exposes two independent interrupt output pins, INT1 and INT2,
each with its own event mapping register. The driver has always hardcoded
INT1, so a board that routes only INT2 to the host never receives
interrupts. This series lets the driver pick the interrupt map register
based on the interrupt-names device tree property.
v3 addresses review feedback on the driver patch: the interrupt number
returned by fwnode_irq_get_byname() is now used for the request, so the
requested line always matches the routed INTMAP register even if the
interrupts are listed in an unexpected order. A precursor patch converts
the existing regmap_update_bits(..., en ? mask : 0) helpers to
regmap_assign_bits() as suggested during review.
Changes in v3:
- New precursor patch converting the boolean regmap_update_bits() helpers
to regmap_assign_bits().
- Use the fwnode_irq_get_byname() interrupt number for
devm_request_threaded_irq() in the INT2 patch.
- Rebased on the latest togreg/testing.
Antoniu Miclaus (4):
dt-bindings: iio: update unreachable maintainer entries
dt-bindings: iio: accel: adi,adxl367: add interrupt-names
iio: accel: adxl367: use regmap_assign_bits()
iio: accel: adxl367: add support for INT2 interrupt pin
.../bindings/iio/accel/adi,adxl367.yaml | 13 ++++-
.../bindings/iio/adc/adi,ad4130.yaml | 3 +-
.../bindings/iio/addac/adi,ad74115.yaml | 3 +-
.../bindings/iio/addac/adi,ad74413r.yaml | 3 +-
MAINTAINERS | 4 ++
drivers/iio/accel/adxl367.c | 47 +++++++++++++++----
6 files changed, 60 insertions(+), 13 deletions(-)
base-commit: 350d1fb9204b13c5f95e511e98b8bcb47574d425
--
2.43.0
next reply other threads:[~2026-08-21 18:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-21 18:07 Antoniu Miclaus [this message]
2026-08-21 18:07 ` [PATCH v3 1/4] dt-bindings: iio: update unreachable maintainer entries Antoniu Miclaus
2026-08-23 18:45 ` Jonathan Cameron
2026-08-24 12:00 ` Marcelo Schmitt
2026-08-21 18:07 ` [PATCH v3 2/4] dt-bindings: iio: accel: adi,adxl367: add interrupt-names Antoniu Miclaus
2026-08-21 18:07 ` [PATCH v3 3/4] iio: accel: adxl367: use regmap_assign_bits() Antoniu Miclaus
2026-08-24 12:19 ` Marcelo Schmitt
2026-08-21 18:07 ` [PATCH v3 4/4] iio: accel: adxl367: add support for INT2 interrupt pin Antoniu Miclaus
2026-08-22 19:07 ` David Lechner
2026-08-23 18:43 ` 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=20260821180753.4633-1-antoniu.miclaus@analog.com \
--to=antoniu.miclaus@analog.com \
--cc=Michael.Hennerich@analog.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@analog.com \
--cc=marcelo.schmitt@analog.com \
--cc=nuno.sa@analog.com \
--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