Received-SPF: pass (google.com: domain of linux-kernel+bounces-208799-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.80.249 as permitted sender) client-ip=147.75.80.249;
Date: Mon, 10 Jun 2024 14:30:15 -0500
From: Bryan Brattlof <bb@ti.com>
To: Hari Nagalla <hnagalla@ti.com>
CC: <vigneshr@ti.com>, <kristo@kernel.org>, <robh+dt@kernel.org>,
        <krzysztof.kozlowski+dt@linaro.org>, <conor+dt@kernel.org>,
        <nm@ti.com>, <linux-kernel@vger.kernel.org>,
        <linux-arm-kernel@lists.infradead.org>, <devicetree@vger.kernel.org>
Subject: Re: [PATCH v3 4/4] arm64: dts: ti: k3-am62a7-sk: Enable ipc with
 remote proc nodes
Message-ID: <20240610193015.flfynlomz6gzwbx6@bryanbrattlof.com>
References: <20240605124859.3034-1-hnagalla@ti.com>
 <20240605124859.3034-5-hnagalla@ti.com>
 <20240606171620.h3twptxb5mrxbqxh@bryanbrattlof.com>
 <e820d497-9327-8d8b-d1b2-7f6707e593aa@ti.com>
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
In-Reply-To: <e820d497-9327-8d8b-d1b2-7f6707e593aa@ti.com>

On June 10, 2024 thus sayeth Hari Nagalla:
> On 6/6/24 12:16, Bryan Brattlof wrote:
> > > +
> > > +		c7x_0_memory_region: c7x-memory@99900000 {
> > > +			compatible = "shared-dma-pool";
> > > +			reg = <0x00 0x99900000 0x00 0x01efffff>;
> > > +			no-map;
> > > +		};
> > >   	};
> > This seems highly specific to the demos we're currently running for our
> > reference boards. If someone wants to develop their own app say with
> > Zypher they would instantly need to change this.
> > 
> > If these absolutely need to be in here could they go in a TI-demo overly?
> > 
> > ~Bryan
> Hey Bryan,
> You are correct, these carveouts match the TI provided firmware binaries.
> Ideally, these could go into an overlay. Just following the carveout model
> used with the rest of the TI SoCs (AM6x/J72x), to avoid confusion to the
> users.

Ah yeah, I was planning to rip those out too ;) 

My idea was to throw them into our SDK layers so that other distros 
don't have to work around them anymore. This also gives the maintainers 
of those meta- layers the control of the reserved-memory{} node so they 
can carve it up or move it around as they need along with the firmware 
they build.

~Bryan