From: Mark Brown <broonie@kernel.org>
To: Julien Panis <jpanis@baylibre.com>
Cc: Esteban Blanc <eblanc@baylibre.com>,
linus.walleij@linaro.org, lgirdwood@gmail.com,
a.zummo@towertech.it, alexandre.belloni@bootlin.com,
linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org,
linux-rtc@vger.kernel.org, jneanne@baylibre.com
Subject: Re: [PATCH INTERNAL v1 3/3] regulator: tps6594-regulator: Add driver for TI TPS6594 regulators
Date: Wed, 22 Mar 2023 13:13:17 +0000 [thread overview]
Message-ID: <ZBr+7X3lcFdI8p/o@sirena.org.uk> (raw)
In-Reply-To: <205a4e62-fd87-629c-ea34-d863ff1549d8@baylibre.com>
[-- Attachment #1: Type: text/plain, Size: 889 bytes --]
On Wed, Mar 22, 2023 at 10:10:23AM +0100, Julien Panis wrote:
> Question @ Mark/Liam:
> Shouldn't we use the generic 'regulator-coupled-with' property
> instead of 'ti,multi-phase-id' ?
My understanding was that this was a hardware configuration where
two regulators operate as one with only one set of registers used
for configuration.
> I am in charge of upstreaming dt-bindings and maintainers
> pointed out the similarity between 'multi-phase' and 'coupled'
> regulator concepts. Does 'regulator-coupled-with' mean that
> outputs of buck converters are combined ? If so, this generic
> property should replace our specific 'ti,multi-phase-id' prop,
> I guess.
No, coupled regulators are regulators where the voltages can vary
but there's a constraint that their configurations need to be
related somehow, for example they must be within 200mV of each
other or something like that.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2023-03-22 13:13 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-24 13:31 [PATCH v1 0/3] TI TPS6594 PMIC support (RTC, pinctrl, regulators, device trees) Esteban Blanc
2023-02-24 13:31 ` [PATCH INTERNAL v1 1/3] rtc: tps6594: add driver for TPS6594 PMIC RTC Esteban Blanc
2023-03-07 11:08 ` Alexandre Belloni
2023-03-13 9:18 ` Esteban Blanc
2023-03-13 11:01 ` Alexandre Belloni
2023-03-13 12:10 ` Esteban Blanc
2023-03-13 13:38 ` Alexandre Belloni
2023-02-24 13:31 ` [PATCH INTERNAL v1 2/3] pinctrl: tps6594: add for TPS6594 PMIC Esteban Blanc
2023-02-24 18:49 ` kernel test robot
2023-02-25 20:36 ` kernel test robot
2023-03-06 14:10 ` Linus Walleij
2023-03-14 17:30 ` Esteban Blanc
2023-02-24 13:31 ` [PATCH INTERNAL v1 3/3] regulator: tps6594-regulator: Add driver for TI TPS6594 regulators Esteban Blanc
2023-02-24 13:42 ` Mark Brown
2023-03-03 15:02 ` jerome Neanne
2023-03-23 9:12 ` jerome Neanne
2023-03-23 11:38 ` Mark Brown
2023-03-24 8:00 ` jerome Neanne
2023-02-24 14:05 ` Matti Vaittinen
2023-03-03 14:49 ` jerome Neanne
2023-02-24 22:06 ` kernel test robot
2023-03-22 9:10 ` Julien Panis
2023-03-22 13:13 ` Mark Brown [this message]
2023-03-22 13:40 ` Julien Panis
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=ZBr+7X3lcFdI8p/o@sirena.org.uk \
--to=broonie@kernel.org \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@bootlin.com \
--cc=eblanc@baylibre.com \
--cc=jneanne@baylibre.com \
--cc=jpanis@baylibre.com \
--cc=lgirdwood@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rtc@vger.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
all inboxes | Powered by JetHome®