From: Ben Schneider <ben@bens.haus>
To: Linux Arm Kernel <linux-arm-kernel@lists.infradead.org>
Subject: [PATCH] arm64: dts: marvell: Fix espressobin-ultra boot failure and wifi
Date: Fri, 26 May 2023 18:14:06 +0200 (CEST) [thread overview]
Message-ID: <NWNpfIn--3-9@bens.haus> (raw)
Boot hangs on EspressoBIN Ultra (Armada 3720) after a message that device
vcc_sd1 had been disabled. The device manufacturer patched this issue in
their kernel fork noting that vcc_sd1 is used by the EspressoBIN model
but not the EspressoBIN Ultra. Removing the device from the tree fixes
the boot hang and wifi.
Link: https://github.com/globalscaletechnologies/linux/commit/b879d560eebf2766781614a0169a9564f1e0fc06
Signed-off-by: Ben Schneider <ben@bens.haus>
---
arch/arm64/boot/dts/marvell/armada-3720-espressobin-ultra.dts | 3 +++
1 file changed, 3 insertions(+)
diff --git a/arch/arm64/boot/dts/marvell/armada-3720-espressobin-ultra.dts b/arch/arm64/boot/dts/marvell/armada-3720-espressobin-ultra.dts
index d29d2da95..f9abef8dc 100644
--- a/arch/arm64/boot/dts/marvell/armada-3720-espressobin-ultra.dts
+++ b/arch/arm64/boot/dts/marvell/armada-3720-espressobin-ultra.dts
@@ -24,6 +24,8 @@
ethernet5 = &switch0port4;
};
+ /delete-node/ regulator;
+
reg_usb3_vbus: usb3-vbus {
compatible = "regulator-fixed";
regulator-name = "usb3-vbus";
@@ -66,6 +68,7 @@
};
&sdhci1 {
+ /delete-property/ vqmmc-supply;
status = "disabled";
};
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2023-05-26 16:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-26 16:14 Ben Schneider [this message]
2023-05-29 16:06 ` [PATCH] arm64: dts: marvell: Fix espressobin-ultra boot failure and wifi Andrew Lunn
2023-05-30 15:41 ` Ben Schneider
2023-05-31 9:20 ` Gregory CLEMENT
2023-05-31 15:47 ` Ben Schneider
2023-06-02 7:02 ` Gregory CLEMENT
2023-06-03 5:23 ` Ben Schneider
2023-06-16 12:05 ` Gregory CLEMENT
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=NWNpfIn--3-9@bens.haus \
--to=ben@bens.haus \
--cc=linux-arm-kernel@lists.infradead.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).