linux-kernel - Re: [PATCH v3 4/4] arm64: dts: ti: k3-am62a7-sk: Enable ipc with remote proc nodes

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date: Mon, 10 Jun 2024 14:30:15 -0500
From: Bryan Brattlof <bb@...com>
To: Hari Nagalla <hnagalla@...com>
CC: <vigneshr@...com>, <kristo@...nel.org>, <robh+dt@...nel.org>,
        <krzysztof.kozlowski+dt@...aro.org>, <conor+dt@...nel.org>,
        <nm@...com>, <linux-kernel@...r.kernel.org>,
        <linux-arm-kernel@...ts.infradead.org>, <devicetree@...r.kernel.org>
Subject: Re: [PATCH v3 4/4] arm64: dts: ti: k3-am62a7-sk: Enable ipc with
 remote proc nodes

On June 10, 2024 thus sayeth Hari Nagalla:
> On 6/6/24 12:16, Bryan Brattlof wrote:
> > > +
> > > +		c7x_0_memory_region: c7x-memory@...00000 {
> > > +			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