From: Luca Ceresoli <luca@lucaceresoli.net>
To: Rob Herring <robh@kernel.org>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Lee Jones <lee.jones@linaro.org>, Keerthy <j-keerthy@ti.com>,
Axel Lin <axel.lin@ingics.com>
Subject: Re: [PATCH v3 2/4] dt-bindings: mfd: lp87565: convert to yaml
Date: Tue, 14 Jul 2020 11:26:17 +0200 [thread overview]
Message-ID: <fda84ebc-a484-fa88-3bdf-00a4272512e7@lucaceresoli.net> (raw)
In-Reply-To: <20200713190107.GA538448@bogus>
Hi Rob,
On 13/07/20 21:01, Rob Herring wrote:
> On Mon, Jun 22, 2020 at 10:43:27PM +0200, Luca Ceresoli wrote:
>> The definition of "xxx-in-supply" was generic, thus define in detail the
>> possible cases for each chip variant.
>>
>> Also document that the only possible I2C slave address is 0x60 as per the
>> datasheet and fix the second example accordingly.
>>
>> Signed-off-by: Luca Ceresoli <luca@lucaceresoli.net>
[...]
>> +allOf:
>> + - if:
>> + properties:
>> + compatible:
>> + contains:
>> + enum:
>> + - ti,lp87565
>> + - ti,lp87565-q1
>> + then:
>> + properties:
>> + buck10-in-supply:
>> + description:
>> + Phandle to parent supply node for BUCK0 and BUCK1 converters.
>> +
>> + buck23-in-supply:
>> + description:
>> + Phandle to parent supply node for BUCK2 and BUCK3 converters.
>> +
>> + required:
>> + - buck10-in-supply
>> + - buck23-in-supply
>> +
>> + - if:
>> + properties:
>> + compatible:
>> + contains:
>> + enum:
>> + - ti,lp87561-q1
>> + then:
>> + properties:
>> + buck3210-in-supply:
>> + description:
>> + Phandle to parent supply node for all the four BUCK converters.
>> +
>> + required:
>> + - buck3210-in-supply
>
> I think this should probably be 2 schema documents (and a 3rd for the
> next patch)...
No problem, will do.
Is there a specific rule to know when to split, or is it just when the
amount of changes is relevant?
>> +
>> +examples:
>> + - |
>> + /* TI LP87565-Q1 PMIC (dual 2-phase output configuration) */
>> + i2c@0 {
>> + reg = <0x0 0x100>;
>> + #address-cells = <1>;
>> + #size-cells = <0>;
>> +
>> + pmic@60 {
>> + compatible = "ti,lp87565-q1";
>> + reg = <0x60>;
>> + gpio-controller;
>> + #gpio-cells = <2>;
>> +
>> + buck10-in-supply = <&vsys_3v3>;
>> + buck23-in-supply = <&vsys_3v3>;
>> +
>> + regulators {
>> + buck10_reg: buck10 {
>
> The regulators also need to be documented.
OK.
--
Luca
next prev parent reply other threads:[~2020-07-14 9:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-22 20:43 [PATCH v3 0/4] mfd: lp87565: convert DT to yaml, ignore ENx pins and add LP87524-Q1 Luca Ceresoli
2020-06-22 20:43 ` [PATCH v3 1/4] regulator: lp87565: enable voltage regardless of ENx pin Luca Ceresoli
2020-06-22 20:43 ` [PATCH v3 2/4] dt-bindings: mfd: lp87565: convert to yaml Luca Ceresoli
2020-07-13 19:01 ` Rob Herring
2020-07-14 9:26 ` Luca Ceresoli [this message]
2020-06-22 20:43 ` [PATCH v3 3/4] dt-bindings: mfd: lp87565: add LP87524-Q1 variant Luca Ceresoli
2020-06-22 20:43 ` [PATCH v3 4/4] " Luca Ceresoli
2020-07-01 22:23 ` [PATCH v3 0/4] mfd: lp87565: convert DT to yaml, ignore ENx pins and add LP87524-Q1 Mark Brown
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=fda84ebc-a484-fa88-3bdf-00a4272512e7@lucaceresoli.net \
--to=luca@lucaceresoli.net \
--cc=axel.lin@ingics.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=j-keerthy@ti.com \
--cc=lee.jones@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@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