[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250212160659.GA3883406-robh@kernel.org>
Date: Wed, 12 Feb 2025 10:06:59 -0600
From: Rob Herring <robh@...nel.org>
To: Miquel Raynal <miquel.raynal@...tlin.com>
Cc: Amit Kumar Mahapatra <amit.kumar-mahapatra@....com>, richard@....at,
vigneshr@...com, krzk+dt@...nel.org, conor+dt@...nel.org,
linux-mtd@...ts.infradead.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, git@....com, amitrkcian2002@...il.com
Subject: Re: [PATCH v12 1/3] dt-bindings: mtd: Describe MTD partitions
concatenation
On Wed, Feb 12, 2025 at 09:25:53AM +0100, Miquel Raynal wrote:
> Hi,
>
> >> The partitions that gets created are
> >> part0_0
> >> part1_1
> >> part0_1-part1_0-concat
> >
> > 'part-concat' doesn't work if you have multiple sets of partitions you
> > want to concatenate.
> >
> > I think you need something like 'prev-partition' or 'next-partition' in
> > the partition nodes to create a linked list of partitions. Hopefully,
> > you don't need both properties, but you do have to scan everything to
> > figure out which ones are concatenated or not. For example, no property
> > can mean not concatenated or last partition if you use 'next-partition'.
>
> Out of curiosity, would the chosen node be eligible as a central place
> where to look at?
Why would you need that?
Rob
Powered by blists - more mailing lists