From: Rob Herring <robh@kernel.org>
To: Patrick Rudolph <patrick.rudolph@9elements.com>
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
linux-kernel@vger.kernel.org, Peter Rosin <peda@axentia.se>,
devicetree@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
linux-i2c@vger.kernel.org
Subject: Re: [v6 1/3] dt-bindings: i2c: Add Maxim MAX735x/MAX736x variants
Date: Wed, 16 Feb 2022 17:43:08 -0600 [thread overview]
Message-ID: <Yg2MDCQNJJBhO5UY@robh.at.kernel.org> (raw)
In-Reply-To: <20220216074613.235725-2-patrick.rudolph@9elements.com>
On Wed, 16 Feb 2022 08:46:10 +0100, Patrick Rudolph wrote:
> Update the pca954x bindings to add support for the Maxim MAX735x/MAX736x
> chips. The functionality will be provided by the exisintg pca954x driver.
>
> While on it make the interrupts support conditionally as not all of the
> existing chips have interrupts.
>
> For chips that are powered off by default add an optional regulator
> called vdd-supply.
>
> Signed-off-by: Patrick Rudolph <patrick.rudolph@9elements.com>
> ---
> .../bindings/i2c/i2c-mux-pca954x.yaml | 44 ++++++++++++++-----
> 1 file changed, 34 insertions(+), 10 deletions(-)
>
Please add Acked-by/Reviewed-by tags when posting new versions. However,
there's no need to repost patches *only* to add the tags. The upstream
maintainer will do that for acks received on the version they apply.
If a tag was not added on purpose, please state why and what changed.
prev parent reply other threads:[~2022-02-16 23:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-16 7:46 [v6 0/3] Add support for Maxim MAX735x/MAX736x variants Patrick Rudolph
2022-02-16 7:46 ` [v6 1/3] dt-bindings: i2c: Add " Patrick Rudolph
2022-02-16 23:43 ` Rob Herring [this message]
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=Yg2MDCQNJJBhO5UY@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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).