From: Mark Brown <broonie@kernel.org>
To: Adrien Grassein <adrien.grassein@gmail.com>
Cc: lgirdwood@gmail.com, Rob Herring <robh+dt@kernel.org>,
linux-kernel@vger.kernel.org, DTML <devicetree@vger.kernel.org>,
troy.kisky@boundarydevices.com,
Gary Bisson <gary.bisson@boundarydevices.com>
Subject: Re: [PATCH 1/2] dt-bindings: regulator: Add pf8x00 regulator
Date: Fri, 11 Dec 2020 13:25:49 +0000 [thread overview]
Message-ID: <20201211132549.GC4929@sirena.org.uk> (raw)
In-Reply-To: <CABkfQAF4AANtxptY+XB2cR6hpz2i2Km+F5U=R67J57zSfnoGMA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1933 bytes --]
On Thu, Dec 10, 2020 at 11:24:17PM +0100, Adrien Grassein wrote:
> Le lun. 7 déc. 2020 à 14:55, Mark Brown <broonie@kernel.org> a écrit :
> > On Sun, Dec 06, 2020 at 01:26:28AM +0100, Adrien Grassein wrote:
> > > Add dt-bindings for the pf8x00 driver.
> > Please submit patches using subject lines reflecting the style for the
> > subsystem, this makes it easier for people to identify relevant patches.
> > Look at what existing commits in the area you're changing are doing and
> > make sure your subject lines visually resemble what they're doing.
> > There's no need to resubmit to fix this alone.
> For v2 I just copy-paste another commit message to be sure to be conform.
For patches for a given subsystem you should use the prefix the
subsystem uses, for regulator that's "regulator: ".
> > > + $ref: /schemas/types.yaml#definitions/flag
> > > + description: |
> > > + Only available for ldo2. When specified, use the VSELECT pin
> > > + of the chip to control the output voltage of the ldo02 regulator.
> > Shouldn't there be a GPIO specified somewhere or something so that the
> > VSELECT pin can be controlled?
> I think I read better documentation for this point. Sorry, it was very unclear.
> VSELECT is in fact an input pin of the chip. The configuration just enabled it.
Then presumably you need some binding to specify how to control this
input too?
> > > + nxp,quad-phase:
> > > + $ref: /schemas/types.yaml#definitions/flag
> > > + description: |
> > > + This allow regulators sw1 and sw2, or sw3 and sw4 or sw4 and sw5
> > > + to work together to deliver a maximum 10A current.
> > Presumably this must be set on both the regulators being grouped
> > together?
> Not. Only the sw1 configuration will be taken in account.
That needs to be documented then.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-12-11 13:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-06 0:26 [PATCH 1/2] dt-bindings: regulator: Add pf8x00 regulator Adrien Grassein
2020-12-06 0:26 ` [PATCH 2/2] regulator: pf8x00: add support of nxp " Adrien Grassein
2020-12-07 14:08 ` Mark Brown
2020-12-07 20:36 ` kernel test robot
2020-12-07 13:55 ` [PATCH 1/2] dt-bindings: regulator: Add " Mark Brown
2020-12-10 22:24 ` Adrien Grassein
2020-12-11 13:25 ` Mark Brown [this message]
2020-12-10 3:35 ` Rob Herring
2020-12-10 22:16 ` [PATCH v2 1/2] dt-bindings: regulator: add pf8x00 PMIC Adrien Grassein
2020-12-10 22:16 ` [PATCH v2 2/2] regulator: pf8x00: add support of nxp pf8x00 regulator Adrien Grassein
2020-12-11 15:28 ` Mark Brown
2020-12-11 14:04 ` [PATCH v2 1/2] dt-bindings: regulator: add pf8x00 PMIC Mark Brown
2020-12-12 22:43 ` Adrien Grassein
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=20201211132549.GC4929@sirena.org.uk \
--to=broonie@kernel.org \
--cc=adrien.grassein@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=gary.bisson@boundarydevices.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=troy.kisky@boundarydevices.com \
/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).