mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Beleswar Padhi <b-padhi@ti.com>
To: <nm@ti.com>, <vigneshr@ti.com>, <kristo@kernel.org>,
	<robh@kernel.org>, <krzk+dt@kernel.org>, <conor+dt@kernel.org>
Cc: <u-kumar1@ti.com>, <tony@atomide.com>, <g-vlaev@ti.com>,
	<afd@ti.com>, <hnagalla@ti.com>,
	<linux-arm-kernel@lists.infradead.org>,
	<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: [PATCH v2 0/5] Reserve Timer Nodes to avoid clash with Remoteproc
Date: Wed, 14 Aug 2024 16:11:46 +0530	[thread overview]
Message-ID: <20240814104151.2038457-1-b-padhi@ti.com> (raw)

The remoteproc firmware like of R5F and DSPs in the MAIN voltage domain
use timers. At the same time, if Linux probes the timers, some
instability is observed while booting remote cores. 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.

v2: Changelog:
- Split the changes into individual patches for each SoC to tag the
  correct offending commit for "Fixes:" tag.

* Udit
1) Add the correct clashing timer nodes for J7200 SoC.
2) Port these changes to board level dts files instead of SoC level dtsi files.

Link to v1:
https://lore.kernel.org/all/20240607105559.771080-1-b-padhi@ti.com/

Beleswar Padhi (5):
  arm64: dts: ti: k3-j7200: Change timer nodes status to reserved
  arm64: dts: ti: k3-j721e: Change timer nodes status to reserved
  arm64: dts: ti: k3-j721s2: Change timer nodes status to reserved
  arm64: dts: ti: k3-j784s4: Change timer nodes status to reserved
  arm64: dts: ti: k3-j722s: Change timer nodes status to reserved

 .../dts/ti/k3-j7200-common-proc-board.dts     | 13 ++++++
 .../dts/ti/k3-j721e-common-proc-board.dts     | 29 +++++++++++++
 .../dts/ti/k3-j721s2-common-proc-board.dts    | 25 +++++++++++
 arch/arm64/boot/dts/ti/k3-j722s-evm.dts       | 13 ++++++
 arch/arm64/boot/dts/ti/k3-j784s4-evm.dts      | 41 +++++++++++++++++++
 5 files changed, 121 insertions(+)

-- 
2.34.1


             reply	other threads:[~2024-08-14 10:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-14 10:41 Beleswar Padhi [this message]
2024-08-14 10:41 ` [PATCH v2 1/5] arm64: dts: ti: k3-j7200: Change timer nodes status to reserved Beleswar Padhi
2024-08-14 15:11   ` Kumar, Udit
2024-08-16  7:16     ` Beleswar Prasad Padhi
2024-08-14 10:41 ` [PATCH v2 2/5] arm64: dts: ti: k3-j721e: " Beleswar Padhi
2024-08-14 10:41 ` [PATCH v2 3/5] arm64: dts: ti: k3-j721s2: " Beleswar Padhi
2024-08-14 10:41 ` [PATCH v2 4/5] arm64: dts: ti: k3-j784s4: " Beleswar Padhi
2024-08-14 10:41 ` [PATCH v2 5/5] arm64: dts: ti: k3-j722s: " Beleswar Padhi
2024-08-14 15:56   ` Kumar, Udit

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=20240814104151.2038457-1-b-padhi@ti.com \
    --to=b-padhi@ti.com \
    --cc=afd@ti.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=g-vlaev@ti.com \
    --cc=hnagalla@ti.com \
    --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=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

all inboxes | Powered by JetHome®