diff options
| author | Amit Kumar Mahapatra <amit.kumar-mahapatra@xilinx.com> | 2020-02-17 07:50:05 -0700 |
|---|---|---|
| committer | Michal Simek <michal.simek@xilinx.com> | 2020-04-06 12:51:31 +0200 |
| commit | 0546b1ab06b22fc3cc2c5b23be351ae671a58f82 (patch) | |
| tree | b3247448394aeff2fac2403d9e4bc8fe9a70b7ca /arch/arm/dts/zynqmp-zc1751-xm016-dc2.dts | |
| parent | d9872d8b47be5218b88e0e435c3ccd0311b44914 (diff) | |
arm64: zynqmp: Do not duplicate flash partition label property
In kernel 5.4, support has been added for reading MTD devices via
the nvmem API.
For this the mtd devices are registered as read-only NVMEM providers
under sysfs with the same name as the flash partition label property.
So if flash partition label property of multiple flash devices are identical
then the second mtd device fails to get registered as a NVMEM provider.
This patch fixes the issue by having different label property for different
flashes.
Signed-off-by: Amit Kumar Mahapatra <amit.kumar-mahapatra@xilinx.com>
Signed-off-by: Michal Simek <michal.simek@xilinx.com>
Diffstat (limited to 'arch/arm/dts/zynqmp-zc1751-xm016-dc2.dts')
| -rw-r--r-- | arch/arm/dts/zynqmp-zc1751-xm016-dc2.dts | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/arch/arm/dts/zynqmp-zc1751-xm016-dc2.dts b/arch/arm/dts/zynqmp-zc1751-xm016-dc2.dts index 2ff7952e70..92d938d665 100644 --- a/arch/arm/dts/zynqmp-zc1751-xm016-dc2.dts +++ b/arch/arm/dts/zynqmp-zc1751-xm016-dc2.dts @@ -197,7 +197,7 @@ reg = <0>; partition@0 { - label = "data"; + label = "spi0-data"; reg = <0x0 0x100000>; }; }; @@ -214,7 +214,7 @@ reg = <0>; partition@0 { - label = "data"; + label = "spi1-data"; reg = <0x0 0x84000>; }; }; |