From: Wolfram Sang <wsa@kernel.org>
To: Patrick Rudolph <patrick.rudolph@9elements.com>
Cc: Peter Rosin <peda@axentia.se>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 4/4] i2c: muxes: pca954x: Add regulator support
Date: Wed, 12 Jan 2022 10:31:30 +0100 [thread overview]
Message-ID: <Yd6f8kQ59kcY7JH6@ninjato> (raw)
In-Reply-To: <20220108185759.2086347-5-patrick.rudolph@9elements.com>
[-- Attachment #1: Type: text/plain, Size: 496 bytes --]
On Sat, Jan 08, 2022 at 07:57:58PM +0100, Patrick Rudolph wrote:
> Add an optional vdd regulator and enable it when found for devices
> that are powered off by default.
>
> Signed-off-by: Patrick Rudolph <patrick.rudolph@9elements.com>
regulator support was recently added to the I2C core but had to be
reverted because of side effects [1]. I think you could make use of it
if it gets readded?
[1] a19f75de73c2 ("Revert "i2c: core: support bus regulator controlling in adapter"")
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-01-12 9:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-08 18:57 [PATCH v2 0/4] Add support for Maxim MAX735x/MAX736x variants Patrick Rudolph
2022-01-08 18:57 ` [PATCH v2 1/4] dt-bindings: i2c: Add " Patrick Rudolph
2022-01-08 23:14 ` Laurent Pinchart
2022-01-08 18:57 ` [PATCH v2 2/4] i2c: muxes: pca954x: Add MAX735x/MAX736x support Patrick Rudolph
2022-01-08 18:57 ` [PATCH v2 3/4] dt-bindings: i2c: Add regulator to pca954x and max735x Patrick Rudolph
2022-01-08 23:17 ` Laurent Pinchart
2022-01-08 18:57 ` [PATCH v2 4/4] i2c: muxes: pca954x: Add regulator support Patrick Rudolph
2022-01-12 9:31 ` Wolfram Sang [this message]
2022-01-20 7:22 ` 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=Yd6f8kQ59kcY7JH6@ninjato \
--to=wsa@kernel.org \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patrick.rudolph@9elements.com \
--cc=peda@axentia.se \
/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).