From: Beleswar Prasad Padhi <b-padhi@ti.com>
To: Nishanth Menon <nm@ti.com>
Cc: <vigneshr@ti.com>, <kristo@kernel.org>, <robh@kernel.org>,
<krzk+dt@kernel.org>, <conor+dt@kernel.org>, <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 v3 0/5] Reserve Timer Nodes to avoid clash with Remoteproc firmware
Date: Mon, 26 Aug 2024 16:20:15 +0530 [thread overview]
Message-ID: <d682f87e-be8e-4679-9b6b-b37b3f897d9b@ti.com> (raw)
In-Reply-To: <20240824180356.quv4zdrtnskrnuo5@diagram>
On 24/08/24 23:33, Nishanth Menon wrote:
> On 13:09-20240816, 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.
>>
>> 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 (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
> All patches: please fix your $subject. it looked initially like
Thanks for pointing out, fixed this in v4 revision.
> you were fixing the default SoC behavior, but later I realized
> you are fixing the evm solution.
>
> Also while at this make sure the corresponding SK behaviors are in sync
Thanks for catching this. I have included timer changes for SK boards in
the v4 revision.
> correctly as well. if you think they do not need to be fixed, address
> that comment in the cover-letter.
>
>> .../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
>>
prev parent reply other threads:[~2024-08-26 10:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-16 7:39 Beleswar Padhi
2024-08-16 7:39 ` [PATCH v3 1/5] arm64: dts: ti: k3-j7200: Change timer nodes status to reserved Beleswar Padhi
2024-08-16 7:39 ` [PATCH v3 2/5] arm64: dts: ti: k3-j721e: " Beleswar Padhi
2024-08-16 7:39 ` [PATCH v3 3/5] arm64: dts: ti: k3-j721s2: " Beleswar Padhi
2024-08-16 7:39 ` [PATCH v3 4/5] arm64: dts: ti: k3-j784s4: " Beleswar Padhi
2024-08-16 7:39 ` [PATCH v3 5/5] arm64: dts: ti: k3-j722s: " Beleswar Padhi
2024-08-26 5:00 ` Kumar, Udit
2024-08-26 10:51 ` Beleswar Prasad Padhi
2024-08-24 18:03 ` [PATCH v3 0/5] Reserve Timer Nodes to avoid clash with Remoteproc firmware Nishanth Menon
2024-08-26 10:50 ` Beleswar Prasad Padhi [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=d682f87e-be8e-4679-9b6b-b37b3f897d9b@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
all inboxes | Powered by JetHome®