public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Beleswar Prasad 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>, <bb@ti.com>,
	<d-gole@ti.com>, <afd@ti.com>, <hnagalla@ti.com>,
	<linux-arm-kernel@lists.infradead.org>,
	<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4 0/7] Reserve Timer Nodes to avoid clash with Remoteproc firmware
Date: Mon, 26 Aug 2024 16:27:25 +0530	[thread overview]
Message-ID: <e6d97ec3-07ad-454f-b804-a39a0397beeb@ti.com> (raw)
In-Reply-To: <20240826104821.1516344-1-b-padhi@ti.com>


On 26/08/24 16:18, Beleswar Padhi wrote:
> 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.
>
> NOTE: This series has been rebased on top of a sibling series[0] as both of them
> introduce changes in the same files. Thus, please apply [0] before applying this
> series.
>
> [0]: https://lore.kernel.org/all/20240826093024.1183540-1-b-padhi@ti.com/
>
> v4: Changelog:
> 1) Refactored changes from {}-common-proc-board.dts to {}-som.dtsi to put all
> remoteproc related changes at one place as remotecores were getting enabled at
> {}-som.dtsi file.
> 2) Rebased this series on top of [0].
>
> * Nishanth:
> 1) Fixed $subject line for all patches to include the board level files where
> the changes were applied instead of the SoC level files.
> 2) Applied these timer fixes to J721E-SK, AM68-SK and AM69-SK boards as well.


Adding to the changelog,
* Udit:
1) Dropped patch "arm64: dts: ti: k3-j722s: Change timer nodes status to 
reserved" in v4 revision as remoteproc support (DT) has not been 
upstreamed yet for j722s-evm platform.

Apologies for missing this changelog in the cover-letter itself.

>
> Link to v3:
> https://lore.kernel.org/all/20240816073908.2343650-1-b-padhi@ti.com/
>
> v3: Changelog:
> * Udit
> 1) j7200: Updated commit message description to remove DSPs as the SoC does not
> have one.
> 2) j722s: Updated the correct commit for "Fixes:" tag which introduced the bug.
> 3) For entire series, removed comment about timer usage by R5fs in the MCU
> voltage domain as those are used by Device Manager firmware to get SoC
> functional.
>
> Link to v2:
> https://lore.kernel.org/all/20240814104151.2038457-1-b-padhi@ti.com/
>
> 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 (7):
>    arm64: dts: ti: k3-j7200-som-p0: Change timer nodes status to reserved
>    arm64: dts: ti: k3-j721e-som-p0: Change timer nodes status to reserved
>    arm64: dts: ti: k3-j721e-sk: Change timer nodes status to reserved
>    arm64: dts: ti: k3-j721s2-som-p0: Change timer nodes status to
>      reserved
>    arm64: dts: ti: k3-am68-sk-som: Change timer nodes status to reserved
>    arm64: dts: ti: k3-j784s4-evm: Change timer nodes status to reserved
>    arm64: dts: ti: k3-am69-sk: Change timer nodes status to reserved
>
>   arch/arm64/boot/dts/ti/k3-am68-sk-som.dtsi   | 25 ++++++++++++
>   arch/arm64/boot/dts/ti/k3-am69-sk.dts        | 41 ++++++++++++++++++++
>   arch/arm64/boot/dts/ti/k3-j7200-som-p0.dtsi  | 13 +++++++
>   arch/arm64/boot/dts/ti/k3-j721e-sk.dts       | 29 ++++++++++++++
>   arch/arm64/boot/dts/ti/k3-j721e-som-p0.dtsi  | 29 ++++++++++++++
>   arch/arm64/boot/dts/ti/k3-j721s2-som-p0.dtsi | 25 ++++++++++++
>   arch/arm64/boot/dts/ti/k3-j784s4-evm.dts     | 41 ++++++++++++++++++++
>   7 files changed, 203 insertions(+)
>

  parent reply	other threads:[~2024-08-26 10:57 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-26 10:48 [PATCH v4 0/7] Reserve Timer Nodes to avoid clash with Remoteproc firmware Beleswar Padhi
2024-08-26 10:48 ` [PATCH v4 1/7] arm64: dts: ti: k3-j7200-som-p0: Change timer nodes status to reserved Beleswar Padhi
2024-08-26 10:54   ` Krzysztof Kozlowski
2024-08-26 12:37     ` Krzysztof Kozlowski
2024-08-27  4:54       ` Beleswar Prasad Padhi
2024-08-26 10:48 ` [PATCH v4 2/7] arm64: dts: ti: k3-j721e-som-p0: " Beleswar Padhi
2024-08-26 10:48 ` [PATCH v4 3/7] arm64: dts: ti: k3-j721e-sk: " Beleswar Padhi
2024-08-26 10:48 ` [PATCH v4 4/7] arm64: dts: ti: k3-j721s2-som-p0: " Beleswar Padhi
2024-08-26 10:48 ` [PATCH v4 5/7] arm64: dts: ti: k3-am68-sk-som: " Beleswar Padhi
2024-08-26 10:48 ` [PATCH v4 6/7] arm64: dts: ti: k3-j784s4-evm: " Beleswar Padhi
2024-08-26 10:48 ` [PATCH v4 7/7] arm64: dts: ti: k3-am69-sk: " Beleswar Padhi
2024-08-26 10:57 ` Beleswar Prasad Padhi [this message]
2024-08-28 18:58 ` [PATCH v4 0/7] Reserve Timer Nodes to avoid clash with Remoteproc firmware Nishanth Menon

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=e6d97ec3-07ad-454f-b804-a39a0397beeb@ti.com \
    --to=b-padhi@ti.com \
    --cc=afd@ti.com \
    --cc=bb@ti.com \
    --cc=conor+dt@kernel.org \
    --cc=d-gole@ti.com \
    --cc=devicetree@vger.kernel.org \
    --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