From: Beleswar Prasad Padhi <b-padhi@ti.com>
To: Wadim Egorov <w.egorov@phytec.de>, <nm@ti.com>, <vigneshr@ti.com>,
<kristo@kernel.org>, <robh@kernel.org>, <krzk+dt@kernel.org>,
<conor+dt@kernel.org>
Cc: <afd@ti.com>, <u-kumar1@ti.com>, <hnagalla@ti.com>, <jm@ti.com>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
Matt McKee <mmckee@phytec.com>,
Garrett Giordano <ggiordano@phytec.com>,
Nathan Morrisson <nmorrisson@phytec.com>,
John Ma <jma@phytec.com>,
Logan Bristol <logan.bristol@utexas.edu>
Subject: Re: [PATCH v2 18/33] arm64: dts: ti: k3-am64-phycore-som: Add missing cfg for TI IPC Firmware
Date: Fri, 29 Aug 2025 11:32:48 +0530 [thread overview]
Message-ID: <877c2edd-851d-4722-8bb4-94fdc3c058a0@ti.com> (raw)
In-Reply-To: <b745deb3-b625-472b-b55a-468eebbdfb16@phytec.de>
Hi Wadim,
On 28/08/25 17:12, Wadim Egorov wrote:
>
>
> On 8/23/25 7:08 PM, Beleswar Padhi wrote:
>> The k3-am64-phycore SoM enables all R5F and M4F remote processors.
>> Reserve the MAIN domain timers that are used by R5F remote
>> processors for ticks to avoid rproc crashes. This config aligns with
>> other AM64 boards and can be refactored out later.
>>
>> Signed-off-by: Beleswar Padhi <b-padhi@ti.com>
>
> I am not sure you need this patch, because you are deleting everything you add in patch 32.
I am also including the "k3-am64-ti-ipc-firmware.dtsi" in patch [32/33]
which has these timer configurations.
This [18/33] is an intermediate patch. We are putting all AM64* boards
into same configuration first before refactoring everything into a
common file [32/33]. That way if there is a bug someday in the future,
due to added configs, the bisect lands on the [18/33] patch and not on
the refactoring patch[32/33].
Just trying to keep every file same before & after the refactoring patch
> But I tested the series on our hardware, so
>
> Tested-by: Wadim Egorov <w.egorov@phytec.de>
Thanks,
Beleswar
>
>> ---
>> Cc: Wadim Egorov <w.egorov@phytec.de>
>> Cc: Matt McKee <mmckee@phytec.com>
>> Cc: Garrett Giordano <ggiordano@phytec.com>
>> Cc: Nathan Morrisson <nmorrisson@phytec.com>
>> Cc: John Ma <jma@phytec.com>
>> Cc: Logan Bristol <logan.bristol@utexas.edu>
>> Requesting for review/test of this patch.
>>
>> v2: Changelog:
>> 1. Re-ordered patch from [PATCH 28/33] to [PATCH v2 18/33].
>>
>> Link to v1:
>> https://lore.kernel.org/all/20250814223839.3256046-29-b-padhi@ti.com/
>>
>> .../boot/dts/ti/k3-am64-phycore-som.dtsi | 24 +++++++++++++++++++
>> 1 file changed, 24 insertions(+)
>>
>> diff --git a/arch/arm64/boot/dts/ti/k3-am64-phycore-som.dtsi b/arch/arm64/boot/dts/ti/k3-am64-phycore-som.dtsi
>> index 03c46d74ebb5..1efd547b2ba6 100644
>> --- a/arch/arm64/boot/dts/ti/k3-am64-phycore-som.dtsi
>> +++ b/arch/arm64/boot/dts/ti/k3-am64-phycore-som.dtsi
>> @@ -275,6 +275,30 @@ mbox_m4_0: mbox-m4-0 {
>> };
>> };
>> +/* main_timer8 is used by r5f0-0 */
>> +&main_timer8 {
>> + status = "reserved";
>> +};
>> +
>> +/* main_timer9 is used by r5f0-1 */
>> +&main_timer9 {
>> + status = "reserved";
>> +};
>> +
>> +/* main_timer10 is used by r5f1-0 */
>> +&main_timer10 {
>> + status = "reserved";
>> +};
>> +
>> +/* main_timer11 is used by r5f1-1 */
>> +&main_timer11 {
>> + status = "reserved";
>> +};
>> +
>> +&main_r5fss0 {
>> + status = "okay";
>> +};
>> +
>> &main_i2c0 {
>> pinctrl-names = "default";
>> pinctrl-0 = <&main_i2c0_pins_default>;
>
next prev parent reply other threads:[~2025-08-29 6:03 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-23 16:08 [PATCH v2 00/33] Refactor TI IPC DT configs into dtsi Beleswar Padhi
2025-08-23 16:08 ` [PATCH v2 01/33] arm64: dts: ti: k3-j7200: Enable remote processors at board level Beleswar Padhi
2025-08-25 14:18 ` Andrew Davis
2025-08-23 16:08 ` [PATCH v2 02/33] arm64: dts: ti: k3-j721e: " Beleswar Padhi
2025-08-23 16:08 ` [PATCH v2 03/33] arm64: dts: ti: k3-j721s2: " Beleswar Padhi
2025-08-23 16:08 ` [PATCH v2 04/33] arm64: dts: ti: k3-j784s4-j742s2: " Beleswar Padhi
2025-08-23 16:08 ` [PATCH v2 05/33] arm64: dts: ti: k3-am62p-j722s: " Beleswar Padhi
2025-08-23 16:08 ` [PATCH v2 06/33] arm64: dts: ti: k3-am62: " Beleswar Padhi
2025-08-28 11:43 ` Wadim Egorov
2025-08-23 16:08 ` [PATCH v2 07/33] arm64: dts: ti: k3-am62a: " Beleswar Padhi
2025-08-23 16:08 ` [PATCH v2 08/33] arm64: dts: ti: k3-am64: " Beleswar Padhi
2025-08-28 11:46 ` Wadim Egorov
2025-08-23 16:08 ` [PATCH v2 09/33] arm64: dts: ti: k3-am65: " Beleswar Padhi
2025-08-23 16:08 ` [PATCH v2 10/33] arm64: dts: ti: k3-am62: Enable Mailbox nodes at the " Beleswar Padhi
2025-08-23 16:08 ` [PATCH v2 11/33] arm64: dts: ti: k3-am62a: " Beleswar Padhi
2025-08-23 16:08 ` [PATCH v2 12/33] arm64: dts: ti: k3-am6*-boards: Add label to reserved-memory node Beleswar Padhi
2025-08-23 16:08 ` [PATCH v2 13/33] arm64: dts: ti: k3-j721e-beagleboneai64: Add missing cfg for TI IPC FW Beleswar Padhi
2025-08-23 16:08 ` [PATCH v2 14/33] arm64: dts: ti: k3-am62p-verdin: Add missing cfg for TI IPC Firmware Beleswar Padhi
2025-08-23 16:08 ` [PATCH v2 15/33] arm64: dts: ti: k3-am62-verdin: " Beleswar Padhi
2025-08-23 16:08 ` [PATCH v2 16/33] arm64: dts: ti: k3-am62-pocketbeagle2: " Beleswar Padhi
2025-08-23 16:08 ` [PATCH v2 17/33] arm64: dts: ti: k3-am642-sr-som: " Beleswar Padhi
2025-08-23 16:08 ` [PATCH v2 18/33] arm64: dts: ti: k3-am64-phycore-som: " Beleswar Padhi
2025-08-28 11:42 ` Wadim Egorov
2025-08-29 6:02 ` Beleswar Prasad Padhi [this message]
2025-08-23 16:08 ` [PATCH v2 19/33] arm64: dts: ti: k3-am642-tqma64xxl: " Beleswar Padhi
2025-08-23 16:08 ` [PATCH v2 20/33] Revert "arm64: dts: ti: k3-j721e-sk: Fix reversed C6x carveout locations" Beleswar Padhi
2025-08-23 16:08 ` [PATCH v2 21/33] Revert "arm64: dts: ti: k3-j721e-beagleboneai64: " Beleswar Padhi
2025-08-23 16:08 ` [PATCH v2 22/33] arm64: dts: ti: k3-j721e-beagleboneai64: Switch MAIN R5F clusters to Split-mode Beleswar Padhi
2025-08-23 16:08 ` [PATCH v2 23/33] arm64: dts: ti: k3-j7200-ti-ipc-firmware: Refactor IPC cfg into new dtsi Beleswar Padhi
2025-08-23 16:08 ` [PATCH v2 24/33] arm64: dts: ti: k3-j721e-ti-ipc-firmware: " Beleswar Padhi
2025-08-23 16:08 ` [PATCH v2 25/33] arm64: dts: ti: k3-j721s2-ti-ipc-firmware: " Beleswar Padhi
2025-08-23 16:08 ` [PATCH v2 26/33] arm64: dts: ti: k3-j784s4-j742s2-ti-ipc-firmware-common: " Beleswar Padhi
2025-08-23 16:08 ` [PATCH v2 27/33] arm64: dts: ti: k3-j784s4-ti-ipc-firmware: " Beleswar Padhi
2025-08-23 16:08 ` [PATCH v2 28/33] arm64: dts: ti: k3-j722s-ti-ipc-firmware: " Beleswar Padhi
2025-08-23 16:08 ` [PATCH v2 29/33] arm64: dts: ti: k3-am62p-ti-ipc-firmware: " Beleswar Padhi
2025-08-23 16:08 ` [PATCH v2 30/33] arm64: dts: ti: k3-am62-ti-ipc-firmware: " Beleswar Padhi
2025-08-28 11:51 ` Wadim Egorov
2025-08-23 16:08 ` [PATCH v2 31/33] arm64: dts: ti: k3-am62a-ti-ipc-firmware: " Beleswar Padhi
2025-08-23 16:09 ` [PATCH v2 32/33] arm64: dts: ti: k3-am64-ti-ipc-firmware: " Beleswar Padhi
2025-08-28 11:52 ` Wadim Egorov
2025-08-23 16:09 ` [PATCH v2 33/33] arm64: dts: ti: k3-am65-ti-ipc-firmware: " Beleswar Padhi
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=877c2edd-851d-4722-8bb4-94fdc3c058a0@ti.com \
--to=b-padhi@ti.com \
--cc=afd@ti.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=ggiordano@phytec.com \
--cc=hnagalla@ti.com \
--cc=jm@ti.com \
--cc=jma@phytec.com \
--cc=kristo@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=logan.bristol@utexas.edu \
--cc=mmckee@phytec.com \
--cc=nm@ti.com \
--cc=nmorrisson@phytec.com \
--cc=robh@kernel.org \
--cc=u-kumar1@ti.com \
--cc=vigneshr@ti.com \
--cc=w.egorov@phytec.de \
/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;
as well as URLs for NNTP newsgroup(s).