All of lore.kernel.org
 help / color / mirror / Atom feed
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: "Mahapatra, Amit Kumar" <amit.kumar-mahapatra@amd.com>
Cc: Tudor Ambarus <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>,
	Rob Herring <robh@kernel.org>,
	"cornor+dt@kernel.org" <cornor+dt@kernel.org>,
	"krzk+dt@kernel.org" <krzk+dt@kernel.org>,
	"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>,
	"linux-sound@vger.kernel.org" <linux-sound@vger.kernel.org>,
	"git (AMD-Xilinx)" <git@amd.com>,
	"amitrkcian2002@gmail.com" <amitrkcian2002@gmail.com>,
	Conor Dooley <conor.dooley@microchip.com>,
	"beanhuo@micron.com" <beanhuo@micron.com>
Subject: Re: Add stacked and parallel memories support in spi-nor
Date: Thu, 10 Oct 2024 17:00:36 +0200	[thread overview]
Message-ID: <20241010165933.09a4114e@xps-13> (raw)
In-Reply-To: <IA0PR12MB76990FC67F334C0FEBDFEF36DC782@IA0PR12MB7699.namprd12.prod.outlook.com>

Hi Amit,

amit.kumar-mahapatra@amd.com wrote on Thu, 10 Oct 2024 10:35:06 +0000:

> Hello Miquel,
> 
> > -----Original Message-----
> > From: Miquel Raynal <miquel.raynal@bootlin.com>
> > Sent: Thursday, October 10, 2024 2:58 PM
> > To: Mahapatra, Amit Kumar <amit.kumar-mahapatra@amd.com>
> > Cc: Tudor Ambarus <tudor.ambarus@linaro.org>; michael@walle.cc;
> > broonie@kernel.org; pratyush@kernel.org; richard@nod.at; vigneshr@ti.com; Rob
> > Herring <robh@kernel.org>; cornor+dt@kernel.org; krzk+dt@kernel.org; linux-
> > spi@vger.kernel.org; linux-kernel@vger.kernel.org; linux-mtd@lists.infradead.org;
> > nicolas.ferre@microchip.com; alexandre.belloni@bootlin.com;
> > claudiu.beznea@tuxon.dev; Simek, Michal <michal.simek@amd.com>; linux-arm-
> > kernel@lists.infradead.org; alsa-devel@alsa-project.org;
> > patches@opensource.cirrus.com; linux-sound@vger.kernel.org; git (AMD-Xilinx)
> > <git@amd.com>; amitrkcian2002@gmail.com; Conor Dooley
> > <conor.dooley@microchip.com>; beanhuo@micron.com
> > Subject: Re: Add stacked and parallel memories support in spi-nor
> > 
> > Hi Amit,
> > 
> > amit.kumar-mahapatra@amd.com wrote on Thu, 10 Oct 2024 09:17:58 +0000:
> >   
> > > Hello Miquel,
> > >  
> > > > > - The stacked-memories DT bindings will contain the phandles of
> > > > > the flash nodes  
> > > > connected in stacked mode.  
> > > > >
> > > > > - The first flash node will contain the mtd partition that would
> > > > > have the cross over memory staring at a memory location in the
> > > > > first flash and ending at some memory location of the 2nd flash  
> > > >
> > > > I don't like that much. Describing partitions past the actual device
> > > > sounds wrong. If you look into [1] there is a suggestion from Rob to
> > > > handle this case using a property that tells us there is a
> > > > continuation, so from a software perspective we can easily make the link, but on  
> > the hardware description side the information are correct.  
> > >
> > > I reviewed Rob's suggestions in [1], and I need to examine the MTD
> > > layer to determine how this can be implemented from a software perspective.
> > > For reference, here is Rob's suggestion:
> > >
> > > Describe each device and partition separately and add link(s) from one
> > > partition to the next
> > >
> > > flash0 {
> > >   partitions {
> > >     compatible = "fixed-partitions";
> > >     concat-partition = <&flash1_partitions>;
> > >     ...
> > >   };
> > > };
> > >
> > > flash1 {
> > >   flash1_partition: partitions {
> > >     compatible = "fixed-partitions";
> > >     ...
> > >   };
> > > };
> > >  
> > > >
> > > > If this description is accepted, then fine, you can deprecate the "stacked-  
> > memories"  
> > > > property.  
> > >
> > > I believe that in addition to Rob's description, we should also
> > > include the 'stacked-memories' property. This property helps us
> > > identify which flashes are stacked, while Rob's suggestion explains
> > > how the partitions within the stacked flashes are connected.
> > >
> > > For example, if we have three flashes connected to an SPI host, with
> > > flash@0 and flash@1 operating in stacked mode and flash@2 functioning
> > > as a standalone flash, the Device Tree binding might look something like this:
> > > Please share your thoughts on this.
> > >
> > > spi@0 {
> > >   ...
> > >   flash@0 {
> > >     compatible = "jedec,spi-nor"
> > >     reg = <0x00>;
> > >     stacked-memories = <&flash@0 &flash@1>;
> > >     spi-max-frequency = <50000000>;
> > >     ...
> > >         flash0_partition: partitions {
> > >             compatible = "fixed-partitions";
> > > 	concat-partition = <&flash1_partitions>;
> > >         	partition@0 {
> > >           	    label = "Stacked-Flash-1";
> > >                 reg = <0x0 0x800000>;
> > > 	}
> > >         }
> > >     }
> > >   flash@1 {
> > >     compatible = "jedec,spi-nor"
> > >      reg = <0x01>;
> > >     spi-max-frequency = <50000000>;
> > >     ...
> > >         flash1_partition: partitions {
> > >             compatible = "fixed-partitions";
> > > 	concat-partition = <&flash0_partitions>;
> > >         	partition@0 {
> > >           	    label = " Stacked-Flash-2";
> > >                 reg = <0x0 0x800000>;
> > > 	}
> > >         }
> > >   }
> > >
> > >   flash@2 {
> > >     compatible = "jedec,spi-nor"
> > >      reg = <0x01>;
> > >     spi-max-frequency = <50000000>;
> > >     ...
> > >         partitions {
> > >             compatible = "fixed-partitions";
> > > 	concat-partition = <&flash0_partitions>;
> > >         	partition@0 {
> > >           	    label = "Single-Flash";
> > >                 reg = <0x0 0x800000>;
> > > 	}
> > >         }
> > >   }  
> > 
> > I'm sorry but this is pretty messed up. The alignments are wrong, I believe the labels
> > are wrong, the reg properties as well. Can you please work on this example and
> > send an updated version?  
> 
> Apologies for that. Here's the updated version along with the explanation.

Thanks for the update.

> spi@0 {
> 	...
>   	flash@0 {
>   		compatible = "jedec,spi-nor"
>     		reg = <0x00>;
>     		stacked-memories = <&flash@0 &flash@1>;

The same property should, IMHO, also be expected...

>     		spi-max-frequency = <50000000>;
>     		...
>         		partitions {
>             		compatible = "fixed-partitions";
>         			concat-partition = <&flash1_partition>; /* Link to the flash@1 partition@0 */
>                 		flash0_partition: partition@0 {
>                     			label = "part0_0";
>                 			reg = <0x0 0x800000>;
>         			}
>         		}
>     	}
>   	flash@1 {
>     		compatible = "jedec,spi-nor"
>      		reg = <0x01>;

... here.

>     		spi-max-frequency = <50000000>;
>     		...
>         		partitions {
>             		compatible = "fixed-partitions";
>         			concat-partition = <&flash0_partition>; /* Link to the flash@0 partition@0 */
>                 		flash1_partition: partition@0 {
>                     			label = "part0_1";
>                 			reg = <0x0 0x800000>;
>         			}
>         		}
>   	}
> 
>   	flash@2 {
>     		compatible = "jedec,spi-nor"
>      		reg = <0x02>;
>     		spi-max-frequency = <50000000>;
>     		...
>         		partitions {
>             		compatible = "fixed-partitions";       
>                 		partition@0 {
>                     			label = "part1_0";
>                 			reg = <0x0 0x800000>;
>         			}
>         		}
>   	}
> }

Otherwise, okay for me.

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 <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>,
	Rob Herring <robh@kernel.org>,
	"cornor+dt@kernel.org" <cornor+dt@kernel.org>,
	"krzk+dt@kernel.org" <krzk+dt@kernel.org>,
	"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>,
	"linux-sound@vger.kernel.org" <linux-sound@vger.kernel.org>,
	"git (AMD-Xilinx)" <git@amd.com>,
	"amitrkcian2002@gmail.com" <amitrkcian2002@gmail.com>,
	Conor Dooley <conor.dooley@microchip.com>,
	"beanhuo@micron.com" <beanhuo@micron.com>
Subject: Re: Add stacked and parallel memories support in spi-nor
Date: Thu, 10 Oct 2024 17:00:36 +0200	[thread overview]
Message-ID: <20241010165933.09a4114e@xps-13> (raw)
In-Reply-To: <IA0PR12MB76990FC67F334C0FEBDFEF36DC782@IA0PR12MB7699.namprd12.prod.outlook.com>

Hi Amit,

amit.kumar-mahapatra@amd.com wrote on Thu, 10 Oct 2024 10:35:06 +0000:

> Hello Miquel,
> 
> > -----Original Message-----
> > From: Miquel Raynal <miquel.raynal@bootlin.com>
> > Sent: Thursday, October 10, 2024 2:58 PM
> > To: Mahapatra, Amit Kumar <amit.kumar-mahapatra@amd.com>
> > Cc: Tudor Ambarus <tudor.ambarus@linaro.org>; michael@walle.cc;
> > broonie@kernel.org; pratyush@kernel.org; richard@nod.at; vigneshr@ti.com; Rob
> > Herring <robh@kernel.org>; cornor+dt@kernel.org; krzk+dt@kernel.org; linux-
> > spi@vger.kernel.org; linux-kernel@vger.kernel.org; linux-mtd@lists.infradead.org;
> > nicolas.ferre@microchip.com; alexandre.belloni@bootlin.com;
> > claudiu.beznea@tuxon.dev; Simek, Michal <michal.simek@amd.com>; linux-arm-
> > kernel@lists.infradead.org; alsa-devel@alsa-project.org;
> > patches@opensource.cirrus.com; linux-sound@vger.kernel.org; git (AMD-Xilinx)
> > <git@amd.com>; amitrkcian2002@gmail.com; Conor Dooley
> > <conor.dooley@microchip.com>; beanhuo@micron.com
> > Subject: Re: Add stacked and parallel memories support in spi-nor
> > 
> > Hi Amit,
> > 
> > amit.kumar-mahapatra@amd.com wrote on Thu, 10 Oct 2024 09:17:58 +0000:
> >   
> > > Hello Miquel,
> > >  
> > > > > - The stacked-memories DT bindings will contain the phandles of
> > > > > the flash nodes  
> > > > connected in stacked mode.  
> > > > >
> > > > > - The first flash node will contain the mtd partition that would
> > > > > have the cross over memory staring at a memory location in the
> > > > > first flash and ending at some memory location of the 2nd flash  
> > > >
> > > > I don't like that much. Describing partitions past the actual device
> > > > sounds wrong. If you look into [1] there is a suggestion from Rob to
> > > > handle this case using a property that tells us there is a
> > > > continuation, so from a software perspective we can easily make the link, but on  
> > the hardware description side the information are correct.  
> > >
> > > I reviewed Rob's suggestions in [1], and I need to examine the MTD
> > > layer to determine how this can be implemented from a software perspective.
> > > For reference, here is Rob's suggestion:
> > >
> > > Describe each device and partition separately and add link(s) from one
> > > partition to the next
> > >
> > > flash0 {
> > >   partitions {
> > >     compatible = "fixed-partitions";
> > >     concat-partition = <&flash1_partitions>;
> > >     ...
> > >   };
> > > };
> > >
> > > flash1 {
> > >   flash1_partition: partitions {
> > >     compatible = "fixed-partitions";
> > >     ...
> > >   };
> > > };
> > >  
> > > >
> > > > If this description is accepted, then fine, you can deprecate the "stacked-  
> > memories"  
> > > > property.  
> > >
> > > I believe that in addition to Rob's description, we should also
> > > include the 'stacked-memories' property. This property helps us
> > > identify which flashes are stacked, while Rob's suggestion explains
> > > how the partitions within the stacked flashes are connected.
> > >
> > > For example, if we have three flashes connected to an SPI host, with
> > > flash@0 and flash@1 operating in stacked mode and flash@2 functioning
> > > as a standalone flash, the Device Tree binding might look something like this:
> > > Please share your thoughts on this.
> > >
> > > spi@0 {
> > >   ...
> > >   flash@0 {
> > >     compatible = "jedec,spi-nor"
> > >     reg = <0x00>;
> > >     stacked-memories = <&flash@0 &flash@1>;
> > >     spi-max-frequency = <50000000>;
> > >     ...
> > >         flash0_partition: partitions {
> > >             compatible = "fixed-partitions";
> > > 	concat-partition = <&flash1_partitions>;
> > >         	partition@0 {
> > >           	    label = "Stacked-Flash-1";
> > >                 reg = <0x0 0x800000>;
> > > 	}
> > >         }
> > >     }
> > >   flash@1 {
> > >     compatible = "jedec,spi-nor"
> > >      reg = <0x01>;
> > >     spi-max-frequency = <50000000>;
> > >     ...
> > >         flash1_partition: partitions {
> > >             compatible = "fixed-partitions";
> > > 	concat-partition = <&flash0_partitions>;
> > >         	partition@0 {
> > >           	    label = " Stacked-Flash-2";
> > >                 reg = <0x0 0x800000>;
> > > 	}
> > >         }
> > >   }
> > >
> > >   flash@2 {
> > >     compatible = "jedec,spi-nor"
> > >      reg = <0x01>;
> > >     spi-max-frequency = <50000000>;
> > >     ...
> > >         partitions {
> > >             compatible = "fixed-partitions";
> > > 	concat-partition = <&flash0_partitions>;
> > >         	partition@0 {
> > >           	    label = "Single-Flash";
> > >                 reg = <0x0 0x800000>;
> > > 	}
> > >         }
> > >   }  
> > 
> > I'm sorry but this is pretty messed up. The alignments are wrong, I believe the labels
> > are wrong, the reg properties as well. Can you please work on this example and
> > send an updated version?  
> 
> Apologies for that. Here's the updated version along with the explanation.

Thanks for the update.

> spi@0 {
> 	...
>   	flash@0 {
>   		compatible = "jedec,spi-nor"
>     		reg = <0x00>;
>     		stacked-memories = <&flash@0 &flash@1>;

The same property should, IMHO, also be expected...

>     		spi-max-frequency = <50000000>;
>     		...
>         		partitions {
>             		compatible = "fixed-partitions";
>         			concat-partition = <&flash1_partition>; /* Link to the flash@1 partition@0 */
>                 		flash0_partition: partition@0 {
>                     			label = "part0_0";
>                 			reg = <0x0 0x800000>;
>         			}
>         		}
>     	}
>   	flash@1 {
>     		compatible = "jedec,spi-nor"
>      		reg = <0x01>;

... here.

>     		spi-max-frequency = <50000000>;
>     		...
>         		partitions {
>             		compatible = "fixed-partitions";
>         			concat-partition = <&flash0_partition>; /* Link to the flash@0 partition@0 */
>                 		flash1_partition: partition@0 {
>                     			label = "part0_1";
>                 			reg = <0x0 0x800000>;
>         			}
>         		}
>   	}
> 
>   	flash@2 {
>     		compatible = "jedec,spi-nor"
>      		reg = <0x02>;
>     		spi-max-frequency = <50000000>;
>     		...
>         		partitions {
>             		compatible = "fixed-partitions";       
>                 		partition@0 {
>                     			label = "part1_0";
>                 			reg = <0x0 0x800000>;
>         			}
>         		}
>   	}
> }

Otherwise, okay for me.

Thanks,
Miquèl

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

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>,
	"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Conor Dooley <conor.dooley@microchip.com>,
	"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
	"beanhuo@micron.com" <beanhuo@micron.com>,
	"git \(AMD-Xilinx\)" <git@amd.com>, Rob Herring <robh@kernel.org>,
	"richard@nod.at" <richard@nod.at>,
	Tudor Ambarus <tudor.ambarus@linaro.org>,
	"cornor+dt@kernel.org" <cornor+dt@kernel.org>,
	"amitrkcian2002@gmail.com" <amitrkcian2002@gmail.com>,
	"linux-sound@vger.kernel.org" <linux-sound@vger.kernel.org>,
	"broonie@kernel.org" <broonie@kernel.org>,
	"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>,
	"claudiu.beznea@tuxon.dev" <claudiu.beznea@tuxon.dev>,
	"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: Add stacked and parallel memories support in spi-nor
Date: Thu, 10 Oct 2024 17:00:36 +0200	[thread overview]
Message-ID: <20241010165933.09a4114e@xps-13> (raw)
In-Reply-To: <IA0PR12MB76990FC67F334C0FEBDFEF36DC782@IA0PR12MB7699.namprd12.prod.outlook.com>

Hi Amit,

amit.kumar-mahapatra@amd.com wrote on Thu, 10 Oct 2024 10:35:06 +0000:

> Hello Miquel,
> 
> > -----Original Message-----
> > From: Miquel Raynal <miquel.raynal@bootlin.com>
> > Sent: Thursday, October 10, 2024 2:58 PM
> > To: Mahapatra, Amit Kumar <amit.kumar-mahapatra@amd.com>
> > Cc: Tudor Ambarus <tudor.ambarus@linaro.org>; michael@walle.cc;
> > broonie@kernel.org; pratyush@kernel.org; richard@nod.at; vigneshr@ti.com; Rob
> > Herring <robh@kernel.org>; cornor+dt@kernel.org; krzk+dt@kernel.org; linux-
> > spi@vger.kernel.org; linux-kernel@vger.kernel.org; linux-mtd@lists.infradead.org;
> > nicolas.ferre@microchip.com; alexandre.belloni@bootlin.com;
> > claudiu.beznea@tuxon.dev; Simek, Michal <michal.simek@amd.com>; linux-arm-
> > kernel@lists.infradead.org; alsa-devel@alsa-project.org;
> > patches@opensource.cirrus.com; linux-sound@vger.kernel.org; git (AMD-Xilinx)
> > <git@amd.com>; amitrkcian2002@gmail.com; Conor Dooley
> > <conor.dooley@microchip.com>; beanhuo@micron.com
> > Subject: Re: Add stacked and parallel memories support in spi-nor
> > 
> > Hi Amit,
> > 
> > amit.kumar-mahapatra@amd.com wrote on Thu, 10 Oct 2024 09:17:58 +0000:
> >   
> > > Hello Miquel,
> > >  
> > > > > - The stacked-memories DT bindings will contain the phandles of
> > > > > the flash nodes  
> > > > connected in stacked mode.  
> > > > >
> > > > > - The first flash node will contain the mtd partition that would
> > > > > have the cross over memory staring at a memory location in the
> > > > > first flash and ending at some memory location of the 2nd flash  
> > > >
> > > > I don't like that much. Describing partitions past the actual device
> > > > sounds wrong. If you look into [1] there is a suggestion from Rob to
> > > > handle this case using a property that tells us there is a
> > > > continuation, so from a software perspective we can easily make the link, but on  
> > the hardware description side the information are correct.  
> > >
> > > I reviewed Rob's suggestions in [1], and I need to examine the MTD
> > > layer to determine how this can be implemented from a software perspective.
> > > For reference, here is Rob's suggestion:
> > >
> > > Describe each device and partition separately and add link(s) from one
> > > partition to the next
> > >
> > > flash0 {
> > >   partitions {
> > >     compatible = "fixed-partitions";
> > >     concat-partition = <&flash1_partitions>;
> > >     ...
> > >   };
> > > };
> > >
> > > flash1 {
> > >   flash1_partition: partitions {
> > >     compatible = "fixed-partitions";
> > >     ...
> > >   };
> > > };
> > >  
> > > >
> > > > If this description is accepted, then fine, you can deprecate the "stacked-  
> > memories"  
> > > > property.  
> > >
> > > I believe that in addition to Rob's description, we should also
> > > include the 'stacked-memories' property. This property helps us
> > > identify which flashes are stacked, while Rob's suggestion explains
> > > how the partitions within the stacked flashes are connected.
> > >
> > > For example, if we have three flashes connected to an SPI host, with
> > > flash@0 and flash@1 operating in stacked mode and flash@2 functioning
> > > as a standalone flash, the Device Tree binding might look something like this:
> > > Please share your thoughts on this.
> > >
> > > spi@0 {
> > >   ...
> > >   flash@0 {
> > >     compatible = "jedec,spi-nor"
> > >     reg = <0x00>;
> > >     stacked-memories = <&flash@0 &flash@1>;
> > >     spi-max-frequency = <50000000>;
> > >     ...
> > >         flash0_partition: partitions {
> > >             compatible = "fixed-partitions";
> > > 	concat-partition = <&flash1_partitions>;
> > >         	partition@0 {
> > >           	    label = "Stacked-Flash-1";
> > >                 reg = <0x0 0x800000>;
> > > 	}
> > >         }
> > >     }
> > >   flash@1 {
> > >     compatible = "jedec,spi-nor"
> > >      reg = <0x01>;
> > >     spi-max-frequency = <50000000>;
> > >     ...
> > >         flash1_partition: partitions {
> > >             compatible = "fixed-partitions";
> > > 	concat-partition = <&flash0_partitions>;
> > >         	partition@0 {
> > >           	    label = " Stacked-Flash-2";
> > >                 reg = <0x0 0x800000>;
> > > 	}
> > >         }
> > >   }
> > >
> > >   flash@2 {
> > >     compatible = "jedec,spi-nor"
> > >      reg = <0x01>;
> > >     spi-max-frequency = <50000000>;
> > >     ...
> > >         partitions {
> > >             compatible = "fixed-partitions";
> > > 	concat-partition = <&flash0_partitions>;
> > >         	partition@0 {
> > >           	    label = "Single-Flash";
> > >                 reg = <0x0 0x800000>;
> > > 	}
> > >         }
> > >   }  
> > 
> > I'm sorry but this is pretty messed up. The alignments are wrong, I believe the labels
> > are wrong, the reg properties as well. Can you please work on this example and
> > send an updated version?  
> 
> Apologies for that. Here's the updated version along with the explanation.

Thanks for the update.

> spi@0 {
> 	...
>   	flash@0 {
>   		compatible = "jedec,spi-nor"
>     		reg = <0x00>;
>     		stacked-memories = <&flash@0 &flash@1>;

The same property should, IMHO, also be expected...

>     		spi-max-frequency = <50000000>;
>     		...
>         		partitions {
>             		compatible = "fixed-partitions";
>         			concat-partition = <&flash1_partition>; /* Link to the flash@1 partition@0 */
>                 		flash0_partition: partition@0 {
>                     			label = "part0_0";
>                 			reg = <0x0 0x800000>;
>         			}
>         		}
>     	}
>   	flash@1 {
>     		compatible = "jedec,spi-nor"
>      		reg = <0x01>;

... here.

>     		spi-max-frequency = <50000000>;
>     		...
>         		partitions {
>             		compatible = "fixed-partitions";
>         			concat-partition = <&flash0_partition>; /* Link to the flash@0 partition@0 */
>                 		flash1_partition: partition@0 {
>                     			label = "part0_1";
>                 			reg = <0x0 0x800000>;
>         			}
>         		}
>   	}
> 
>   	flash@2 {
>     		compatible = "jedec,spi-nor"
>      		reg = <0x02>;
>     		spi-max-frequency = <50000000>;
>     		...
>         		partitions {
>             		compatible = "fixed-partitions";       
>                 		partition@0 {
>                     			label = "part1_0";
>                 			reg = <0x0 0x800000>;
>         			}
>         		}
>   	}
> }

Otherwise, okay for me.

Thanks,
Miquèl


  reply	other threads:[~2024-10-10 15:01 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-20 12:00 Add stacked and parallel memories support in spi-nor Mahapatra, Amit Kumar
2024-09-09 10:05 ` Mahapatra, Amit Kumar
2024-09-30  9:04 ` Miquel Raynal
2024-09-30  9:04   ` Miquel Raynal
2024-09-30  9:04   ` Miquel Raynal
2024-10-10  9:17   ` Mahapatra, Amit Kumar
2024-10-10  9:17     ` Mahapatra, Amit Kumar
2024-10-10  9:17     ` Mahapatra, Amit Kumar
2024-10-10  9:27     ` Miquel Raynal
2024-10-10  9:27       ` Miquel Raynal
2024-10-10  9:27       ` Miquel Raynal
2024-10-10 10:35       ` Mahapatra, Amit Kumar
2024-10-10 10:35         ` Mahapatra, Amit Kumar
2024-10-10 10:35         ` Mahapatra, Amit Kumar
2024-10-10 15:00         ` Miquel Raynal [this message]
2024-10-10 15:00           ` Miquel Raynal
2024-10-10 15:00           ` Miquel Raynal

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=20241010165933.09a4114e@xps-13 \
    --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.dooley@microchip.com \
    --cc=cornor+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-sound@vger.kernel.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=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.