From: Rob Herring <robh+dt@kernel.org>
To: Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com>
Cc: Matti Vaittinen <mazziesaccount@gmail.com>,
Lee Jones <lee.jones@linaro.org>,
Mark Rutland <mark.rutland@arm.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
devicetree@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] dt-bindings: bd718x7: Yamlify and add BD71850
Date: Mon, 30 Dec 2019 10:55:54 -0700 [thread overview]
Message-ID: <CAL_Jsq+rEsFARDejfskLHF_zM8qi8dadLKNhq4a+MxMvfeHiNA@mail.gmail.com> (raw)
In-Reply-To: <20191227111235.GA3370@localhost.localdomain>
On Fri, Dec 27, 2019 at 4:12 AM Matti Vaittinen
<matti.vaittinen@fi.rohmeurope.com> wrote:
>
> Convert ROHM bd71837 and bd71847 PMIC binding text docs to yaml. Split
> the binding document to two separate documents (own documents for BD71837
> and BD71847) as they have different amount of regulators. This way we can
> better enforce the node name check for regulators. ROHM is also providing
> BD71850 - which is almost identical to BD71847 - main difference is some
> initial regulator states. The BD71850 can be driven by same driver and it
> has same buck/LDO setup as BD71847 - add it to BD71847 binding document and
> introduce compatible for it.
>
> Signed-off-by: Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com>
> ---
>
> changes since v1:
> - constrains to short and long presses.
> - reworded commit message to shorten a line exceeding 75 chars
> - added 'additionalProperties: false'
> - removed 'clock-names' from example node
>
> .../bindings/mfd/rohm,bd71837-pmic.txt | 90 -------
> .../bindings/mfd/rohm,bd71837-pmic.yaml | 236 ++++++++++++++++++
> .../bindings/mfd/rohm,bd71847-pmic.yaml | 222 ++++++++++++++++
> .../regulator/rohm,bd71837-regulator.txt | 162 ------------
> .../regulator/rohm,bd71837-regulator.yaml | 103 ++++++++
> .../regulator/rohm,bd71847-regulator.yaml | 97 +++++++
> 6 files changed, 658 insertions(+), 252 deletions(-)
> delete mode 100644 Documentation/devicetree/bindings/mfd/rohm,bd71837-pmic.txt
> create mode 100644 Documentation/devicetree/bindings/mfd/rohm,bd71837-pmic.yaml
> create mode 100644 Documentation/devicetree/bindings/mfd/rohm,bd71847-pmic.yaml
> delete mode 100644 Documentation/devicetree/bindings/regulator/rohm,bd71837-regulator.txt
> create mode 100644 Documentation/devicetree/bindings/regulator/rohm,bd71837-regulator.yaml
> create mode 100644 Documentation/devicetree/bindings/regulator/rohm,bd71847-regulator.yaml
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2019-12-30 17:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-27 11:12 [PATCH v2] dt-bindings: bd718x7: Yamlify and add BD71850 Matti Vaittinen
2019-12-30 17:55 ` Rob Herring [this message]
2020-01-07 13:01 ` Lee Jones
2020-01-07 15:37 ` Rob Herring
2020-01-08 8:38 ` Vaittinen, Matti
2020-01-13 10:49 ` Lee Jones
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=CAL_Jsq+rEsFARDejfskLHF_zM8qi8dadLKNhq4a+MxMvfeHiNA@mail.gmail.com \
--to=robh+dt@kernel.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=lee.jones@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=matti.vaittinen@fi.rohmeurope.com \
--cc=mazziesaccount@gmail.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).