From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: barebox@lists.infradead.org
Cc: lst@pengutronix.de, mfe@pengutronix.de,
Ahmad Fatoum <a.fatoum@pengutronix.de>
Subject: [PATCH master 3/3] ARM: i.MX8MN: assume USBOTG power domains to be powered
Date: Sat, 30 Jul 2022 11:52:11 +0200 [thread overview]
Message-ID: <20220730095211.1769119-3-a.fatoum@pengutronix.de> (raw)
In-Reply-To: <20220730095211.1769119-1-a.fatoum@pengutronix.de>
When i.MX8MN support was first added, upstream device tree did list no
power domains. Now it does and we defer probe of USB indefinitely
because we have no power domain driver. If we need to do PCI on the
i.MX8MM in barebox, there'll likely be no way around importing the power
domain driver, but for USB which used to work, only thing we need to do
is ignore the new power domain specification. Do so by adding the
new barebox,allow-dummy property to the new known-enabled power domain.
Fixes: b01786baa849 ("dts: update to v5.18-rc1")
Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
---
Untested on actual i.MX8MN HW, but close enough i.MX8MM. i.MX8MP is
also affect since v5.19-rc1 sync, but we have no USB support there yet.
Power domains also seems more complicated on 8MPlus where we have a
blk-ctrl power domain driver in-between usbotg and gpcv2.
---
arch/arm/dts/imx8mn-evk.dtsi | 2 ++
arch/arm/dts/imx8mn.dtsi | 5 +++++
2 files changed, 7 insertions(+)
create mode 100644 arch/arm/dts/imx8mn.dtsi
diff --git a/arch/arm/dts/imx8mn-evk.dtsi b/arch/arm/dts/imx8mn-evk.dtsi
index ceeb5f8b9384..aeb357007991 100644
--- a/arch/arm/dts/imx8mn-evk.dtsi
+++ b/arch/arm/dts/imx8mn-evk.dtsi
@@ -4,6 +4,8 @@
* Copyright (C) 2017 Pengutronix, Lucas Stach <kernel@pengutronix.de>
*/
+#include "imx8mn.dtsi"
+
/ {
chosen {
environment-sd {
diff --git a/arch/arm/dts/imx8mn.dtsi b/arch/arm/dts/imx8mn.dtsi
new file mode 100644
index 000000000000..176125e73bce
--- /dev/null
+++ b/arch/arm/dts/imx8mn.dtsi
@@ -0,0 +1,5 @@
+// SPDX-License-Identifier: (GPL-2.0+ OR MIT)
+
+&pgc_otg1 {
+ barebox,allow-dummy;
+};
--
2.30.2
next prev parent reply other threads:[~2022-07-30 9:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-30 9:52 [PATCH master 1/3] drivers: power: ignore power domains with barebox,allow-dummy Ahmad Fatoum
2022-07-30 9:52 ` [PATCH master 2/3] ARM: i.MX8MM: assume USBOTG power domains to be powered Ahmad Fatoum
2022-07-30 9:52 ` Ahmad Fatoum [this message]
2022-08-05 5:23 ` [PATCH master 1/3] drivers: power: ignore power domains with barebox,allow-dummy Ahmad Fatoum
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=20220730095211.1769119-3-a.fatoum@pengutronix.de \
--to=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=lst@pengutronix.de \
--cc=mfe@pengutronix.de \
/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