From: Rasmus Villemoes <rasmus.villemoes@prevas.dk>
To: Jun Li <jun.li@nxp.com>, Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Shawn Guo <shawnguo@kernel.org>, Arnd Bergmann <arnd@arndb.de>
Subject: Re: commit 3497b9a5 (usb: dwc3: add power down scale setting) breaks imx8mp
Date: Mon, 9 Jan 2023 09:46:54 +0100 [thread overview]
Message-ID: <04f2b720-c588-0431-b80b-2ae407bb6006@prevas.dk> (raw)
In-Reply-To: <PA4PR04MB9640E88C1F4EF722682608D689FB9@PA4PR04MB9640.eurprd04.prod.outlook.com>
On 06/01/2023 14.35, Jun Li wrote:
>
>
>> -----Original Message-----
>> From: Rasmus Villemoes <rasmus.villemoes@prevas.dk>
>> Sent: Friday, January 6, 2023 7:55 PM
>> To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>; Jun Li
>> <jun.li@nxp.com>
>> Li Jun, please either revert 3497b9a5 or figure out if imx8mp.dtsi is broken
>> and needs a fix similar to 74bd5951dd3.
>
> iMX8MP suspend clock(with name IMX8MP_CLK_USB_ROOT) was 32K when 3497b9a5
> was merged, a later iMX8MP clock driver patch change the clock to be root
> clock gate(actually this is a shared clock gate for both suspend and root
> clock), so break the iMX8MP USB as you are seeing, a fix patch set already
> addressed this issue, please check and apply below 3 patches:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/include/dt-bindings/clock/imx8mp-clock.h?id=5c1f7f1090947d494c30042123e0ec846f696336
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/drivers/clk/imx/clk-imx8mp.c?id=ed1f4ccfe947a3e1018a3bd7325134574c7ff9b3
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/arch/arm64/boot/dts/freescale/imx8mp.dtsi?id=8a1ed98fe0f2e7669f0409de0f46f317b275f8be
Thanks, I see that the first two are in 6.2-rc1 and have already been
picked up in 6.0.y and 6.1.y. The last is not yet in mainline and thus
not eligible for -stable, but does seem to be included in Shawn's PR
https://lore.kernel.org/all/20230102132016.GA10699@T480/
so I assume that it will land shortly.
Rasmus
prev parent reply other threads:[~2023-01-09 8:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-06 11:54 commit 3497b9a5 (usb: dwc3: add power down scale setting) breaks imx8mp Rasmus Villemoes
2023-01-06 12:05 ` Linux kernel regression tracking (#adding)
2023-02-16 14:29 ` Linux regression tracking #update (Thorsten Leemhuis)
2023-01-06 13:35 ` Jun Li
2023-01-09 8:46 ` Rasmus Villemoes [this message]
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=04f2b720-c588-0431-b80b-2ae407bb6006@prevas.dk \
--to=rasmus.villemoes@prevas.dk \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=jun.li@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=shawnguo@kernel.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).