From: Wei Xu <xuwei5@hisilicon.com>
To: Johan Hovold <johan+linaro@kernel.org>
Cc: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<xuwei5@hisilicon.com>
Subject: Re: [PATCH 0/2] arm64: dts: hisilicon: hikey970-pmic: clean up PMIC nodes
Date: Fri, 8 Dec 2023 15:17:06 +0800 [thread overview]
Message-ID: <6572C2F2.9090202@hisilicon.com> (raw)
In-Reply-To: <20231130175635.14251-1-johan+linaro@kernel.org>
Hi Johan,
On 2023/12/1 1:56, Johan Hovold wrote:
> When reviewing the various SPMI PMIC bindings, I noticed that several
> examples were incorrect and misleading and could also use some cleanup.
>
> This series cleans up the hisilicon hikey970 PMIC dtsi which appears to
> have been used as the basis for some of the examples.
>
> Note that the binding documents "hisilicon,hi6421v600-spmi" while the
> devicetree and driver only uses and recognises "hisilicon,hi6421-spmi".
> I'll leave that as is for now...
>
> Johan
>
>
> Johan Hovold (2):
> arm64: dts: hisilicon: hikey970-pmic: fix regulator cells properties
> arm64: dts: hisilicon: hikey970-pmic: clean up SPMI node
>
> arch/arm64/boot/dts/hisilicon/hikey970-pmic.dtsi | 6 +-----
> 1 file changed, 1 insertion(+), 5 deletions(-)
>
Series applied to the HiSilicon arm64 dt tree as the binding part has been applied.
Thanks!
Best Regards,
Wei
prev parent reply other threads:[~2023-12-08 7:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-30 17:56 [PATCH 0/2] arm64: dts: hisilicon: hikey970-pmic: clean up PMIC nodes Johan Hovold
2023-11-30 17:56 ` [PATCH 1/2] arm64: dts: hisilicon: hikey970-pmic: fix regulator cells properties Johan Hovold
2023-11-30 17:56 ` [PATCH 2/2] arm64: dts: hisilicon: hikey970-pmic: clean up SPMI node Johan Hovold
2023-12-08 7:17 ` Wei Xu [this message]
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=6572C2F2.9090202@hisilicon.com \
--to=xuwei5@hisilicon.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=johan+linaro@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).