From: Nishanth Menon <nm@ti.com>
To: Apurva Nandan <a-nandan@ti.com>
Cc: Vignesh Raghavendra <vigneshr@ti.com>,
Tero Kristo <kristo@kernel.org>, 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>,
Udit Kumar <u-kumar1@ti.com>, Hari Nagalla <hnagalla@ti.com>
Subject: Re: [PATCH 3/3] arm64: dts: ti: k3-j784s4-evm: Add bootph-pre-ram property for SPL nodes
Date: Mon, 7 Aug 2023 07:48:45 -0500 [thread overview]
Message-ID: <20230807124845.jyo2pb5goxwb3fqw@dance> (raw)
In-Reply-To: <20230806164838.18088-4-a-nandan@ti.com>
On 22:18-20230806, Apurva Nandan wrote:
> Add bootph-pre-ram property for all the nodes used in SPL stage,
> for syncing it later to u-boot j784s4 dts.
>
> Signed-off-by: Apurva Nandan <a-nandan@ti.com>
> ---
> arch/arm64/boot/dts/ti/k3-j784s4-evm.dts | 23 +++++++++++++++++++++++
am69-sk is missing in the series.
but thanks for starting on this series.
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
prev parent reply other threads:[~2023-08-07 12:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-06 16:48 [PATCH 0/3] arm64: dts: ti: k3-j784s4: Add bootph-pre-ram property for SPL nodes Apurva Nandan
2023-08-06 16:48 ` [PATCH 1/3] arm64: dts: ti: k3-j784s4-main: " Apurva Nandan
2023-08-06 16:48 ` [PATCH 2/3] arm64: dts: ti: k3-j784s4-mcu-wakeup: " Apurva Nandan
2023-08-07 4:31 ` Kumar, Udit
2023-08-07 17:13 ` Apurva Nandan
2023-08-07 17:21 ` Nishanth Menon
2023-08-07 17:25 ` Apurva Nandan
2023-08-06 16:48 ` [PATCH 3/3] arm64: dts: ti: k3-j784s4-evm: " Apurva Nandan
2023-08-07 4:34 ` Kumar, Udit
2023-08-07 12:48 ` Nishanth Menon [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=20230807124845.jyo2pb5goxwb3fqw@dance \
--to=nm@ti.com \
--cc=a-nandan@ti.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=hnagalla@ti.com \
--cc=kristo@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 \
--cc=u-kumar1@ti.com \
--cc=vigneshr@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