public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Dhruva Gole <d-gole@ti.com>
To: Beleswar Padhi <b-padhi@ti.com>
Cc: <nm@ti.com>, <vigneshr@ti.com>, <kristo@kernel.org>,
	<robh@kernel.org>, <krzk+dt@kernel.org>, <conor+dt@kernel.org>,
	<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>,
	Wadim Egorov <w.egorov@phytec.de>
Subject: Re: [PATCH v3 30/33] arm64: dts: ti: k3-am62-ti-ipc-firmware: Refactor IPC cfg into new dtsi
Date: Mon, 8 Sep 2025 15:07:51 +0530	[thread overview]
Message-ID: <20250908093751.2chmawizotlo3gm6@lcpd911> (raw)
In-Reply-To: <20250905051846.1189612-31-b-padhi@ti.com>

On Sep 05, 2025 at 10:48:43 +0530, Beleswar Padhi wrote:
> The TI K3 AM62 SoCs have multiple programmable remote processors like
> R5F, M4F etc. The TI SDKs for AM62 SoCs offer sample firmwares which
> could be run on these cores to demonstrate an "echo" IPC test. Those
> firmware require certain memory carveouts to be reserved from system
> memory, timers to be reserved, and certain mailbox configurations for
> interrupt based messaging. These configurations could be different for a
> different firmware.
> 
> While DT is not meant for system configurations, at least refactor these
> configurations from board level DTS into a dtsi for now. This dtsi for
> TI IPC firmware is board-independent and can be applied to all boards
> from the same SoC Family. This gets rid of code duplication and allows
> more freedom for users developing custom firmware (or no firmware) to
> utilize system resources better; easily by swapping out this dtsi. To
> maintain backward compatibility, the dtsi is included in all boards.
> 
> Signed-off-by: Beleswar Padhi <b-padhi@ti.com>
> Reviewed-by: Wadim Egorov <w.egorov@phytec.de>
> Tested-by: Wadim Egorov <w.egorov@phytec.de> # phycore-am62x
> ---
[...]

Reviewed-by: Dhruva Gole <d-gole@ti.com>

-- 
Best regards,
Dhruva Gole
Texas Instruments Incorporated


  reply	other threads:[~2025-09-08 12:04 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-05  5:18 [PATCH v3 00/33] Refactor TI IPC DT configs into dtsi Beleswar Padhi
2025-09-05  5:18 ` [PATCH v3 01/33] arm64: dts: ti: k3-j7200: Enable R5F remote processors at board level Beleswar Padhi
2025-09-05  5:18 ` [PATCH v3 02/33] arm64: dts: ti: k3-j721e: Enable " Beleswar Padhi
2025-09-05  5:18 ` [PATCH v3 03/33] arm64: dts: ti: k3-j721s2: " Beleswar Padhi
2025-09-05  5:18 ` [PATCH v3 04/33] arm64: dts: ti: k3-j784s4-j742s2: " Beleswar Padhi
2025-09-05  5:18 ` [PATCH v3 05/33] arm64: dts: ti: k3-am62p-j722s: " Beleswar Padhi
2025-09-05 19:09   ` Dhruva Gole
2025-09-05  5:18 ` [PATCH v3 06/33] arm64: dts: ti: k3-am62: " Beleswar Padhi
2025-09-05 19:11   ` Dhruva Gole
2025-09-05  5:18 ` [PATCH v3 07/33] arm64: dts: ti: k3-am62a: " Beleswar Padhi
2025-09-05  5:18 ` [PATCH v3 08/33] arm64: dts: ti: k3-am64: " Beleswar Padhi
2025-09-05  5:18 ` [PATCH v3 09/33] arm64: dts: ti: k3-am65: " Beleswar Padhi
2025-09-05  5:18 ` [PATCH v3 10/33] arm64: dts: ti: k3-am62: Enable Mailbox nodes at the " Beleswar Padhi
2025-09-05 19:13   ` Dhruva Gole
2025-09-05  5:18 ` [PATCH v3 11/33] arm64: dts: ti: k3-am62a: " Beleswar Padhi
2025-09-05  5:18 ` [PATCH v3 12/33] arm64: dts: ti: k3-am6*-boards: Add label to reserved-memory node Beleswar Padhi
2025-09-05  5:18 ` [PATCH v3 13/33] arm64: dts: ti: k3-j721e-beagleboneai64: Add missing cfg for TI IPC FW Beleswar Padhi
2025-09-05  5:18 ` [PATCH v3 14/33] arm64: dts: ti: k3-am62p-verdin: Add missing cfg for TI IPC Firmware Beleswar Padhi
2025-09-05  5:18 ` [PATCH v3 15/33] arm64: dts: ti: k3-am62-verdin: " Beleswar Padhi
2025-09-05  5:18 ` [PATCH v3 16/33] arm64: dts: ti: k3-am62-pocketbeagle2: " Beleswar Padhi
2025-09-08 11:46   ` Dhruva Gole
2025-09-05  5:18 ` [PATCH v3 17/33] arm64: dts: ti: k3-am642-sr-som: " Beleswar Padhi
2025-09-05  6:34   ` Francesco Dolcini
2025-09-05  5:18 ` [PATCH v3 18/33] arm64: dts: ti: k3-am64-phycore-som: " Beleswar Padhi
2025-09-05  5:18 ` [PATCH v3 19/33] arm64: dts: ti: k3-am642-tqma64xxl: " Beleswar Padhi
2025-09-05  5:18 ` [PATCH v3 20/33] Revert "arm64: dts: ti: k3-j721e-sk: Fix reversed C6x carveout locations" Beleswar Padhi
2025-09-05  5:18 ` [PATCH v3 21/33] Revert "arm64: dts: ti: k3-j721e-beagleboneai64: " Beleswar Padhi
2025-09-05  5:18 ` [PATCH v3 22/33] arm64: dts: ti: k3-j721e-beagleboneai64: Switch MAIN R5F clusters to Split-mode Beleswar Padhi
2025-09-05  5:18 ` [PATCH v3 23/33] arm64: dts: ti: k3-j7200-ti-ipc-firmware: Refactor IPC cfg into new dtsi Beleswar Padhi
2025-09-05  5:18 ` [PATCH v3 24/33] arm64: dts: ti: k3-j721e-ti-ipc-firmware: " Beleswar Padhi
2025-09-05  5:18 ` [PATCH v3 25/33] arm64: dts: ti: k3-j721s2-ti-ipc-firmware: " Beleswar Padhi
2025-09-05  5:18 ` [PATCH v3 26/33] arm64: dts: ti: k3-j784s4-j742s2-ti-ipc-firmware-common: " Beleswar Padhi
2025-09-05  5:18 ` [PATCH v3 27/33] arm64: dts: ti: k3-j784s4-ti-ipc-firmware: " Beleswar Padhi
2025-09-05  5:18 ` [PATCH v3 28/33] arm64: dts: ti: k3-j722s-ti-ipc-firmware: " Beleswar Padhi
2025-09-05  5:18 ` [PATCH v3 29/33] arm64: dts: ti: k3-am62p-ti-ipc-firmware: " Beleswar Padhi
2025-09-08  9:45   ` Dhruva Gole
2025-09-05  5:18 ` [PATCH v3 30/33] arm64: dts: ti: k3-am62-ti-ipc-firmware: " Beleswar Padhi
2025-09-08  9:37   ` Dhruva Gole [this message]
2025-09-05  5:18 ` [PATCH v3 31/33] arm64: dts: ti: k3-am62a-ti-ipc-firmware: " Beleswar Padhi
2025-09-08  9:46   ` Dhruva Gole
2025-09-05  5:18 ` [PATCH v3 32/33] arm64: dts: ti: k3-am64-ti-ipc-firmware: " Beleswar Padhi
2025-09-08  9:46   ` Dhruva Gole
2025-09-05  5:18 ` [PATCH v3 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=20250908093751.2chmawizotlo3gm6@lcpd911 \
    --to=d-gole@ti.com \
    --cc=afd@ti.com \
    --cc=b-padhi@ti.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=hnagalla@ti.com \
    --cc=jm@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=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