From: Miquel Raynal <miquel.raynal@bootlin.com>
To: "Mahapatra, Amit Kumar" <amit.kumar-mahapatra@amd.com>
Cc: "tudor.ambarus@linaro.org" <tudor.ambarus@linaro.org>,
"michael@walle.cc" <michael@walle.cc>,
"broonie@kernel.org" <broonie@kernel.org>,
"pratyush@kernel.org" <pratyush@kernel.org>,
"richard@nod.at" <richard@nod.at>,
"vigneshr@ti.com" <vigneshr@ti.com>,
"robh@kernel.org" <robh@kernel.org>,
"conor+dt@kernel.org" <conor+dt@kernel.org>,
"krzk+dt@kernel.org" <krzk+dt@kernel.org>,
"Abbarapu, Venkatesh" <venkatesh.abbarapu@amd.com>,
"linux-spi@vger.kernel.org" <linux-spi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"nicolas.ferre@microchip.com" <nicolas.ferre@microchip.com>,
"alexandre.belloni@bootlin.com" <alexandre.belloni@bootlin.com>,
"claudiu.beznea@tuxon.dev" <claudiu.beznea@tuxon.dev>,
"Simek, Michal" <michal.simek@amd.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"patches@opensource.cirrus.com" <patches@opensource.cirrus.com>,
"git (AMD-Xilinx)" <git@amd.com>,
"amitrkcian2002@gmail.com" <amitrkcian2002@gmail.com>,
"beanhuo@micron.com" <beanhuo@micron.com>
Subject: Re: [RFC PATCH 1/2] dt-bindings: mtd: Add bindings for describing concatinated MTD devices
Date: Wed, 20 Nov 2024 10:52:38 +0100 [thread overview]
Message-ID: <87sermxme1.fsf@bootlin.com> (raw)
In-Reply-To: <IA0PR12MB76994483BBB757BD9F691513DC202@IA0PR12MB7699.namprd12.prod.outlook.com> (Amit Kumar Mahapatra's message of "Tue, 19 Nov 2024 17:02:33 +0000")
On 19/11/2024 at 17:02:33 GMT, "Mahapatra, Amit Kumar" <amit.kumar-mahapatra@amd.com> wrote:
> Hello Miquel,
>
>> > This approach was suggested by Rob [1] during a discussion on Miquel's
>> > initial approach [2] to extend the MTD-CONCAT driver to support
>> > stacked memories.
>> > Define each flash node separately with its respective partitions, and
>> > add a 'concat-parts' binding to link the partitions of the two flash
>> > nodes that need to be concatenated.
>> >
>> > flash@0 {
>> > compatible = "jedec,spi-nor"
>> > ...
>> > partitions {
>>
>> Wrong indentation here and below which makes the example hard to read.
>
> Sorry about that. I am redefining both the flash nodes here with proper
> indentation.
>
> flash@0 {
> compatible = "jedec,spi-nor"
> ...
> partitions {
> compatible = "fixed-partitions";
> concat-partition = <&flash0_partition &flash1_partition>;
>
> flash0_partition: partition@0 {
> label = "part0_0";
> reg = <0x0 0x800000>;
> };
> };
> };
>
> flash@1 {
> compatible = "jedec,spi-nor"
> ...
> partitions {
> compatible = "fixed-partitions";
> concat-partition = <&flash0_partition &flash1_partition>;
>
> flash1_partition: partition@0 {
> label = "part0_1";
> reg = <0x0 0x800000>;
> };
> };
> };
>
>>
>> > compatible = "fixed-partitions";
>> > concat-partition = <&flash0_partition &flash1_partition>;
>> > flash0_partition: partition@0 {
>> > label = "part0_0";
>> > reg = <0x0 0x800000>;
>> > }
>> > }
>> > }
>> > flash@1 {
>> > compatible = "jedec,spi-nor"
>> > ...
>> > partitions {
>> > compatible = "fixed-partitions";
>> > concat-partition = <&flash0_partition &flash1_partition>;
>> > flash1_partition: partition@0 {
>> > label = "part0_1";
>> > reg = <0x0 0x800000>;
>> > }
>> > }
>> > }
>>
>> This approach has a limitation I didn't think about before: you cannot use anything
>> else than fixed partitions as partition parser.
>
> Yes, that's correct—it won't function when partitions are defined via the
> command line. In my opinion, we should start by adding support for fixed
> partitions, add comments in code stating the same. If needed, we can later
> extend the support to dynamic partitions as well.
New thought. What if it was a pure fixed-partition capability? That's
actually what we want: defining fixed partitions through device
boundaries. It automatically removes the need for further dynamic
partition extensions.
Thanks,
Miquèl
WARNING: multiple messages have this Message-ID (diff)
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: "Mahapatra, Amit Kumar" <amit.kumar-mahapatra@amd.com>
Cc: "alexandre.belloni@bootlin.com" <alexandre.belloni@bootlin.com>,
"vigneshr@ti.com" <vigneshr@ti.com>,
"amitrkcian2002@gmail.com" <amitrkcian2002@gmail.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"claudiu.beznea@tuxon.dev" <claudiu.beznea@tuxon.dev>,
"beanhuo@micron.com" <beanhuo@micron.com>,
"git \(AMD-Xilinx\)" <git@amd.com>,
"robh@kernel.org" <robh@kernel.org>,
"richard@nod.at" <richard@nod.at>,
"tudor.ambarus@linaro.org" <tudor.ambarus@linaro.org>,
"conor+dt@kernel.org" <conor+dt@kernel.org>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"broonie@kernel.org" <broonie@kernel.org>,
"Abbarapu, Venkatesh" <venkatesh.abbarapu@amd.com>,
"Simek, Michal" <michal.simek@amd.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"patches@opensource.cirrus.com" <patches@opensource.cirrus.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-spi@vger.kernel.org" <linux-spi@vger.kernel.org>,
"michael@walle.cc" <michael@walle.cc>,
"krzk+dt@kernel.org" <krzk+dt@kernel.org>,
"pratyush@kernel.org" <pratyush@kernel.org>
Subject: Re: [RFC PATCH 1/2] dt-bindings: mtd: Add bindings for describing concatinated MTD devices
Date: Wed, 20 Nov 2024 10:52:38 +0100 [thread overview]
Message-ID: <87sermxme1.fsf@bootlin.com> (raw)
In-Reply-To: <IA0PR12MB76994483BBB757BD9F691513DC202@IA0PR12MB7699.namprd12.prod.outlook.com> (Amit Kumar Mahapatra's message of "Tue, 19 Nov 2024 17:02:33 +0000")
On 19/11/2024 at 17:02:33 GMT, "Mahapatra, Amit Kumar" <amit.kumar-mahapatra@amd.com> wrote:
> Hello Miquel,
>
>> > This approach was suggested by Rob [1] during a discussion on Miquel's
>> > initial approach [2] to extend the MTD-CONCAT driver to support
>> > stacked memories.
>> > Define each flash node separately with its respective partitions, and
>> > add a 'concat-parts' binding to link the partitions of the two flash
>> > nodes that need to be concatenated.
>> >
>> > flash@0 {
>> > compatible = "jedec,spi-nor"
>> > ...
>> > partitions {
>>
>> Wrong indentation here and below which makes the example hard to read.
>
> Sorry about that. I am redefining both the flash nodes here with proper
> indentation.
>
> flash@0 {
> compatible = "jedec,spi-nor"
> ...
> partitions {
> compatible = "fixed-partitions";
> concat-partition = <&flash0_partition &flash1_partition>;
>
> flash0_partition: partition@0 {
> label = "part0_0";
> reg = <0x0 0x800000>;
> };
> };
> };
>
> flash@1 {
> compatible = "jedec,spi-nor"
> ...
> partitions {
> compatible = "fixed-partitions";
> concat-partition = <&flash0_partition &flash1_partition>;
>
> flash1_partition: partition@0 {
> label = "part0_1";
> reg = <0x0 0x800000>;
> };
> };
> };
>
>>
>> > compatible = "fixed-partitions";
>> > concat-partition = <&flash0_partition &flash1_partition>;
>> > flash0_partition: partition@0 {
>> > label = "part0_0";
>> > reg = <0x0 0x800000>;
>> > }
>> > }
>> > }
>> > flash@1 {
>> > compatible = "jedec,spi-nor"
>> > ...
>> > partitions {
>> > compatible = "fixed-partitions";
>> > concat-partition = <&flash0_partition &flash1_partition>;
>> > flash1_partition: partition@0 {
>> > label = "part0_1";
>> > reg = <0x0 0x800000>;
>> > }
>> > }
>> > }
>>
>> This approach has a limitation I didn't think about before: you cannot use anything
>> else than fixed partitions as partition parser.
>
> Yes, that's correct—it won't function when partitions are defined via the
> command line. In my opinion, we should start by adding support for fixed
> partitions, add comments in code stating the same. If needed, we can later
> extend the support to dynamic partitions as well.
New thought. What if it was a pure fixed-partition capability? That's
actually what we want: defining fixed partitions through device
boundaries. It automatically removes the need for further dynamic
partition extensions.
Thanks,
Miquèl
WARNING: multiple messages have this Message-ID (diff)
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: "Mahapatra, Amit Kumar" <amit.kumar-mahapatra@amd.com>
Cc: "tudor.ambarus@linaro.org" <tudor.ambarus@linaro.org>,
"michael@walle.cc" <michael@walle.cc>,
"broonie@kernel.org" <broonie@kernel.org>,
"pratyush@kernel.org" <pratyush@kernel.org>,
"richard@nod.at" <richard@nod.at>,
"vigneshr@ti.com" <vigneshr@ti.com>,
"robh@kernel.org" <robh@kernel.org>,
"conor+dt@kernel.org" <conor+dt@kernel.org>,
"krzk+dt@kernel.org" <krzk+dt@kernel.org>,
"Abbarapu, Venkatesh" <venkatesh.abbarapu@amd.com>,
"linux-spi@vger.kernel.org" <linux-spi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"nicolas.ferre@microchip.com" <nicolas.ferre@microchip.com>,
"alexandre.belloni@bootlin.com" <alexandre.belloni@bootlin.com>,
"claudiu.beznea@tuxon.dev" <claudiu.beznea@tuxon.dev>,
"Simek, Michal" <michal.simek@amd.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"patches@opensource.cirrus.com" <patches@opensource.cirrus.com>,
"git (AMD-Xilinx)" <git@amd.com>,
"amitrkcian2002@gmail.com" <amitrkcian2002@gmail.com>,
"beanhuo@micron.com" <beanhuo@micron.com>
Subject: Re: [RFC PATCH 1/2] dt-bindings: mtd: Add bindings for describing concatinated MTD devices
Date: Wed, 20 Nov 2024 10:52:38 +0100 [thread overview]
Message-ID: <87sermxme1.fsf@bootlin.com> (raw)
In-Reply-To: <IA0PR12MB76994483BBB757BD9F691513DC202@IA0PR12MB7699.namprd12.prod.outlook.com> (Amit Kumar Mahapatra's message of "Tue, 19 Nov 2024 17:02:33 +0000")
On 19/11/2024 at 17:02:33 GMT, "Mahapatra, Amit Kumar" <amit.kumar-mahapatra@amd.com> wrote:
> Hello Miquel,
>
>> > This approach was suggested by Rob [1] during a discussion on Miquel's
>> > initial approach [2] to extend the MTD-CONCAT driver to support
>> > stacked memories.
>> > Define each flash node separately with its respective partitions, and
>> > add a 'concat-parts' binding to link the partitions of the two flash
>> > nodes that need to be concatenated.
>> >
>> > flash@0 {
>> > compatible = "jedec,spi-nor"
>> > ...
>> > partitions {
>>
>> Wrong indentation here and below which makes the example hard to read.
>
> Sorry about that. I am redefining both the flash nodes here with proper
> indentation.
>
> flash@0 {
> compatible = "jedec,spi-nor"
> ...
> partitions {
> compatible = "fixed-partitions";
> concat-partition = <&flash0_partition &flash1_partition>;
>
> flash0_partition: partition@0 {
> label = "part0_0";
> reg = <0x0 0x800000>;
> };
> };
> };
>
> flash@1 {
> compatible = "jedec,spi-nor"
> ...
> partitions {
> compatible = "fixed-partitions";
> concat-partition = <&flash0_partition &flash1_partition>;
>
> flash1_partition: partition@0 {
> label = "part0_1";
> reg = <0x0 0x800000>;
> };
> };
> };
>
>>
>> > compatible = "fixed-partitions";
>> > concat-partition = <&flash0_partition &flash1_partition>;
>> > flash0_partition: partition@0 {
>> > label = "part0_0";
>> > reg = <0x0 0x800000>;
>> > }
>> > }
>> > }
>> > flash@1 {
>> > compatible = "jedec,spi-nor"
>> > ...
>> > partitions {
>> > compatible = "fixed-partitions";
>> > concat-partition = <&flash0_partition &flash1_partition>;
>> > flash1_partition: partition@0 {
>> > label = "part0_1";
>> > reg = <0x0 0x800000>;
>> > }
>> > }
>> > }
>>
>> This approach has a limitation I didn't think about before: you cannot use anything
>> else than fixed partitions as partition parser.
>
> Yes, that's correct—it won't function when partitions are defined via the
> command line. In my opinion, we should start by adding support for fixed
> partitions, add comments in code stating the same. If needed, we can later
> extend the support to dynamic partitions as well.
New thought. What if it was a pure fixed-partition capability? That's
actually what we want: defining fixed partitions through device
boundaries. It automatically removes the need for further dynamic
partition extensions.
Thanks,
Miquèl
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2024-11-20 9:53 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-26 7:53 [RFC PATCH 0/2] Add support for stacked and parallel memories Amit Kumar Mahapatra
2024-10-26 7:53 ` Amit Kumar Mahapatra
2024-10-26 7:53 ` Amit Kumar Mahapatra
2024-10-26 7:53 ` [RFC PATCH 1/2] dt-bindings: mtd: Add bindings for describing concatinated MTD devices Amit Kumar Mahapatra
2024-10-26 7:53 ` Amit Kumar Mahapatra
2024-10-26 7:53 ` Amit Kumar Mahapatra
2024-10-26 11:13 ` Krzysztof Kozlowski
2024-10-26 11:13 ` Krzysztof Kozlowski
2024-10-26 11:13 ` Krzysztof Kozlowski
2024-10-28 6:41 ` Mahapatra, Amit Kumar
2024-10-28 6:41 ` Mahapatra, Amit Kumar
2024-10-28 6:41 ` Mahapatra, Amit Kumar
2024-11-18 13:27 ` Miquel Raynal
2024-11-18 13:27 ` Miquel Raynal
2024-11-18 13:27 ` Miquel Raynal
2024-11-19 17:02 ` Mahapatra, Amit Kumar
2024-11-19 17:02 ` Mahapatra, Amit Kumar
2024-11-19 17:02 ` Mahapatra, Amit Kumar
2024-11-20 9:52 ` Miquel Raynal [this message]
2024-11-20 9:52 ` Miquel Raynal
2024-11-20 9:52 ` Miquel Raynal
2024-11-20 10:08 ` Mahapatra, Amit Kumar
2024-11-20 10:08 ` Mahapatra, Amit Kumar
2024-11-20 10:08 ` Mahapatra, Amit Kumar
2024-10-26 7:53 ` [RFC PATCH 2/2] dt-bindings: spi: Update stacked and parallel bindings Amit Kumar Mahapatra
2024-10-26 7:53 ` Amit Kumar Mahapatra
2024-10-26 7:53 ` Amit Kumar Mahapatra
2024-11-18 13:39 ` Miquel Raynal
2024-11-18 13:39 ` Miquel Raynal
2024-11-18 13:39 ` Miquel Raynal
2024-11-19 17:02 ` Mahapatra, Amit Kumar
2024-11-19 17:02 ` Mahapatra, Amit Kumar
2024-11-19 17:02 ` Mahapatra, Amit Kumar
2024-11-20 9:58 ` Miquel Raynal
2024-11-20 9:58 ` Miquel Raynal
2024-11-20 9:58 ` Miquel Raynal
2024-11-20 10:57 ` Mahapatra, Amit Kumar
2024-11-20 10:57 ` Mahapatra, Amit Kumar
2024-11-20 10:57 ` Mahapatra, Amit Kumar
[not found] ` <b025774a-adf6-443f-b795-bb138c490c2b@metux.net>
2024-10-30 12:09 ` [RFC PATCH 0/2] Add support for stacked and parallel memories Mahapatra, Amit Kumar
2024-10-30 12:09 ` Mahapatra, Amit Kumar
2024-10-30 12:09 ` Mahapatra, Amit Kumar
2024-11-08 14:25 ` Mahapatra, Amit Kumar
2024-11-08 14:25 ` Mahapatra, Amit Kumar
2024-11-08 14:25 ` Mahapatra, Amit Kumar
2024-11-25 15:40 ` Pratyush Yadav
2024-11-25 15:40 ` Pratyush Yadav
2024-11-25 15:40 ` Pratyush Yadav
2024-11-25 15:40 ` Pratyush Yadav
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sermxme1.fsf@bootlin.com \
--to=miquel.raynal@bootlin.com \
--cc=alexandre.belloni@bootlin.com \
--cc=alsa-devel@alsa-project.org \
--cc=amit.kumar-mahapatra@amd.com \
--cc=amitrkcian2002@gmail.com \
--cc=beanhuo@micron.com \
--cc=broonie@kernel.org \
--cc=claudiu.beznea@tuxon.dev \
--cc=conor+dt@kernel.org \
--cc=git@amd.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-spi@vger.kernel.org \
--cc=michael@walle.cc \
--cc=michal.simek@amd.com \
--cc=nicolas.ferre@microchip.com \
--cc=patches@opensource.cirrus.com \
--cc=pratyush@kernel.org \
--cc=richard@nod.at \
--cc=robh@kernel.org \
--cc=tudor.ambarus@linaro.org \
--cc=venkatesh.abbarapu@amd.com \
--cc=vigneshr@ti.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.