[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <PH0PR18MB5002D6EE41A5C285A2CC4E38CED4A@PH0PR18MB5002.namprd18.prod.outlook.com>
Date: Thu, 19 Oct 2023 01:12:22 +0000
From: Linu Cherian <lcherian@...vell.com>
To: Conor Dooley <conor@...nel.org>
CC: Mike Leach <mike.leach@...aro.org>,
"suzuki.poulose@....com" <suzuki.poulose@....com>,
"james.clark@....com" <james.clark@....com>,
"leo.yan@...aro.org" <leo.yan@...aro.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"coresight@...ts.linaro.org" <coresight@...ts.linaro.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"robh+dt@...nel.org" <robh+dt@...nel.org>,
"krzysztof.kozlowski+dt@...aro.org"
<krzysztof.kozlowski+dt@...aro.org>,
"conor+dt@...nel.org" <conor+dt@...nel.org>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
Sunil Kovvuri Goutham <sgoutham@...vell.com>,
George Cherian <gcherian@...vell.com>
Subject: RE: [EXT] Re: [PATCH 1/7] dt-bindings: arm: coresight-tmc: Add
"memory-region" property
Hi Conor,
> -----Original Message-----
> From: Conor Dooley <conor@...nel.org>
> Sent: Saturday, October 14, 2023 6:56 PM
> To: Linu Cherian <lcherian@...vell.com>
> Cc: Mike Leach <mike.leach@...aro.org>; suzuki.poulose@....com;
> james.clark@....com; leo.yan@...aro.org; linux-arm-
> kernel@...ts.infradead.org; coresight@...ts.linaro.org; linux-
> kernel@...r.kernel.org; robh+dt@...nel.org;
> krzysztof.kozlowski+dt@...aro.org; conor+dt@...nel.org;
> devicetree@...r.kernel.org; Sunil Kovvuri Goutham
> <sgoutham@...vell.com>; George Cherian <gcherian@...vell.com>
> Subject: Re: [EXT] Re: [PATCH 1/7] dt-bindings: arm: coresight-tmc: Add
> "memory-region" property
>
> On Sat, Oct 14, 2023 at 11:36:37AM +0000, Linu Cherian wrote:
> > > > + - description: Reserved meta data memory. Used for ETR and ETF
> sinks.
> > > > +
> > > > + memory-region-names:
> > > > + items:
> > > > + - const: trace-mem
> > > > + - const: metadata-mem
> > > > +
> > >
> > > Is there a constraint required here? If we are using the memory area
> > > for trace in a panic situation, then we must have the meta data
> > > memory area defined?
> > > Perhaps a set of names such as "etr-trace-mem", "panic-trace-mem" ,
> > > "panic-metadata-mem", were the first is for general ETR trace in
> > > non-panic situation and then constrain the "panic-" areas to appear
> together.
> > > The "etr-trace-mem", "panic-trace-mem" could easily point to the
> > > same area.
> > >
> > As noted above, we do not have other generic use case for these reserved
> regions now.
> > Hence two regions/names, panic-trace-mem and panic-metadata-mem
> with
> > constraints kept as
> > minItems: 2 and maxItems: 2 would suffice ?
>
> Whatever you do, please delete the -mem suffix.
Ack.
Powered by blists - more mailing lists