From: Shawn Guo <shawnguo@kernel.org>
To: Fabio Estevam <festevam@gmail.com>
Cc: otavio@ossystems.com.br, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ARM: dts: imx6sl: Add a label for the cpu node
Date: Thu, 5 May 2022 10:33:18 +0800 [thread overview]
Message-ID: <20220505023318.GM14615@dragon> (raw)
In-Reply-To: <20220422195537.1783718-1-festevam@gmail.com>
On Fri, Apr 22, 2022 at 04:55:37PM -0300, Fabio Estevam wrote:
> Add a label for the cpu node, so that board devicetree files can
> reference to the CPU node.
>
> This is useful for describing a PMIC voltage that supplies the CPU
> voltage.
>
> For example:
>
> &cpu0 {
> cpu-supply = <&sw1_reg>;
>
> Signed-off-by: Fabio Estevam <festevam@gmail.com>
Applied, thanks!
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2022-05-05 2:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-22 19:55 [PATCH] ARM: dts: imx6sl: Add a label for the cpu node Fabio Estevam
2022-05-05 2:33 ` Shawn Guo [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=20220505023318.GM14615@dragon \
--to=shawnguo@kernel.org \
--cc=festevam@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=otavio@ossystems.com.br \
/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).