From: Michael Walle <michael@walle.cc>
To: linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: Shawn Guo <shawnguo@kernel.org>, Li Yang <leoyang.li@nxp.com>,
Rob Herring <robh+dt@kernel.org>, Yangbo Lu <yangbo.lu@nxp.com>,
Vladimir Oltean <vladimir.oltean@nxp.com>,
Michael Walle <michael@walle.cc>
Subject: [PATCH] arm64: dts: freescale: sl28: correct MMC order
Date: Tue, 24 Nov 2020 22:21:26 +0100 [thread overview]
Message-ID: <20201124212126.32218-1-michael@walle.cc> (raw)
Commit 342ab37ecaf8 ("arm64: dts: freescale: use fixed index mmcN for
layerscape") hardcoded the order of the MMC devices. This doesn't fit
the sl28 boards, which come with an onboard eMMC. Thus use the more
natural order for the eMMC and SD card. Use /dev/mmcblk0 for the eMMC
and /dev/mmcblk1 for the SD card which is removable by the user.
Please note, that the images for this board already use root=UUID=,
therefore the actual device number doesn't matter for booting.
Signed-off-by: Michael Walle <michael@walle.cc>
---
arch/arm64/boot/dts/freescale/fsl-ls1028a-kontron-sl28.dts | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm64/boot/dts/freescale/fsl-ls1028a-kontron-sl28.dts b/arch/arm64/boot/dts/freescale/fsl-ls1028a-kontron-sl28.dts
index fbaecf285d05..6da4a28c4d19 100644
--- a/arch/arm64/boot/dts/freescale/fsl-ls1028a-kontron-sl28.dts
+++ b/arch/arm64/boot/dts/freescale/fsl-ls1028a-kontron-sl28.dts
@@ -18,6 +18,8 @@
aliases {
crypto = &crypto;
+ mmc0 = &esdhc1;
+ mmc1 = &esdhc;
serial0 = &duart0;
serial1 = &duart1;
serial2 = &lpuart1;
--
2.20.1
next reply other threads:[~2020-11-24 21:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-24 21:21 Michael Walle [this message]
2020-11-25 3:03 ` [PATCH] arm64: dts: freescale: sl28: correct MMC order Y.b. Lu
2020-11-30 15:18 ` Michael Walle
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=20201124212126.32218-1-michael@walle.cc \
--to=michael@walle.cc \
--cc=devicetree@vger.kernel.org \
--cc=leoyang.li@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=shawnguo@kernel.org \
--cc=vladimir.oltean@nxp.com \
--cc=yangbo.lu@nxp.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).