From: Samuel Holland <samuel@sholland.org>
To: Maxime Ripard <mripard@kernel.org>, Chen-Yu Tsai <wens@csie.org>,
Jernej Skrabec <jernej.skrabec@siol.net>
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-sunxi@lists.linux.dev, linux-kernel@vger.kernel.org,
Samuel Holland <samuel@sholland.org>
Subject: [PATCH 0/2] sunxi: Enforce consistent MMC numbering
Date: Sun, 18 Apr 2021 21:52:44 -0500 [thread overview]
Message-ID: <20210419025246.21722-1-samuel@sholland.org> (raw)
Dealing with the inconsistent numbering has been a major pain, and
there is a solution with (as far as I can tell) no tangible downsides.
So let's use it.
Yes, I know the kernel supports UUIDs for root=. But UUIDs do not help
when referencing the whole, unpartitioned device, like is needed for
updating the bootloader and firmware. So for the use case of "write a
bootloader to the SD card, regardless of where the board is currently
booted from", I know of two options:
- Dig around in sysfs to find the mmc number from the MMIO address,
which means I have to know the MMIO addresses for every SoC, or
- Apply patches like these.
Samuel Holland (2):
ARM: dts: sunxi: h3/h5: Enforce consistent MMC numbering
arm64: dts: allwinner: Enforce consistent MMC numbering
arch/arm/boot/dts/sunxi-h3-h5.dtsi | 6 ++++++
arch/arm64/boot/dts/allwinner/sun50i-a64.dtsi | 6 ++++++
arch/arm64/boot/dts/allwinner/sun50i-h6.dtsi | 6 ++++++
3 files changed, 18 insertions(+)
--
2.26.3
next reply other threads:[~2021-04-19 2:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-19 2:52 Samuel Holland [this message]
2021-04-19 2:52 ` [PATCH 1/2] ARM: dts: sunxi: h3/h5: Enforce consistent MMC numbering Samuel Holland
2021-04-19 2:52 ` [PATCH 2/2] arm64: dts: allwinner: " Samuel Holland
2021-04-19 3:17 ` [PATCH 0/2] sunxi: " Chen-Yu Tsai
2021-04-19 8:54 ` Andre Przywara
2021-04-30 9:10 ` Maxime Ripard
2021-04-30 10:55 ` Andre Przywara
2021-05-24 13:56 ` Maxime Ripard
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=20210419025246.21722-1-samuel@sholland.org \
--to=samuel@sholland.org \
--cc=devicetree@vger.kernel.org \
--cc=jernej.skrabec@siol.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@lists.linux.dev \
--cc=mripard@kernel.org \
--cc=wens@csie.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;
as well as URLs for NNTP newsgroup(s).