From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
To: Jean-Baptiste Maneyrol via B4 Relay
<devnull+jean-baptiste.maneyrol.tdk.com@kernel.org>
Cc: <jean-baptiste.maneyrol@tdk.com>,
Jonathan Cameron <jic23@kernel.org>,
Lars-Peter Clausen <lars@metafoo.de>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, <linux-iio@vger.kernel.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] dt-bindings: iio: imu: icm42600: add interrupt naming support
Date: Fri, 4 Apr 2025 18:16:22 +0100 [thread overview]
Message-ID: <20250404181622.00006d29@huawei.com> (raw)
In-Reply-To: <20250404-iio-imu-inv-icm42600-rework-interrupt-using-names-v1-1-72ed5100da14@tdk.com>
On Fri, 04 Apr 2025 17:52:02 +0200
Jean-Baptiste Maneyrol via B4 Relay <devnull+jean-baptiste.maneyrol.tdk.com@kernel.org> wrote:
> From: Jean-Baptiste Maneyrol <jean-baptiste.maneyrol@tdk.com>
>
> Add interrupt-names field for specifying interrupt used.
> Only INT1 is supported by the driver currently.
No SoB?
Also, these are tricky to retrofit. Arguably this is a binding
fix because there was not documentation to see the interrupt was INT1,
so perhaps we don't need to care in the binding (beyond adding that
INT2 is valid as well).
However we don't want the driver to fail on DT out in the field so
we need to fallback to assuming that if the interrupt name is not supplied
we just grab the one interrupt there and assume it is INT1.
Jonathan
> ---
> .../devicetree/bindings/iio/imu/invensense,icm42600.yaml | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/iio/imu/invensense,icm42600.yaml b/Documentation/devicetree/bindings/iio/imu/invensense,icm42600.yaml
> index 7e4492bbd0278a336587dc5ac04da7153453da29..f19cdfd7450e04e7c984dc987f3c23f5ad89a248 100644
> --- a/Documentation/devicetree/bindings/iio/imu/invensense,icm42600.yaml
> +++ b/Documentation/devicetree/bindings/iio/imu/invensense,icm42600.yaml
> @@ -41,6 +41,12 @@ properties:
> interrupts:
> maxItems: 1
>
> + interrupt-names:
> + enum:
> + - INT1
> + description: |
> + set to "INT1" the only supported interrupts pin
> +
> drive-open-drain:
> type: boolean
>
> @@ -76,6 +82,7 @@ examples:
> reg = <0x68>;
> interrupt-parent = <&gpio2>;
> interrupts = <7 IRQ_TYPE_EDGE_FALLING>;
> + interrupt-names = "INT1";
> vdd-supply = <&vdd>;
> vddio-supply = <&vddio>;
> };
> @@ -95,6 +102,7 @@ examples:
> spi-cpol;
> interrupt-parent = <&gpio1>;
> interrupts = <2 IRQ_TYPE_EDGE_FALLING>;
> + interrupt-names = "INT1";
> vdd-supply = <&vdd>;
> vddio-supply = <&vddio>;
> };
>
next prev parent reply other threads:[~2025-04-04 17:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-04 15:52 [PATCH 0/2] iio: imu: inv_icm42600: switch to use generic name irq get Jean-Baptiste Maneyrol via B4 Relay
2025-04-04 15:52 ` [PATCH 1/2] dt-bindings: iio: imu: icm42600: add interrupt naming support Jean-Baptiste Maneyrol via B4 Relay
2025-04-04 16:53 ` Conor Dooley
2025-04-04 17:21 ` Krzysztof Kozlowski
2025-04-07 15:09 ` Conor Dooley
2025-04-04 17:16 ` Jonathan Cameron [this message]
2025-04-04 15:52 ` [PATCH 2/2] iio: imu: inv_icm42600: switch to use generic name irq get Jean-Baptiste Maneyrol via B4 Relay
2025-04-04 17:18 ` Jonathan Cameron
2025-04-04 17:22 ` Krzysztof Kozlowski
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=20250404181622.00006d29@huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=devnull+jean-baptiste.maneyrol.tdk.com@kernel.org \
--cc=jean-baptiste.maneyrol@tdk.com \
--cc=jic23@kernel.org \
--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).