[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <173953794334.323038.6276165864210863274.b4-ty@kernel.org>
Date: Fri, 14 Feb 2025 18:29:03 +0530
From: Vinod Koul <vkoul@...nel.org>
To: JC Kuo <jckuo@...dia.com>, Kishon Vijay Abraham I <kishon@...nel.org>,
Thierry Reding <thierry.reding@...il.com>,
Jonathan Hunter <jonathanh@...dia.com>, Henry Lin <henryl@...dia.com>
Cc: linux-phy@...ts.infradead.org, linux-tegra@...r.kernel.org,
linux-kernel@...r.kernel.org, BH Hsieh <bhsieh@...dia.com>,
stable@...r.kernel.org
Subject: Re: [PATCH v2] phy: tegra: xusb: reset VBUS & ID OVERRIDE
On Wed, 22 Jan 2025 18:59:43 +0800, Henry Lin wrote:
> Observed VBUS_OVERRIDE & ID_OVERRIDE might be programmed
> with unexpected value prior to XUSB PADCTL driver, this
> could also occur in virtualization scenario.
>
> For example, UEFI firmware programs ID_OVERRIDE=GROUNDED to set
> a type-c port to host mode and keeps the value to kernel.
> If the type-c port is connected a usb host, below errors can be
> observed right after usb host mode driver gets probed. The errors
> would keep until usb role class driver detects the type-c port
> as device mode and notifies usb device mode driver to set both
> ID_OVERRIDE and VBUS_OVERRIDE to correct value by XUSB PADCTL
> driver.
>
> [...]
Applied, thanks!
[1/1] phy: tegra: xusb: reset VBUS & ID OVERRIDE
commit: 55f1a5f7c97c3c92ba469e16991a09274410ceb7
Best regards,
--
~Vinod
Powered by blists - more mailing lists