[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <172522185704.996619.16331297087532612354.b4-ty@ti.com>
Date: Sun, 1 Sep 2024 15:20:42 -0500
From: Nishanth Menon <nm@...com>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Rob Herring
<robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley
<conor+dt@...nel.org>, Roger Quadros <rogerq@...nel.org>,
Peter Chen
<peter.chen@...nel.org>,
Pawel Laszczak <pawell@...ence.com>,
Mathias Nyman
<mathias.nyman@...el.com>,
Vignesh Raghavendra <vigneshr@...com>,
Tero Kristo
<kristo@...nel.org>,
Théo Lebrun <theo.lebrun@...tlin.com>
CC: Nishanth Menon <nm@...com>, <linux-usb@...r.kernel.org>,
<devicetree@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
<linux-arm-kernel@...ts.infradead.org>,
Kevin Hilman <khilman@...nel.org>,
Grégory Clement <gregory.clement@...tlin.com>,
Thomas
Petazzoni <thomas.petazzoni@...tlin.com>,
Conor Dooley
<conor.dooley@...rochip.com>
Subject: Re: (subset) [PATCH v5 00/12] Fix USB suspend on TI J7200 (cdns3-ti, cdns3, xhci)
Hi Théo Lebrun,
On Fri, 26 Jul 2024 20:17:48 +0200, Théo Lebrun wrote:
> Currently, system-wide suspend is broken on J7200 because of a
> controller reset. The TI wrapper does not get re-initialised at resume
> and the first register access from cdns core fails.
>
> We address that in a few ways:
> - In cdns3-ti, if a reset has occured at resume, we reconfigure the HW.
> - We pass the XHCI_RESET_ON_RESUME quirk, meaning the XHCI core expects
> a resume.
> - We add a xhci->lost_power flag.
>
> [...]
Since Greg has picked f7fd939e805672417bbf418f6035dec9400230fd ("dt-bindings:
usb: ti,j721e-usb: fix compatible list"), the corresponding
patch needs to go via the soc dt tree, so picking just that.
I have applied the following to branch ti-k3-dts-next on [1].
Thank you!
[12/12] arm64: dts: ti: k3-am64: add USB fallback compatible to J721E
commit: 99ced42d6f3ebcae52c2c6d1207d3f96d7cf88ac
Theo: Do let me know if Greg decides to drop the said patch, and I will drop
this off my PR as well. But, no action at the moment for this.
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent up the chain during
the next merge window (or sooner if it is a relevant bug fix), however if
problems are discovered then the patch may be dropped or reverted.
You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.
If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.
Please add any relevant lists and maintainers to the CCs when replying
to this mail.
[1] https://git.kernel.org/pub/scm/linux/kernel/git/ti/linux.git
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
Powered by blists - more mailing lists