Re: [PATCH v12 1/3] dt-bindings: mtd: Describe MTD partitions concatenation

From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Rob Herring <robh@kernel.org>
Cc: Amit Kumar Mahapatra <amit.kumar-mahapatra@amd.com>,
	 richard@nod.at, vigneshr@ti.com,  krzk+dt@kernel.org,
	 conor+dt@kernel.org, linux-mtd@lists.infradead.org,
	 devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	 git@amd.com,  amitrkcian2002@gmail.com
Subject: Re: [PATCH v12 1/3] dt-bindings: mtd: Describe MTD partitions concatenation
Date: Wed, 19 Feb 2025 09:36:37 +0100	[thread overview]
Message-ID: <87ldu2qqju.fsf@bootlin.com> (raw)
In-Reply-To: <20250218213903.GA1203860-robh@kernel.org> (Rob Herring's message of "Tue, 18 Feb 2025 15:39:03 -0600")

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

______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/