From: Andi Shyti <andi.shyti@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: [v16 2/4] dt-bindings: i2c: Add Maxim MAX735x/MAX736x variants
Date: Wed, 23 Aug 2023 16:15:47 +0200 [thread overview]
Message-ID: <20230823141547.w33ieqnu4oshkhld@intel.intel> (raw)
In-Reply-To: <20230821062027.2631725-3-patrick.rudolph@9elements.com>
Hi Patrick,
On Mon, Aug 21, 2023 at 08:20:22AM +0200, Patrick Rudolph wrote:
> Update the pca954x bindings to add support for the Maxim MAX735x/MAX736x
> chips. The functionality will be provided by the existing pca954x driver.
>
> For chips that are powered off by default add a regulator called vdd-supply.
>
> Signed-off-by: Patrick Rudolph <patrick.rudolph@9elements.com>
> Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
you forgot:
Acked-by: Peter Rosin <peda@axentia.se>
Adding it for b4 and patchwork.
Thanks,
Andi
prev parent reply other threads:[~2023-08-23 14:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-21 6:20 [v16 0/4] Add support for Maxim MAX735x/MAX736x variants Patrick Rudolph
2023-08-21 6:20 ` [v16 1/4] dt-bindings: i2c: pca954x: Correct interrupt support Patrick Rudolph
2023-08-23 14:14 ` Andi Shyti
2023-08-21 6:20 ` [v16 2/4] dt-bindings: i2c: Add Maxim MAX735x/MAX736x variants Patrick Rudolph
2023-08-23 14:15 ` Andi Shyti [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=20230823141547.w33ieqnu4oshkhld@intel.intel \
--to=andi.shyti@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).