From: Vignesh Raghavendra <vigneshr@ti.com>
To: Neha Malcom Francis <n-francis@ti.com>, <nm@ti.com>,
<kristo@kernel.org>, <robh@kernel.org>, <krzk+dt@kernel.org>,
<conor+dt@kernel.org>
Cc: <linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<u-kumar1@ti.com>
Subject: Re: [PATCH] arm: dts: k3-j721e-mcu-wakeup: Add bootph-all to chipid
Date: Sun, 30 Jun 2024 00:10:03 +0530 [thread overview]
Message-ID: <69cd28cc-60d3-4ca6-b31b-af940a937d9a@ti.com> (raw)
In-Reply-To: <20240627101003.3608397-1-n-francis@ti.com>
On 27/06/24 15:40, Neha Malcom Francis wrote:
> Add bootph-all property to the chipid node so that it is available at
> bootloader stage for obtaining the SoC ID and revision.
>
> Signed-off-by: Neha Malcom Francis <n-francis@ti.com>
> ---
$subject prefix should match existing convention for the file
arm64: dts: ti: ...
> arch/arm64/boot/dts/ti/k3-j721e-mcu-wakeup.dtsi | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/arch/arm64/boot/dts/ti/k3-j721e-mcu-wakeup.dtsi b/arch/arm64/boot/dts/ti/k3-j721e-mcu-wakeup.dtsi
> index 9349ae07c046..c2417ef614cf 100644
> --- a/arch/arm64/boot/dts/ti/k3-j721e-mcu-wakeup.dtsi
> +++ b/arch/arm64/boot/dts/ti/k3-j721e-mcu-wakeup.dtsi
> @@ -57,6 +57,7 @@ wkup_conf: bus@43000000 {
> chipid: chipid@14 {
> compatible = "ti,am654-chipid";
> reg = <0x14 0x4>;
> + bootph-all;
> };
> };
>
--
Regards
Vignesh
prev parent reply other threads:[~2024-06-29 18:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-27 10:10 Neha Malcom Francis
2024-06-29 18:40 ` Vignesh Raghavendra [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=69cd28cc-60d3-4ca6-b31b-af940a937d9a@ti.com \
--to=vigneshr@ti.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kristo@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=n-francis@ti.com \
--cc=nm@ti.com \
--cc=robh@kernel.org \
--cc=u-kumar1@ti.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
all inboxes | Powered by JetHome®