[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <87ldu2qqju.fsf@bootlin.com>
Date: Wed, 19 Feb 2025 09:36:37 +0100
From: Miquel Raynal <miquel.raynal@...tlin.com>
To: Rob Herring <robh@...nel.org>
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
Hi Rob,
>> I'm talking about storing in a central place all the concatenated
>> partitions. Your proposal with "next-partition" works fine if we locate
>> it inside the 'partitions' node, but I feel like the 'part-concat'
>> instead was not fitting very well there. So I was wondering in this case
>> if moving the concatenation of the partitions would be eligible to the
>> chosen node, or if that's reserved to *very* few properties (and should
>> remain like that).
>
> You would have to solve the same problem as this patchset which is how
> to support N sets of concatenated partitions.
>
> In general though, we add new things to /chosen very carefully. It's
> usually "things the bootloader configured/enabled" which I don't think
> this qualifies as.
Interesting, I didn't have this "things the bootloader did" explicit
case in mind.
Thanks!
Miquèl
Powered by blists - more mailing lists