From: Wolfram Sang <wsa@kernel.org>
To: Patrick Rudolph <patrick.rudolph@9elements.com>
Cc: Peter Rosin <peda@axentia.se>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
naresh.solanki@9elements.com,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
linux-i2c@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v15 1/4] dt-bindings: i2c: pca954x: Correct interrupt support
Date: Wed, 23 Aug 2023 23:15:08 +0200 [thread overview]
Message-ID: <ZOZ23CEnQ+Cus2wh@shikoro> (raw)
In-Reply-To: <20230817071056.2125679-2-patrick.rudolph@9elements.com>
[-- Attachment #1: Type: text/plain, Size: 495 bytes --]
On Thu, Aug 17, 2023 at 09:10:50AM +0200, Patrick Rudolph wrote:
> Only some of the PCA954x compatible ICs have interrupt
> capability, but the binding advertises it on all ICs.
>
> Sync the dt-binding with the driver and only advertise it on:
> - nxp,pca9542
> - nxp,pca9543
> - nxp,pca9544
> - nxp,pca9545
>
> Signed-off-by: Patrick Rudolph <patrick.rudolph@9elements.com>
> Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Applied to for-next, thanks!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-08-23 21:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-17 7:10 [PATCH v15 0/4] Add support for Maxim MAX735x/MAX736x variants Patrick Rudolph
2023-08-17 7:10 ` [PATCH v15 1/4] dt-bindings: i2c: pca954x: Correct interrupt support Patrick Rudolph
2023-08-17 16:21 ` Peter Rosin
2023-08-23 21:15 ` Wolfram Sang [this message]
2023-08-23 21:21 ` Wolfram Sang
2023-08-17 7:10 ` [PATCH v15 2/4] dt-bindings: i2c: Add Maxim MAX735x/MAX736x variants Patrick Rudolph
2023-08-17 16:22 ` Peter Rosin
2023-08-23 21:15 ` Wolfram Sang
2023-08-17 16:21 ` [PATCH v15 0/4] Add support for " Peter Rosin
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=ZOZ23CEnQ+Cus2wh@shikoro \
--to=wsa@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=naresh.solanki@9elements.com \
--cc=patrick.rudolph@9elements.com \
--cc=peda@axentia.se \
--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).