From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: barebox@lists.infradead.org
Cc: michael.riesch@wolfvision.net, j.zink@pengutronix.de
Subject: [RFT PATCH 0/3] ARM: Rockchip: align bootsource_instance
Date: Wed, 20 Jul 2022 07:50:39 +0200 [thread overview]
Message-ID: <20220720055042.3510276-1-a.fatoum@pengutronix.de> (raw)
[ "$bootsource" = mmc ] && boot mmc$bootsource_instance on the Rockchip
board doesn't do what one would expect, because the bootrom has
different numbering for the MMC devices than what the upstream board
device trees use for their aliases. This series resolves that.
@Johannes, could you give this a test on the ROCK-3A?
Thanks,
Ahmad Fatoum (3):
bootsource: rename existing bootsource_set to bootsource_set_raw
bootsource: allow DT aliases and bootrom numbering to differ
ARM: dts: rk356x: align bootsource_instance numbering and MMC DT
aliases
.../devicetree/bindings/barebox/aliases.rst | 36 ++++++
arch/arm/boards/radxa-rock3/board.c | 2 +-
.../boards/rockchip-rk3568-bpi-r2pro/board.c | 2 +-
arch/arm/boards/rockchip-rk3568-evb/board.c | 2 +-
arch/arm/dts/rk3566-quartz64-a.dts | 1 +
arch/arm/dts/rk3568-bpi-r2-pro.dts | 1 +
arch/arm/dts/rk3568-evb1-v10.dts | 1 +
arch/arm/dts/rk3568-rock-3a.dts | 1 +
arch/arm/dts/rk356x.dtsi | 9 ++
arch/arm/mach-at91/sama5d2.c | 4 +-
arch/arm/mach-imx/boot.c | 6 +-
arch/arm/mach-layerscape/boot.c | 4 +-
arch/arm/mach-mxs/imx.c | 3 +-
arch/arm/mach-omap/am33xx_generic.c | 3 +-
arch/arm/mach-omap/omap3_generic.c | 3 +-
arch/arm/mach-omap/omap4_generic.c | 3 +-
arch/arm/mach-rockchip/rk3288.c | 3 +-
arch/arm/mach-rockchip/rk3568.c | 9 +-
arch/arm/mach-socfpga/arria10-bootsource.c | 3 +-
arch/arm/mach-socfpga/cyclone5-bootsource.c | 6 +-
arch/arm/mach-stm32mp/init.c | 3 +-
arch/arm/mach-zynq/zynq.c | 2 +-
arch/arm/mach-zynqmp/zynqmp.c | 3 +-
common/bootsource.c | 110 +++++++++++++-----
drivers/block/efi-block-io.c | 2 +-
drivers/efi/efi-device.c | 3 +-
include/bootsource.h | 40 ++++++-
27 files changed, 192 insertions(+), 73 deletions(-)
create mode 100644 Documentation/devicetree/bindings/barebox/aliases.rst
create mode 100644 arch/arm/dts/rk356x.dtsi
--
2.30.2
next reply other threads:[~2022-07-20 5:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-20 5:50 Ahmad Fatoum [this message]
2022-07-20 5:50 ` [RFT PATCH 1/3] bootsource: rename existing bootsource_set to bootsource_set_raw Ahmad Fatoum
2022-07-20 5:50 ` [RFT PATCH 2/3] bootsource: allow DT aliases and bootrom numbering to differ Ahmad Fatoum
2022-07-20 8:32 ` [PATCH] fixup! " Johannes Zink
2022-07-20 9:29 ` Johannes Zink
2022-07-20 5:50 ` [RFT PATCH 3/3] ARM: dts: rk356x: align bootsource_instance numbering and MMC DT aliases Ahmad Fatoum
2022-07-20 9:30 ` Johannes Zink
2022-07-20 10:45 ` Ahmad Fatoum
2022-08-09 7:41 ` [RFT PATCH 0/3] ARM: Rockchip: align bootsource_instance 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=20220720055042.3510276-1-a.fatoum@pengutronix.de \
--to=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=j.zink@pengutronix.de \
--cc=michael.riesch@wolfvision.net \
/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