Add minimal boot support for Raspberry Pi 5
Subsystems (7)
v4 cover Add minimal boot support for Raspberry Pi 5
Hi,
This patchset adds minimal support for the Broadcom BCM2712 SoC and for the on-board SDHCI controller on Broadcom BCM2712 in order to make it possible to boot (particularly) a Raspberry Pi 5 from SD card and get a console through uart.
Changes to arm64/defconfig are not needed since the actual options work as they are.
This work is heavily based on downstream contributions.
Tested on Tumbleweed substituting the stock kernel with upstream one, either chainloading uboot+grub+kernel or directly booting the kernel from 1st stage bootloader. Steps to reproduce:
- prepare an SD card from a Raspberry enabled raw image, mount the first FAT partition.
- make sure the FAT partition is big enough to contain the kernel, anything bigger than 64Mb is usually enough, depending on your kernel config options.
- build the kernel and dtbs making sure that the support for your root fs type is compiled as builtin.
- copy the kernel image in your FAT partition overwriting the older one (e.g. kernel*.img for Raspberry Pi OS or u-boot.bin for Tumbleweed).
- copy arch/arm64/boot/dts/broadcom/bcm2712-rpi-5-b.dtb on FAT partition.
- make sure you have a cmdline.txt file in FAT partition with the following content:
# cat /boot/efi/cmdline.txt root=/dev/mmcblk0p3 rootwait rw console=tty ignore_loglevel earlycon console=ttyAMA10,115200 - if you experience random SD issues during boot, try to set initial_turbo=0 in config.txt.
Changes in V4:
sdhci-brcmstb.c:
- dropped the last 4 lines of sdhci_brcmstb_cfginit_2712() function to avoid setting the SDIO_CFG_CQ_CAPABILITY register. The rationale behind this can be found in [4] and subsequent comments
DT-bindings:
- simplified the compatible item list for 'brcm,bcm2712-sdhci' as per [5]
Changes in V3:
DTS:
- uart0 renamed to uart10 to reflect the current indexing (ttyAMA10 and serial10)
- updated the license to (GPL-2.0 OR MIT)
- sd_io_1v8_reg 'states' property have second cells as decimal instead of hex.
- root node has size-cells=<2> now to accommodate for the DRAM controller and the address bus mapping that goes beyond 4GB. As a consequence, memory, axi and reserved-memory nodes have also size-cells=<2> and subnodes reg and ranges properties have been updated accordingly
- ranges property in 'axi' node has been fixed, reg properties of sdio1 and gicv2 subnodes have been adjusted according to the new mapping
- 'interrupt-controller@7d517000' node is now enabled by default
- dropped 'arm,cpu-registers-not-fw-configured' as it is no longer relevant on A76 core
- l2 cache nodes moved under respective cpus, since they are per-cpu
- dropped psci cpu functions properties
- added the hypervisor EL2 virtual timer interrupt to the 'timer' node
- splitted-lines url are now on a single line
sdhci-brcmstb.c:
- simplified MMC_CAP_HSE_MASK leveraging already existing definitions
- MMC_CAP_UHS_MASK renamed to MMC_CAP_UHS_I_SDR_MASK to better reflect its purpose. Added also a comment.
- sdhci_brcmstb_set_power() replaced with the already existing (and equivalent) sdhci_set_power_and_bus_voltage()
DT-bindings:
- removed the BCM2712 specific example, as per Rob's request.
Changes in V2:
- the patchshet has been considerably simplified, both in terms of dts and driver code. Notably, the pinctrl/pinmux driver (and associated binding) was not strictly needed to use the SD card so it has been dropped
- dropped the optional SD express support patch
- the patches order has been revisited
- pass all checks (binding, dtb, checkpatch)
Many thanks,
Andrea
References:
[1] - Link to V1: https://lore.kernel.org/all/[email protected]/
[2] - Link to V2: https://lore.kernel.org/all/[email protected]/
[3] - Link to V3: https://lore.kernel.org/all/[email protected]/
[4] - https://lore.kernel.org/all/ZlF5dQbNpZ921e66@apocalypse/
[5] - https://lore.kernel.org/all/[email protected]/#t
Andrea della Porta (4):
dt-bindings: arm: bcm: Add BCM2712 SoC support
dt-bindings: mmc: Add support for BCM2712 SD host controller
mmc: sdhci-brcmstb: Add BCM2712 support
arm64: dts: broadcom: Add support for BCM2712
.../devicetree/bindings/arm/bcm/bcm2835.yaml | 6 + .../bindings/mmc/brcm,sdhci-brcmstb.yaml | 1 + arch/arm64/boot/dts/broadcom/Makefile | 1 + .../boot/dts/broadcom/bcm2712-rpi-5-b.dts | 64 ++++ arch/arm64/boot/dts/broadcom/bcm2712.dtsi | 292 ++++++++++++++++++ drivers/mmc/host/sdhci-brcmstb.c | 60 ++++ 6 files changed, 424 insertions(+) create mode 100644 arch/arm64/boot/dts/broadcom/bcm2712-rpi-5-b.dts create mode 100644 arch/arm64/boot/dts/broadcom/bcm2712.dtsi
Signature · 1 line
2.35.3
PATCH v4 1/4 dt-bindings: arm: bcm: Add BCM2712 SoC support
The BCM2712 SoC is found on Raspberry Pi 5. Add compatible string to acknowledge its new chipset.
--- Documentation/devicetree/bindings/arm/bcm/bcm2835.yaml | 6 ++++++ 1 file changed, 6 insertions(+)
Documentation/devicetree/bindings/arm/bcm/bcm2835.yaml +6 -0
@@ -23,6 +23,12 @@ properties: - raspberrypi,4-model-b - const: brcm,bcm2711 + - description: BCM2712 based Boards + items: + - enum: + - raspberrypi,5-model-b + - const: brcm,bcm2712 + - description: BCM2835 based Boards items: - enum:
Signature · 1 line
2.35.3
PATCH v4 2/4 dt-bindings: mmc: Add support for BCM2712 SD host controller
In reply to Andrea della PortaThe BCM2712 has an SDHCI capable host interface similar to the one found in other STB chipsets. Add the relevant compatible string.
--- Documentation/devicetree/bindings/mmc/brcm,sdhci-brcmstb.yaml | 1 + 1 file changed, 1 insertion(+)
Documentation/devicetree/bindings/mmc/brcm,sdhci-brcmstb.yaml +1 -0
@@ -20,6 +20,7 @@ properties: - const: brcm,sdhci-brcmstb - items: - enum: + - brcm,bcm2712-sdhci - brcm,bcm74165b0-sdhci - brcm,bcm7445-sdhci - brcm,bcm7425-sdhci
Signature · 1 line
2.35.3
Re: [PATCH v4 2/4] dt-bindings: mmc: Add support for BCM2712 SD host controller
Am 28.05.24 um 15:32 schrieb Andrea della Porta:
Quoted 4 lines
The BCM2712 has an SDHCI capable host interface similar to the one found in other STB chipsets. Add the relevant compatible string.
Signed-off-by Andrea della Porta <[email protected]>
Re: [PATCH v4 2/4] dt-bindings: mmc: Add support for BCM2712 SD host controller
In reply to Andrea della PortaQuoted 5 lines · Andrea della Porta
The BCM2712 has an SDHCI capable host interface similar to the one found in other STB chipsets. Add the relevant compatible string.
Signed-off-by Andrea della Porta <[email protected]>---
Best regards,
Krzysztof
PATCH v4 3/4 mmc: sdhci-brcmstb: Add BCM2712 support
In reply to Andrea della PortaBroadcom BCM2712 SoC has an SDHCI card controller using the SDIO CFG register block present on other STB chips. Add support for BCM2712 SD capabilities of this chipset.
The silicon is SD Express capable but this driver port does not currently include that feature yet.
Based on downstream driver by raspberry foundation maintained kernel.
--- drivers/mmc/host/sdhci-brcmstb.c | 60 ++++++++++++++++++++++++++++++++ 1 file changed, 60 insertions(+)
drivers/mmc/host/sdhci-brcmstb.c +60 -0
@@ -30,6 +30,21 @@#define SDHCI_ARASAN_CQE_BASE_ADDR 0x200 +#define SDIO_CFG_CQ_CAPABILITY 0x4c +#define SDIO_CFG_CQ_CAPABILITY_FMUL GENMASK(13, 12) + +#define SDIO_CFG_CTRL 0x0 +#define SDIO_CFG_CTRL_SDCD_N_TEST_EN BIT(31) +#define SDIO_CFG_CTRL_SDCD_N_TEST_LEV BIT(30) + +#define SDIO_CFG_MAX_50MHZ_MODE 0x1ac +#define SDIO_CFG_MAX_50MHZ_MODE_STRAP_OVERRIDE BIT(31) +#define SDIO_CFG_MAX_50MHZ_MODE_ENABLE BIT(0) + +#define MMC_CAP_HSE_MASK (MMC_CAP2_HSX00_1_2V | MMC_CAP2_HSX00_1_8V) +/* Select all SD UHS type I SDR speed above 50MB/s */ +#define MMC_CAP_UHS_I_SDR_MASK (MMC_CAP_UHS_SDR50 | MMC_CAP_UHS_SDR104) +struct sdhci_brcmstb_priv {void __iomem *cfg_regs;unsigned int flags;
@@ -38,6 +53,7 @@ struct sdhci_brcmstb_priv { };struct brcmstb_match_priv { +void (*cfginit)(struct sdhci_host *host);void (*hs400es)(struct mmc_host *mmc,struct mmc_ios *ios);struct sdhci_ops *ops;const unsigned int flags;
@@ -168,6 +184,33 @@ static void sdhci_brcmstb_set_uhs_signaling(struct sdhci_host *host,sdhci_writew (host, ctrl_2,SDHCI_HOST_CONTROL2 ); } +static void sdhci_brcmstb_cfginit_2712 (struct sdhci_host *host) +{ +struct sdhci_pltfm_host *pltfm_host =sdhci_priv (host); +struct sdhci_brcmstb_priv *brcmstb_priv =sdhci_pltfm_priv (pltfm_host); +u32 reg, base_clk_mhz; + +/* +* If we support a speed that requires tuning, +* then select the delay line PHY as the clock source. +*/ +if ((host->mmc->caps &MMC_CAP_UHS_I_SDR_MASK ) || (host->mmc->caps2 &MMC_CAP_HSE_MASK )) { + reg =readl (brcmstb_priv->cfg_regs +SDIO_CFG_MAX_50MHZ_MODE ); + reg &= ~SDIO_CFG_MAX_50MHZ_MODE_ENABLE ; + reg |=SDIO_CFG_MAX_50MHZ_MODE_STRAP_OVERRIDE ; +writel (reg, brcmstb_priv->cfg_regs +SDIO_CFG_MAX_50MHZ_MODE ); + } + +if ((host->mmc->caps &MMC_CAP_NONREMOVABLE ) || + (host->mmc->caps &MMC_CAP_NEEDS_POLL )) { +/* Force presence */ + reg =readl (brcmstb_priv->cfg_regs +SDIO_CFG_CTRL ); + reg &= ~SDIO_CFG_CTRL_SDCD_N_TEST_LEV ; + reg |=SDIO_CFG_CTRL_SDCD_N_TEST_EN ; +writel (reg, brcmstb_priv->cfg_regs +SDIO_CFG_CTRL ); + } +} +static void sdhci_brcmstb_dumpregs (struct mmc_host *mmc) {sdhci_dumpregs (mmc_priv (mmc));
@@ -200,6 +243,14 @@ static struct sdhci_ops sdhci_brcmstb_ops = { .set_uhs_signaling = sdhci_set_uhs_signaling, }; +static struct sdhci_ops sdhci_brcmstb_ops_2712 = { + .set_clock = sdhci_set_clock, + .set_power = sdhci_set_power_and_bus_voltage, + .set_bus_width = sdhci_set_bus_width, + .reset = sdhci_reset, + .set_uhs_signaling = sdhci_set_uhs_signaling, +}; +static struct sdhci_ops sdhci_brcmstb_ops_7216 = { .set_clock = sdhci_brcmstb_set_clock, .set_bus_width = sdhci_set_bus_width,
@@ -214,6 +265,11 @@ static struct sdhci_ops sdhci_brcmstb_ops_74165b0 = { .set_uhs_signaling = sdhci_brcmstb_set_uhs_signaling, }; +static const struct brcmstb_match_priv match_priv_2712 = { + .cfginit = sdhci_brcmstb_cfginit_2712, + .ops = &sdhci_brcmstb_ops_2712, +}; +static struct brcmstb_match_priv match_priv_7425 = { .flags =BRCMSTB_MATCH_FLAGS_NO_64BIT |BRCMSTB_MATCH_FLAGS_BROKEN_TIMEOUT ,
@@ -238,6 +294,7 @@ static struct brcmstb_match_priv match_priv_74165b0 = { };static const struct of_device_id __maybe_unused sdhci_brcm_of_match[] = { + { .compatible ="brcm,bcm2712-sdhci" , .data = &match_priv_2712 }, { .compatible ="brcm,bcm7425-sdhci" , .data = &match_priv_7425 }, { .compatible ="brcm,bcm7445-sdhci" , .data = &match_priv_7445 }, { .compatible ="brcm,bcm7216-sdhci" , .data = &match_priv_7216 },
@@ -370,6 +427,9 @@ static int sdhci_brcmstb_probe(struct platform_device *pdev) (host->mmc->caps2 & MMC_CAP2_HS400_ES)) host->mmc_host_ops.hs400_enhanced_strobe = match_priv->hs400es; +if (match_priv->cfginit) + match_priv->cfginit (host); +/* * Supply the existing CAPS, but clear the UHS modes. This * will allow these modes to be specified by device tree
Signature · 1 line
2.35.3
Re: [PATCH v4 3/4] mmc: sdhci-brcmstb: Add BCM2712 support
Am 28.05.24 um 15:32 schrieb Andrea della Porta:
Quoted 8 lines
Broadcom BCM2712 SoC has an SDHCI card controller using the SDIO CFG register block present on other STB chips. Add support for BCM2712 SD capabilities of this chipset.
The silicon is SD Express capable but this driver port does not currently include that feature yet.
Based on downstream driver by raspberry foundation maintained kernel.Signed-off-by Andrea della Porta <[email protected]>
Re: [PATCH v4 3/4] mmc: sdhci-brcmstb: Add BCM2712 support
In reply to Andrea della PortaQuoted 8 lines · Andrea della Porta
Broadcom BCM2712 SoC has an SDHCI card controller using the SDIO CFG register block present on other STB chips. Add support for BCM2712 SD capabilities of this chipset.
The silicon is SD Express capable but this driver port does not currently include that feature yet.
Based on downstream driver by raspberry foundation maintained kernel.Signed-off-by Andrea della Porta <[email protected]>
One minor comment below, otherwise:
Also, unrelated to this patch, the driver has this code which looks like it would have an issue if there were 2 devices of the same type but only 1 had supports-cqe, because the ops would be shared they would both try to use sdhci_brcmstb_cqhci_irq().
if (device_property_read_bool(&pdev->dev, "supports-cqe")) {
priv->flags |= BRCMSTB_PRIV_FLAGS_HAS_CQE;
match_priv->ops->irq = sdhci_brcmstb_cqhci_irq;
}Quoted 39 lines
--- drivers/mmc/host/sdhci-brcmstb.c | 60 ++++++++++++++++++++++++++++++++ 1 file changed, 60 insertions(+)drivers/mmc/host/sdhci-brcmstb.c +16
-0@@ -30,6 +30,21 @@#define SDHCI_ARASAN_CQE_BASE_ADDR 0x200 +#define SDIO_CFG_CQ_CAPABILITY 0x4c +#define SDIO_CFG_CQ_CAPABILITY_FMUL GENMASK(13, 12) + +#define SDIO_CFG_CTRL 0x0 +#define SDIO_CFG_CTRL_SDCD_N_TEST_EN BIT(31) +#define SDIO_CFG_CTRL_SDCD_N_TEST_LEV BIT(30) + +#define SDIO_CFG_MAX_50MHZ_MODE 0x1ac +#define SDIO_CFG_MAX_50MHZ_MODE_STRAP_OVERRIDE BIT(31) +#define SDIO_CFG_MAX_50MHZ_MODE_ENABLE BIT(0) + +#define MMC_CAP_HSE_MASK (MMC_CAP2_HSX00_1_2V | MMC_CAP2_HSX00_1_8V) +/* Select all SD UHS type I SDR speed above 50MB/s */ +#define MMC_CAP_UHS_I_SDR_MASK (MMC_CAP_UHS_SDR50 | MMC_CAP_UHS_SDR104) +struct sdhci_brcmstb_priv {void __iomem *cfg_regs;unsigned int flags;@@ -38,6 +53,7 @@ struct sdhci_brcmstb_priv { };struct brcmstb_match_priv { +void (*cfginit)(struct sdhci_host *host);void (*hs400es)(struct mmc_host *mmc,struct mmc_ios *ios);struct sdhci_ops *ops;const unsigned int flags;
drivers/mmc/host/sdhci-brcmstb.c static void sdhci_brcmstb_set_uhs_signaling(struct sdhci_host *host, · line 191
Quoted 8 lines
drivers/mmc/host/sdhci-brcmstb.c +5
-0@@ -168,6 +184,33 @@ static void sdhci_brcmstb_set_uhs_signaling(struct sdhci_host *host,sdhci_writew (host, ctrl_2,SDHCI_HOST_CONTROL2 ); } +static void sdhci_brcmstb_cfginit_2712 (struct sdhci_host *host) +{ +struct sdhci_pltfm_host *pltfm_host =sdhci_priv (host); +struct sdhci_brcmstb_priv *brcmstb_priv =sdhci_pltfm_priv (pltfm_host); +u32 reg, base_clk_mhz;
drivers/mmc/host/sdhci-brcmstb.c: In function ‘sdhci_brcmstb_cfginit_2712’:drivers/mmc/host/sdhci-brcmstb.c:191:18: error: unused variable ‘base_clk_mhz’ [-Werror=unused-variable]
191 | u32 reg, base_clk_mhz;
| ^~~~~~~~~~~~Quoted 70 lines
drivers/mmc/host/sdhci-brcmstb.c +39
-0+ +/* +* If we support a speed that requires tuning, +* then select the delay line PHY as the clock source. +*/ +if ((host->mmc->caps &MMC_CAP_UHS_I_SDR_MASK ) || (host->mmc->caps2 &MMC_CAP_HSE_MASK )) { + reg =readl (brcmstb_priv->cfg_regs +SDIO_CFG_MAX_50MHZ_MODE ); + reg &= ~SDIO_CFG_MAX_50MHZ_MODE_ENABLE ; + reg |=SDIO_CFG_MAX_50MHZ_MODE_STRAP_OVERRIDE ; +writel (reg, brcmstb_priv->cfg_regs +SDIO_CFG_MAX_50MHZ_MODE ); + } + +if ((host->mmc->caps &MMC_CAP_NONREMOVABLE ) || + (host->mmc->caps &MMC_CAP_NEEDS_POLL )) { +/* Force presence */ + reg =readl (brcmstb_priv->cfg_regs +SDIO_CFG_CTRL ); + reg &= ~SDIO_CFG_CTRL_SDCD_N_TEST_LEV ; + reg |=SDIO_CFG_CTRL_SDCD_N_TEST_EN ; +writel (reg, brcmstb_priv->cfg_regs +SDIO_CFG_CTRL ); + } +} +static void sdhci_brcmstb_dumpregs (struct mmc_host *mmc) {sdhci_dumpregs (mmc_priv (mmc));@@ -200,6 +243,14 @@ static struct sdhci_ops sdhci_brcmstb_ops = { .set_uhs_signaling = sdhci_set_uhs_signaling, }; +static struct sdhci_ops sdhci_brcmstb_ops_2712 = { + .set_clock = sdhci_set_clock, + .set_power = sdhci_set_power_and_bus_voltage, + .set_bus_width = sdhci_set_bus_width, + .reset = sdhci_reset, + .set_uhs_signaling = sdhci_set_uhs_signaling, +}; +static struct sdhci_ops sdhci_brcmstb_ops_7216 = { .set_clock = sdhci_brcmstb_set_clock, .set_bus_width = sdhci_set_bus_width,@@ -214,6 +265,11 @@ static struct sdhci_ops sdhci_brcmstb_ops_74165b0 = { .set_uhs_signaling = sdhci_brcmstb_set_uhs_signaling, }; +static const struct brcmstb_match_priv match_priv_2712 = { + .cfginit = sdhci_brcmstb_cfginit_2712, + .ops = &sdhci_brcmstb_ops_2712, +}; +static struct brcmstb_match_priv match_priv_7425 = { .flags =BRCMSTB_MATCH_FLAGS_NO_64BIT |BRCMSTB_MATCH_FLAGS_BROKEN_TIMEOUT ,@@ -238,6 +294,7 @@ static struct brcmstb_match_priv match_priv_74165b0 = { };static const struct of_device_id __maybe_unused sdhci_brcm_of_match[] = { + { .compatible ="brcm,bcm2712-sdhci" , .data = &match_priv_2712 }, { .compatible ="brcm,bcm7425-sdhci" , .data = &match_priv_7425 }, { .compatible ="brcm,bcm7445-sdhci" , .data = &match_priv_7445 }, { .compatible ="brcm,bcm7216-sdhci" , .data = &match_priv_7216 },@@ -370,6 +427,9 @@ static int sdhci_brcmstb_probe(struct platform_device *pdev) (host->mmc->caps2 & MMC_CAP2_HS400_ES)) host->mmc_host_ops.hs400_enhanced_strobe = match_priv->hs400es; +if (match_priv->cfginit) + match_priv->cfginit (host); +/* * Supply the existing CAPS, but clear the UHS modes. This * will allow these modes to be specified by device tree
PATCH v4 4/4 arm64: dts: broadcom: Add support for BCM2712
In reply to Andrea della PortaThe BCM2712 SoC family can be found on Raspberry Pi 5. Add minimal SoC and board (Rpi5 specific) dts file to be able to boot from SD card and use console on debug UART.
--- arch/arm64/boot/dts/broadcom/Makefile | 1 + .../boot/dts/broadcom/bcm2712-rpi-5-b.dts | 64 ++++ arch/arm64/boot/dts/broadcom/bcm2712.dtsi | 292 ++++++++++++++++++ 3 files changed, 357 insertions(+) create mode 100644 arch/arm64/boot/dts/broadcom/bcm2712-rpi-5-b.dts create mode 100644 arch/arm64/boot/dts/broadcom/bcm2712.dtsi
arch/arm64/boot/dts/broadcom/Makefile +1 -0
@@ -6,6 +6,7 @@ DTC_FLAGS := -@ dtb-$(CONFIG_ARCH_BCM2835) += bcm2711-rpi-400.dtb \ bcm2711-rpi-4-b.dtb \ bcm2711-rpi-cm4-io.dtb \ + bcm2712-rpi-5-b.dtb \ bcm2837-rpi-3-a-plus.dtb \ bcm2837-rpi-3-b.dtb \ bcm2837-rpi-3-b-plus.dtb \
arch/arm64/boot/dts/broadcom/bcm2712-rpi-5-b.dts new file +64 -0
64 lines not on this page · raw message
arch/arm64/boot/dts/broadcom/bcm2712.dtsi new file +292 -0
292 lines not on this page · raw message
Signature · 1 line
2.35.3
Florian Fainelli
maintainerRe: [PATCH v4 4/4] arm64: dts: broadcom: Add support for BCM2712
Quoted 6 lines · Andrea della Porta
The BCM2712 SoC family can be found on Raspberry Pi 5. Add minimal SoC and board (Rpi5 specific) dts file to be able to boot from SD card and use console on debug UART.
Signed-off-by Andrea della Porta <[email protected]>---
[snip]
Quoted 12 lines
arch/arm64/boot/dts/broadcom/bcm2712.dtsi new file +6
-0@@ -0,0 +1,292 @@ +// SPDX-License-Identifier: (GPL-2.0 OR MIT) +#include <dt-bindings/interrupt-controller/arm-gic.h> + +/ { + compatible = "brcm,bcm2712"; +
arch/arm64/boot/dts/broadcom/bcm2712.dtsi line 16
Quoted 10 lines
arch/arm64/boot/dts/broadcom/bcm2712.dtsi new file +10
-0+ #address-cells = <2>; + #size-cells = <2>; + + interrupt-parent = <&gicv2>; + + axi: axi@1000000000 { + compatible = "simple-bus"; + #address-cells = <2>; + #size-cells = <2>; + ranges = <0x10 0x00000000 0x10 0x00000000 0x01 0x00000000>;
That property does not look correct, you want to define an aperture that starts at 0x10_0000_0000 into the CPU's address space, and then have sub-node(s) whose "reg" property is to be encoded using #address-cells = <1> and #size-cells = <1> because that's enough to represent that address space.
arch/arm64/boot/dts/broadcom/bcm2712.dtsi line 22
Quoted 6 lines
arch/arm64/boot/dts/broadcom/bcm2712.dtsi new file +6
-0+ + sdio1: mmc@1000fff000 { + compatible = "brcm,bcm2712-sdhci", + "brcm,sdhci-brcmstb"; + reg = <0x10 0x00fff000 0x0 0x260>, + <0x10 0x00fff400 0x0 0x200>;
That "reg" property should not be including the 0x10_0000_0000 offset at all, and we should just have:
reg = <0xfff000 0x260>, <0xfff400 0x200>;
Quoted 5 lines
arch/arm64/boot/dts/broadcom/bcm2712.dtsi new file +5
-0+ reg-names = "host", "cfg"; + interrupts = <GIC_SPI 273 IRQ_TYPE_LEVEL_HIGH>; + clocks = <&clk_emmc2>; + clock-names = "sw_sdio"; + mmc-ddr-3_3v;
arch/arm64/boot/dts/broadcom/bcm2712.dtsi line 37
Quoted 10 lines
arch/arm64/boot/dts/broadcom/bcm2712.dtsi new file +10
-0+ }; + + gicv2: interrupt-controller@107fff9000 { + interrupt-controller; + #interrupt-cells = <3>; + compatible = "arm,gic-400"; + reg = <0x10 0x7fff9000 0x0 0x1000>, + <0x10 0x7fffa000 0x0 0x2000>, + <0x10 0x7fffc000 0x0 0x2000>, + <0x10 0x7fffe000 0x0 0x2000>;
Likewise, this is supposed to be:
reg = <0x7fff9000 0x1000>, <0x7fffa000 0x2000>, <0x7fffc000 0x2000>, <0x7fffe000 0x2000>;
[snip]
arch/arm64/boot/dts/broadcom/bcm2712.dtsi line 223
Quoted 7 lines
arch/arm64/boot/dts/broadcom/bcm2712.dtsi new file +7
-0+ + soc: soc@107c000000 { + compatible = "simple-bus"; + #address-cells = <1>; + #size-cells = <1>; + + ranges = <0x7c000000 0x10 0x7c000000 0x04000000>;
That spans the previously defined axi node above (goes up to 0x10_8000_0000), once we make the necessary "ranges" adjustments to the axi node as indicated before.
I thought that based upon our conversation in v3, this was all going to be a single "soc" node?
Quoted 41 lines
arch/arm64/boot/dts/broadcom/bcm2712.dtsi new file +41
-0+ /* Emulate a contiguous 30-bit address range for DMA */ + dma-ranges = <0xc0000000 0x00 0x00000000 0x40000000>, + <0x7c000000 0x10 0x7c000000 0x04000000>; + + system_timer: timer@7c003000 { + compatible = "brcm,bcm2835-system-timer"; + reg = <0x7c003000 0x1000>; + interrupts = <GIC_SPI 64 IRQ_TYPE_LEVEL_HIGH>, + <GIC_SPI 65 IRQ_TYPE_LEVEL_HIGH>, + <GIC_SPI 66 IRQ_TYPE_LEVEL_HIGH>, + <GIC_SPI 67 IRQ_TYPE_LEVEL_HIGH>; + clock-frequency = <1000000>; + }; + + mailbox: mailbox@7c013880 { + compatible = "brcm,bcm2835-mbox"; + reg = <0x7c013880 0x40>; + interrupts = <GIC_SPI 33 IRQ_TYPE_LEVEL_HIGH>; + #mbox-cells = <0>; + }; + + local_intc: local-intc@7cd00000 { + compatible = "brcm,bcm2836-l1-intc"; + reg = <0x7cd00000 0x100>; + }; + + uart10: serial@7d001000 { + compatible = "arm,pl011", "arm,primecell"; + reg = <0x7d001000 0x200>; + interrupts = <GIC_SPI 121 IRQ_TYPE_LEVEL_HIGH>; + clocks = <&clk_uart>, <&clk_vpu>; + clock-names = "uartclk", "apb_pclk"; + arm,primecell-periphid = <0x00241011>; + status = "disabled"; + }; + + interrupt-controller@7d517000 { + compatible = "brcm,bcm7271-l2-intc"; + reg = <0x7d517000 0x10>; + interrupts = <GIC_SPI 247 IRQ_TYPE_LEVEL_HIGH>; + interrupt-controller;
arch/arm64/boot/dts/broadcom/bcm2712.dtsi line 274
Quoted 10 lines
arch/arm64/boot/dts/broadcom/bcm2712.dtsi new file +10
-0+ #interrupt-cells = <1>; + }; + + gio_aon: gpio@7d517c00 { + compatible = "brcm,bcm7445-gpio", "brcm,brcmstb-gpio"; + reg = <0x7d517c00 0x40>; + gpio-controller; + #gpio-cells = <2>; + // Don't use GIO_AON as an interrupt controller because it will + // clash with the firmware monitoring the PMIC interrupt via the VPU.
OK, so the comment is intended to explain why there is no 'interrupt-controller' property specified when one might expect to find one, and it has nothing to do with the "brcm,gpio-bank-widths" property, because that one is correct and does indicate the number of pins that need to be managed per bank. Some clarification is warranted here IMHO.
Signature · 1 line
Florian
Re: [PATCH v4 4/4] arm64: dts: broadcom: Add support for BCM2712
In reply to Andrea della PortaHi Andrea,
i think the following subject would be better:
arm64: dts: broadcom: Add minimal support for Raspberry Pi 5
because you also add the board file here.
Am 28.05.24 um 15:32 schrieb Andrea della Porta:
Quoted 128 lines
The BCM2712 SoC family can be found on Raspberry Pi 5. Add minimal SoC and board (Rpi5 specific) dts file to be able to boot from SD card and use console on debug UART.
Signed-off-by Andrea della Porta <[email protected]>--- arch/arm64/boot/dts/broadcom/Makefile | 1 + .../boot/dts/broadcom/bcm2712-rpi-5-b.dts | 64 ++++ arch/arm64/boot/dts/broadcom/bcm2712.dtsi | 292 ++++++++++++++++++ 3 files changed, 357 insertions(+)create mode 100644
arch/arm64/boot/dts/broadcom/bcm2712-rpi-5-b.dtscreate mode 100644arch/arm64/boot/dts/broadcom/bcm2712.dtsiarch/arm64/boot/dts/broadcom/Makefile +1
-0@@ -6,6 +6,7 @@ DTC_FLAGS := -@ dtb-$(CONFIG_ARCH_BCM2835) += bcm2711-rpi-400.dtb \ bcm2711-rpi-4-b.dtb \ bcm2711-rpi-cm4-io.dtb \ + bcm2712-rpi-5-b.dtb \ bcm2837-rpi-3-a-plus.dtb \ bcm2837-rpi-3-b.dtb \ bcm2837-rpi-3-b-plus.dtb \arch/arm64/boot/dts/broadcom/bcm2712-rpi-5-b.dts new file +64
-0@@ -0,0 +1,64 @@ +// SPDX-License-Identifier: (GPL-2.0 OR MIT) +/dts-v1/; + +#include <dt-bindings/gpio/gpio.h> +#include "bcm2712.dtsi" + +/ { + compatible = "raspberrypi,5-model-b", "brcm,bcm2712"; + model = "Raspberry Pi 5"; + + aliases { + serial10 = &uart10; + }; + + chosen: chosen { + stdout-path = "serial10:115200n8"; + }; + + /* Will be filled by the bootloader */ + memory@0 { + device_type = "memory"; + reg = <0 0 0 0x28000000>; + }; + + sd_io_1v8_reg: sd-io-1v8-reg { + compatible = "regulator-gpio"; + regulator-name = "vdd-sd-io"; + regulator-min-microvolt = <1800000>; + regulator-max-microvolt = <3300000>; + regulator-boot-on; + regulator-always-on; + regulator-settling-time-us = <5000>; + gpios = <&gio_aon 3 GPIO_ACTIVE_HIGH>; + states = <1800000 1>, + <3300000 0>; + }; + + sd_vcc_reg: sd-vcc-reg { + compatible = "regulator-fixed"; + regulator-name = "vcc-sd"; + regulator-min-microvolt = <3300000>; + regulator-max-microvolt = <3300000>; + regulator-boot-on; + enable-active-high; + gpios = <&gio_aon 4 GPIO_ACTIVE_HIGH>; + }; +}; + +/* The Debug UART, on Rpi5 it's on JST-SH 1.0mm 3-pin connector + * labeled "UART", i.e. the interface with the system console. + */ +&uart10 { + status = "okay"; +}; + +/* SDIO1 is used to drive the SD card */ +&sdio1 { + vqmmc-supply = <&sd_io_1v8_reg>; + vmmc-supply = <&sd_vcc_reg>; + bus-width = <4>; + sd-uhs-sdr50; + sd-uhs-ddr50; + sd-uhs-sdr104; +};arch/arm64/boot/dts/broadcom/bcm2712.dtsi new file +27
-0@@ -0,0 +1,292 @@ +// SPDX-License-Identifier: (GPL-2.0 OR MIT) +#include <dt-bindings/interrupt-controller/arm-gic.h> + +/ { + compatible = "brcm,bcm2712"; + + #address-cells = <2>; + #size-cells = <2>; + + interrupt-parent = <&gicv2>; + + axi: axi@1000000000 { + compatible = "simple-bus"; + #address-cells = <2>; + #size-cells = <2>; + ranges = <0x10 0x00000000 0x10 0x00000000 0x01 0x00000000>; + + sdio1: mmc@1000fff000 { + compatible = "brcm,bcm2712-sdhci", + "brcm,sdhci-brcmstb"; + reg = <0x10 0x00fff000 0x0 0x260>, + <0x10 0x00fff400 0x0 0x200>; + reg-names = "host", "cfg"; + interrupts = <GIC_SPI 273 IRQ_TYPE_LEVEL_HIGH>; + clocks = <&clk_emmc2>; + clock-names = "sw_sdio"; + mmc-ddr-3_3v;
arch/arm64/boot/dts/broadcom/bcm2712.dtsi line 37
Quoted 10 lines
arch/arm64/boot/dts/broadcom/bcm2712.dtsi new file +10
-0+ }; + + gicv2: interrupt-controller@107fff9000 { + interrupt-controller; + #interrupt-cells = <3>; + compatible = "arm,gic-400"; + reg = <0x10 0x7fff9000 0x0 0x1000>, + <0x10 0x7fffa000 0x0 0x2000>, + <0x10 0x7fffc000 0x0 0x2000>, + <0x10 0x7fffe000 0x0 0x2000>;
Please move compatible and reg before the other properties (DTS coding style)
Quoted 8 lines
arch/arm64/boot/dts/broadcom/bcm2712.dtsi new file +8
-0+ }; + }; + + clocks { + /* The oscillator is the root of the clock tree. */ + clk_osc: clk-osc { + compatible = "fixed-clock"; + #clock-cells = <0>;
arch/arm64/boot/dts/broadcom/bcm2712.dtsi line 55
Quoted 10 lines
arch/arm64/boot/dts/broadcom/bcm2712.dtsi new file +10
-0+ clock-output-names = "osc"; + clock-frequency = <54000000>; + }; + + clk_vpu: clk-vpu { + #clock-cells = <0>; + compatible = "fixed-clock"; + clock-frequency = <750000000>; + clock-output-names = "vpu-clock"; + };
Is the VPU clock really fixed or is it just a workaround for minimal boot support?
Except of this, LGTM
Re: [PATCH v4 4/4] arm64: dts: broadcom: Add support for BCM2712
Hi Stefan,
On 08:11 Thu 30 May , Stefan Wahren wrote:
[cut...]
Quoted 9 lines
Quoted 9 lines
arch/arm64/boot/dts/broadcom/bcm2712.dtsi new file +9
-0+ clocks { + /* The oscillator is the root of the clock tree. */ + clk_osc: clk-osc { + compatible = "fixed-clock"; + #clock-cells = <0>; + clock-output-names = "osc"; + clock-frequency = <54000000>; + }; +
Quoted 8 lines
arch/arm64/boot/dts/broadcom/bcm2712.dtsi line 55
Quoted 6 lines
arch/arm64/boot/dts/broadcom/bcm2712.dtsi new file +6
-0+ clk_vpu: clk-vpu { + #clock-cells = <0>; + compatible = "fixed-clock"; + clock-frequency = <750000000>; + clock-output-names = "vpu-clock"; + };Is the VPU clock really fixed or is it just a workaround for minimal boot support?
Unfortunately I don't have enough insight on this due to lack of documentation. I had to take it by faith from downstream dts.
Many thanks,
Andrea
Rob Herring (Arm)
maintainerQuoted 112 lines · Andrea della Porta
Hi,
This patchset adds minimal support for the Broadcom BCM2712 SoC and for the on-board SDHCI controller on Broadcom BCM2712 in order to make it possible to boot (particularly) a Raspberry Pi 5 from SD card and get a console through uart.
Changes to arm64/defconfig are not needed since the actual options work as they are.
This work is heavily based on downstream contributions.Tested on Tumbleweed substituting the stock kernel with upstream one, either chainloading uboot+grub+kernel or directly booting the kernel from 1st stage bootloader. Steps to reproduce:
- prepare an SD card from a Raspberry enabled raw image, mount the first FAT partition.
- make sure the FAT partition is big enough to contain the kernel, anything bigger than 64Mb is usually enough, depending on your kernel config options.
- build the kernel and dtbs making sure that the support for your root fs type is compiled as builtin.
- copy the kernel image in your FAT partition overwriting the older one (e.g. kernel*.img for Raspberry Pi OS or u-boot.bin for Tumbleweed).
- copyarch/arm64/boot/dts/broadcom/bcm2712-rpi-5-b.dtbon FAT partition.
- make sure you have a cmdline.txt file in FAT partition with the following content:# cat /boot/efi/cmdline.txt root=/dev/mmcblk0p3 rootwait rw console=tty ignore_loglevel earlycon console=ttyAMA10,115200 - if you experience random SD issues during boot, try to set initial_turbo=0 in config.txt.Changes in V4:
sdhci-brcmstb.c:
- dropped the last 4 lines ofsdhci_brcmstb_cfginit_2712()function to avoid setting theSDIO_CFG_CQ_CAPABILITYregister. The rationale behind this can be found in [4] and subsequent commentsDT-bindings:
- simplified the compatible item list for 'brcm,bcm2712-sdhci' as per [5]Changes in V3:
DTS:
- uart0 renamed to uart10 to reflect the current indexing (ttyAMA10 and serial10)
- updated the license to (GPL-2.0 OR MIT)
-sd_io_1v8_reg'states' property have second cells as decimal instead of hex.
- root node has size-cells=<2> now to accommodate for the DRAM controller and the address bus mapping that goes beyond 4GB. As a consequence, memory, axi and reserved-memory nodes have also size-cells=<2> and subnodes reg and ranges properties have been updated accordingly
- ranges property in 'axi' node has been fixed, reg properties of sdio1 and gicv2 subnodes have been adjusted according to the new mapping
- 'interrupt-controller@7d517000' node is now enabled by default
- dropped 'arm,cpu-registers-not-fw-configured' as it is no longer relevant on A76 core
- l2 cache nodes moved under respective cpus, since they are per-cpu
- dropped psci cpu functions properties
- added the hypervisor EL2 virtual timer interrupt to the 'timer' node
- splitted-lines url are now on a single line
sdhci-brcmstb.c:
- simplifiedMMC_CAP_HSE_MASKleveraging already existing definitions
-MMC_CAP_UHS_MASKrenamed toMMC_CAP_UHS_I_SDR_MASKto better reflect its purpose. Added also a comment.
-sdhci_brcmstb_set_power()replaced with the already existing (and equivalent)sdhci_set_power_and_bus_voltage()DT-bindings:
- removed the BCM2712 specific example, as per Rob's request.Changes in V2:
- the patchshet has been considerably simplified, both in terms of dts and driver code. Notably, the pinctrl/pinmux driver (and associated binding) was not strictly needed to use the SD card so it has been dropped
- dropped the optional SD express support patch
- the patches order has been revisited
- pass all checks (binding, dtb, checkpatch)Many thanks,
AndreaReferences:
[1] - Link to V1: https://lore.kernel.org/all/[email protected]/
[2] - Link to V2: https://lore.kernel.org/all/[email protected]/
[3] - Link to V3: https://lore.kernel.org/all/[email protected]/
[4] - https://lore.kernel.org/all/ZlF5dQbNpZ921e66@apocalypse/
[5] - https://lore.kernel.org/all/[email protected]/#tAndrea della Porta (4):
dt-bindings: arm: bcm: Add BCM2712 SoC support
dt-bindings: mmc: Add support for BCM2712 SD host controller
mmc: sdhci-brcmstb: Add BCM2712 support
arm64: dts: broadcom: Add support for BCM2712.../devicetree/bindings/arm/bcm/bcm2835.yaml | 6 + .../bindings/mmc/brcm,sdhci-brcmstb.yaml | 1 + arch/arm64/boot/dts/broadcom/Makefile | 1 + .../boot/dts/broadcom/bcm2712-rpi-5-b.dts | 64 ++++ arch/arm64/boot/dts/broadcom/bcm2712.dtsi | 292 ++++++++++++++++++ drivers/mmc/host/sdhci-brcmstb.c | 60 ++++ 6 files changed, 424 insertions(+) create mode 100644 arch/arm64/boot/dts/broadcom/bcm2712-rpi-5-b.dts create mode 100644 arch/arm64/boot/dts/broadcom/bcm2712.dtsi
Quoted 5 lines
--
2.35.3
My bot found new DTB warnings on the .dts files added or changed in this series.
Some warnings may be from an existing SoC .dtsi. Or perhaps the warnings are fixed by another series. Ultimately, it is up to the platform maintainer whether these warnings are acceptable or not. No need to reply unless the platform maintainer has comments.
If you already ran DT checks and didn't see these error(s), then make sure dt-schema is up to date:
pip3 install dtschema --upgrade
New warnings running 'make CHECK_DTBS=y broadcom/bcm2712-rpi-5-b.dtb' for [email protected]:
arch/arm64/boot/dts/broadcom/bcm2712-rpi-5-b.dtb: /soc@107c000000/timer@7c003000: failed to match any schema with compatible: ['brcm,bcm2835-system-timer'] arch/arm64/boot/dts/broadcom/bcm2712-rpi-5-b.dtb: /soc@107c000000/local-intc@7cd00000: failed to match any schema with compatible: ['brcm,bcm2836-l1-intc']