From: David Heidelberg <david@ixit.cz>
To: Lee Jones <lee.jones@linaro.org>, Rob Herring <robh@kernel.org>
Cc: linux-kernel@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
Andy Gross <agross@kernel.org>,
Caleb Connolly <caleb@connolly.tech>,
linux-arm-msm@vger.kernel.org, Stephen Boyd <sboyd@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
~okias/devicetree@lists.sr.ht,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
devicetree@vger.kernel.org, Lee Jones <lee@kernel.org>
Subject: Re: [PATCH v3] dt-bindings: mfd: convert to yaml Qualcomm SPMI PMIC
Date: Wed, 10 Aug 2022 13:47:44 +0200 [thread overview]
Message-ID: <1768ffde-fc99-29c5-d9fe-ce41db052c7a@ixit.cz> (raw)
In-Reply-To: <YvOPKKw60F4qEKM6@google.com>
On 10/08/2022 12:57, Lee Jones wrote:
> On Tue, 09 Aug 2022, Rob Herring wrote:
>
>> On Sun, 26 Jun 2022 21:16:30 +0200, David Heidelberg wrote:
>>> Convert Qualcomm SPMI PMIC binding to yaml format.
>>>
>>> Additional changes:
>>> - filled many missing compatibles
>>>
>>> Co-developed-by: Caleb Connolly <caleb@connolly.tech>
>>> Signed-off-by: David Heidelberg <david@ixit.cz>
>>> ---
>>> v3:
>>> - added subnodes, there are two not converted to YAML yet, but it works
>>> - now it prints milion directly unrelated warning to this binding
>>> (it's related to the included subnodes bindings, can be merged,
>>> but it'll generate more warnings and preferably anyone can takeover
>>> from here)
>>> - add qcom,pmx65
>>>
>>> v2:
>>> - changed author to myself, kept Caleb as co-author
>>> - moved nodename to properties
>>> - add nodenames for pm* with deprecated property
>>> - add ^$ to pattern properties
>>> - dropped interrupt-names property
>>> - added reg prop. to the nodes which have register in nodename
>>> - added compatible pmx55
>>> Signed-off-by: David Heidelberg <david@ixit.cz>
>>> ---
>>> .../bindings/mfd/qcom,spmi-pmic.txt | 94 ---------
>>> .../bindings/mfd/qcom,spmi-pmic.yaml | 191 ++++++++++++++++++
>>> 2 files changed, 191 insertions(+), 94 deletions(-)
>>> delete mode 100644 Documentation/devicetree/bindings/mfd/qcom,spmi-pmic.txt
>>> create mode 100644 Documentation/devicetree/bindings/mfd/qcom,spmi-pmic.yaml
>>>
>> As this hasn't been picked up, I applied it. Thanks!
> I'd prefer to take it via MFD if it's all the same to you.
>
> In case there are additional fix-ups required during the next cycle.
I can rebase it against MFD if it's more convenient.
David
>
--
David Heidelberg
Consultant Software Engineer
Matrix: @okias:matrix.org
next prev parent reply other threads:[~2022-08-10 11:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-26 19:16 [PATCH v3] dt-bindings: mfd: convert to yaml Qualcomm SPMI PMIC David Heidelberg
2022-06-27 13:31 ` Rob Herring
2022-07-14 18:50 ` Rob Herring
2022-08-09 23:56 ` Rob Herring
2022-08-10 10:57 ` Lee Jones
2022-08-10 11:47 ` David Heidelberg [this message]
2022-08-10 11:52 ` Lee Jones
2022-08-10 15:07 ` Rob Herring
2022-08-10 15:23 ` Lee Jones
2022-08-10 13:29 ` 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=1768ffde-fc99-29c5-d9fe-ce41db052c7a@ixit.cz \
--to=david@ixit.cz \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=caleb@connolly.tech \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lee.jones@linaro.org \
--cc=lee@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=robh@kernel.org \
--cc=sboyd@kernel.org \
--cc=~okias/devicetree@lists.sr.ht \
/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).