From: Sascha Hauer <s.hauer@pengutronix.de>
To: Barebox List <barebox@lists.infradead.org>
Subject: [PATCH 1/2] ARM: vexpress: Disable non working devices
Date: Tue, 25 Apr 2023 15:35:34 +0200 [thread overview]
Message-ID: <20230425133535.273920-1-s.hauer@pengutronix.de> (raw)
Disable some non working devices in the vexpress dts files to
avoid error messages during runtime. vexpress_defconfig has the
drivers for these devices disabled, but with multi_v7_defconfig
the driver are enabled. To make vexpress more usable with
multi_v7_defconfig disable the non working devices in the device
tree.
/timer@1e000600 doesn't work because our arm,cortex-a9-twd-timer
implementation needs a clock which the dts doesn't provide. We don't
need this as we use another timer anyway.
/bus@40000000/motherboard-bus@40000000/leds/ and /leds/ are a gpio-leds
devices which need a GPIO driver which doesn't exist in barebox
/bus@40000000/motherboard-bus@40000000/iofpga@7,00000000/compact-flash@1a000/
/bus@8000000/motherboard-bus@8000000/iofpga-bus@300000000/compact-flash@1a0000/
are ata-generic devices. The driver times out probing the device. While
it doesn't issue an error message it delays starting up the board for
several seconds.
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
---
arch/arm/dts/vexpress-v2p-ca15.dts | 8 ++++++++
arch/arm/dts/vexpress-v2p-ca9.dts | 12 ++++++++++++
2 files changed, 20 insertions(+)
diff --git a/arch/arm/dts/vexpress-v2p-ca15.dts b/arch/arm/dts/vexpress-v2p-ca15.dts
index 78d0025909..cdf7bd37d5 100644
--- a/arch/arm/dts/vexpress-v2p-ca15.dts
+++ b/arch/arm/dts/vexpress-v2p-ca15.dts
@@ -28,3 +28,11 @@
};
};
};
+
+&{/leds} {
+ status = "disabled";
+};
+
+&{/bus@8000000/motherboard-bus@8000000/iofpga-bus@300000000/compact-flash@1a0000/} {
+ status = "disabled";
+};
diff --git a/arch/arm/dts/vexpress-v2p-ca9.dts b/arch/arm/dts/vexpress-v2p-ca9.dts
index a43628e7ce..113548bedb 100644
--- a/arch/arm/dts/vexpress-v2p-ca9.dts
+++ b/arch/arm/dts/vexpress-v2p-ca9.dts
@@ -91,3 +91,15 @@
};
};
};
+
+&{/timer@1e000600} {
+ status = "disabled";
+};
+
+&{/bus@40000000/motherboard-bus@40000000/leds/} {
+ status = "disabled";
+};
+
+&{/bus@40000000/motherboard-bus@40000000/iofpga@7,00000000/compact-flash@1a000/} {
+ status = "disabled";
+};
--
2.39.2
next reply other threads:[~2023-04-25 13:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-25 13:35 Sascha Hauer [this message]
2023-04-25 13:35 ` [PATCH 2/2] ARM: remove vexpress_defconfig 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=20230425133535.273920-1-s.hauer@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@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