From: Yunus Bas <y.bas@phytec.de>
To: barebox@lists.infradead.org
Subject: [PATCH] ARM: dts: phycore-imx6: change mtd-partition names for compatibility with kernel
Date: Thu, 27 Feb 2020 10:06:55 +0100 [thread overview]
Message-ID: <1582794415-151399-1-git-send-email-y.bas@phytec.de> (raw)
The NVMEM-subsystem in newer kernels does not allow identical partition
names on different subdevices. According to the recommendation, we have to
rename the partition names to be compatible with actual kernel
versions.
To minimize the problems which could possibly arise, the nand device is
not changed. For all other devices, we prepend the device name to the
partitions.
Signed-off-by: Yunus Bas <y.bas@phytec.de>
---
arch/arm/dts/imx6qdl-phytec-phycore-som.dtsi | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/arch/arm/dts/imx6qdl-phytec-phycore-som.dtsi b/arch/arm/dts/imx6qdl-phytec-phycore-som.dtsi
index 69f252b..50cf852 100644
--- a/arch/arm/dts/imx6qdl-phytec-phycore-som.dtsi
+++ b/arch/arm/dts/imx6qdl-phytec-phycore-som.dtsi
@@ -29,7 +29,7 @@
environment-spinor {
compatible = "barebox,environment";
- device-path = &m25p80, "partname:barebox-environment";
+ device-path = &m25p80, "partname:nor.barebox-environment";
status = "disabled";
};
};
@@ -86,22 +86,22 @@
#size-cells = <1>;
partition@0 {
- label = "barebox";
+ label = "nor.barebox";
reg = <0x0 0x100000>;
};
partition@100000 {
- label = "barebox-environment";
+ label = "nor.barebox-environment";
reg = <0x100000 0x20000>;
};
partition@120000 {
- label = "oftree";
+ label = "nor.oftree";
reg = <0x120000 0x20000>;
};
partition@140000 {
- label = "kernel";
+ label = "nor.kernel";
reg = <0x140000 0x0>;
};
};
--
2.7.4
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next reply other threads:[~2020-02-27 9:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-27 9:06 Yunus Bas [this message]
2020-03-05 13:26 ` Sascha Hauer
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=1582794415-151399-1-git-send-email-y.bas@phytec.de \
--to=y.bas@phytec.de \
--cc=barebox@lists.infradead.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox