mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: barebox@lists.infradead.org
Cc: Hans Christian Lonstad <hcl@datarespons.com>,
	Ahmad Fatoum <a.fatoum@pengutronix.de>
Subject: [PATCH master] ARM: dts: i.MX8MP: snps,dis-u2-freeclk-exists-quirk
Date: Thu, 30 Mar 2023 13:38:44 +0200	[thread overview]
Message-ID: <20230330113844.3343865-1-a.fatoum@pengutronix.de> (raw)

Linux v6.1 adds a snps,gfladj-refclk-lpm-sel-quirk property to the
i.MX8MP DWC3 device tree nodes, which is a superset of the existing
snps,dis-u2-freeclk-exists-quirk property. For this reason, the old
property was dropped breaking some usages of barebox i.MX8MP DWC3.

The proper fix would be supporting this new property, which is already
in next as part of the DWC3 driver sync with the kernel.

Until that lands in master though, let's add back the removed property
to fix the regression. Expectation is that we can revert this commit
as part of v2023.05.0.

Link: https://github.com/saschahauer/barebox/issues/19
Reported-by: Hans Christian Lonstad <hcl@datarespons.com>
Fixes: 32e2176ba050 ("dts: update to v6.1-rc1")
Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
---
 arch/arm/dts/imx8mp.dtsi | 9 +++++++++
 1 file changed, 9 insertions(+)

diff --git a/arch/arm/dts/imx8mp.dtsi b/arch/arm/dts/imx8mp.dtsi
index 6962d11e853a..3bec8432627f 100644
--- a/arch/arm/dts/imx8mp.dtsi
+++ b/arch/arm/dts/imx8mp.dtsi
@@ -10,6 +10,15 @@
 	};
 };
 
+/* Temporary workaround until snps,gfladj-refclk-lpm-sel-quirk is supported */
+&usb_dwc3_0 {
+	snps,dis-u2-freeclk-exists-quirk;
+};
+
+&usb_dwc3_1 {
+	snps,dis-u2-freeclk-exists-quirk;
+};
+
 /*
  * The DSP reserved memory will collide with the Barebox malloc area for some
  * DRAM sizes, even though the DSP itself is disabled in most configurations.
-- 
2.39.2




             reply	other threads:[~2023-03-30 11:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-30 11:38 Ahmad Fatoum [this message]
2023-03-31  5:48 ` 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=20230330113844.3343865-1-a.fatoum@pengutronix.de \
    --to=a.fatoum@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=hcl@datarespons.com \
    /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