From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Patrick Rudolph <patrick.rudolph@9elements.com>,
Peter Rosin <peda@axentia.se>
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
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 v14 2/4] dt-bindings: i2c: Add Maxim MAX735x/MAX736x variants
Date: Tue, 2 May 2023 10:46:11 +0200 [thread overview]
Message-ID: <cfb17cbc-b8cf-c3ce-cf77-7e13e12c42eb@linaro.org> (raw)
In-Reply-To: <CALNFmy1gxUD-C62SH5GxA=fq8eKYxiOHe8wqXGsVdzsyiJc6Xg@mail.gmail.com>
On 02/05/2023 08:52, Patrick Rudolph wrote:
> Hi Peter,
> it could indeed cause problems when VDD1 != VDD2 and at both needs to
> be enabled.
> The pca9846 datasheet seems to refer to VDD1 as VDD. Thus I could add
> an optional "vdd2" regulator to the binding and driver.
>
> Please let me know if that's what you had in mind.
Don't top post.
In such case vdd-supply should not be used for VDD2.
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-05-02 8:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-01 9:15 [PATCH v14 0/4] Add support for Maxim MAX735x/MAX736x variants Patrick Rudolph
2023-05-01 9:15 ` [PATCH v14 1/4] dt-bindings: i2c: pca954x: Correct interrupt support Patrick Rudolph
2023-05-01 9:15 ` [PATCH v14 2/4] dt-bindings: i2c: Add Maxim MAX735x/MAX736x variants Patrick Rudolph
2023-05-02 6:03 ` Peter Rosin
2023-05-02 6:52 ` Patrick Rudolph
2023-05-02 8:46 ` Krzysztof Kozlowski [this message]
2023-05-02 10:36 ` Peter Rosin
2023-07-31 15:29 ` Naresh Solanki
2023-05-01 9:15 ` [PATCH v14 3/4] i2c: muxes: pca954x: Add MAX735x/MAX736x support Patrick Rudolph
2023-05-01 9:15 ` [PATCH v14 4/4] i2c: muxes: pca954x: Add regulator support Patrick Rudolph
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=cfb17cbc-b8cf-c3ce-cf77-7e13e12c42eb@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.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