From: "Kumar, Udit" <u-kumar1@ti.com>
To: Beleswar Padhi <b-padhi@ti.com>, <nm@ti.com>, <vigneshr@ti.com>
Cc: <kristo@kernel.org>, <robh@kernel.org>, <krzk+dt@kernel.org>,
<conor+dt@kernel.org>, <tony@atomide.com>,
<linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] arm64: dts: ti: k3-j7xx: Change timer nodes status to reserved
Date: Tue, 9 Jul 2024 21:46:11 +0530 [thread overview]
Message-ID: <39caa8a7-bc40-4f7e-87e1-005c8b677655@ti.com> (raw)
In-Reply-To: <20240607105559.771080-1-b-padhi@ti.com>
Hi Beleswa,
On 6/7/2024 4:25 PM, Beleswar Padhi wrote:
> The remoteproc firmware like of R5F and DSPs in the MAIN voltage domain
> use timers. Therefore, change the status of the timer nodes to
> "reserved" to avoid any clash.
>
> This change is already incorporated for timer nodes in the MCU voltage
> domain.
>
> Fixes: 835d04422f9d ("arm64: dts: ti: k3-j721s2: Add general purpose timers")
>
> Signed-off-by: Beleswar Padhi <b-padhi@ti.com>
> ---
> arch/arm64/boot/dts/ti/k3-j7200-main.dtsi | 2 ++
> arch/arm64/boot/dts/ti/k3-j721e-main.dtsi | 7 +++++++
> arch/arm64/boot/dts/ti/k3-j721s2-main.dtsi | 6 ++++++
> arch/arm64/boot/dts/ti/k3-j784s4-main.dtsi | 10 ++++++++++
> 4 files changed, 25 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/ti/k3-j7200-main.dtsi b/arch/arm64/boot/dts/ti/k3-j7200-main.dtsi
> index 9386bf3ef9f68..22351a4f3da6e 100644
> --- a/arch/arm64/boot/dts/ti/k3-j7200-main.dtsi
> +++ b/arch/arm64/boot/dts/ti/k3-j7200-main.dtsi
> @@ -1254,6 +1254,7 @@ main_timer0: timer@2400000 {
> assigned-clock-parents = <&k3_clks 49 2>;
> power-domains = <&k3_pds 49 TI_SCI_PD_EXCLUSIVE>;
> ti,timer-pwm;
> + status = "reserved";
> };
Instead of changing these nodes in base device tree.
I suggest to change in device tree, where those remoteproc drivers are
getting enabled.
>
> [..]
prev parent reply other threads:[~2024-07-09 16:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-07 10:55 Beleswar Padhi
2024-07-01 8:26 ` Kumar, Udit
2024-07-09 16:16 ` Kumar, Udit [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=39caa8a7-bc40-4f7e-87e1-005c8b677655@ti.com \
--to=u-kumar1@ti.com \
--cc=b-padhi@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=nm@ti.com \
--cc=robh@kernel.org \
--cc=tony@atomide.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
all inboxes | Powered by JetHome®