summaryrefslogtreecommitdiff
path: root/arch/arm/dts/bcm2835-rpi-a.dts
diff options
context:
space:
mode:
authorSimon Glass <sjg@chromium.org>2021-12-16 20:59:13 -0700
committerTom Rini <trini@konsulko.com>2021-12-23 10:24:39 -0500
commit9ae600e9e280f48d7c56dae891dbe1497d633ad7 (patch)
tree7aca8f8d14a2103371bb0e817d22d09aee1d7f77 /arch/arm/dts/bcm2835-rpi-a.dts
parent4027792090dd1f4e4f77082151086df5aea62e63 (diff)
downloadu-boot-9ae600e9e280f48d7c56dae891dbe1497d633ad7.tar.gz
u-boot-9ae600e9e280f48d7c56dae891dbe1497d633ad7.tar.bz2
u-boot-9ae600e9e280f48d7c56dae891dbe1497d633ad7.zip
arm: rpi: Sync rpi dts files from Linux
Sync these files, obtained from Linux v5.15. This adds a devicetree file for rpi_4 which was not there before. Testing shows no change so far as I can see: - boots to U-Boot prompt on rpi0, rpi2 - boots to distro on rpi3 - boots to distro on rpi4 I am assuming that syncing with Linux is safe, but the maintainer should know for sure. Signed-off-by: Simon Glass <sjg@chromium.org>
Diffstat (limited to 'arch/arm/dts/bcm2835-rpi-a.dts')
-rw-r--r--arch/arm/dts/bcm2835-rpi-a.dts16
1 files changed, 15 insertions, 1 deletions
diff --git a/arch/arm/dts/bcm2835-rpi-a.dts b/arch/arm/dts/bcm2835-rpi-a.dts
index 067d1f07a2..11edb581db 100644
--- a/arch/arm/dts/bcm2835-rpi-a.dts
+++ b/arch/arm/dts/bcm2835-rpi-a.dts
@@ -8,8 +8,13 @@
compatible = "raspberrypi,model-a", "brcm,bcm2835";
model = "Raspberry Pi Model A";
+ memory@0 {
+ device_type = "memory";
+ reg = <0 0x10000000>;
+ };
+
leds {
- act {
+ led-act {
gpios = <&gpio 16 GPIO_ACTIVE_LOW>;
};
};
@@ -94,6 +99,8 @@
&hdmi {
hpd-gpios = <&gpio 46 GPIO_ACTIVE_HIGH>;
+ power-domains = <&power RPI_POWER_DOMAIN_HDMI>;
+ status = "okay";
};
&pwm {
@@ -102,6 +109,13 @@
status = "okay";
};
+&sdhost {
+ pinctrl-names = "default";
+ pinctrl-0 = <&sdhost_gpio48>;
+ bus-width = <4>;
+ status = "okay";
+};
+
&uart0 {
pinctrl-names = "default";
pinctrl-0 = <&uart0_gpio14>;