summaryrefslogtreecommitdiff
path: root/drivers/infiniband/hw/mlx5/qp.h
diff options
context:
space:
mode:
authorBH Hsieh <bhsieh@nvidia.com>2025-01-22 18:59:43 +0800
committerVinod Koul <vkoul@kernel.org>2025-02-14 18:03:05 +0530
commit55f1a5f7c97c3c92ba469e16991a09274410ceb7 (patch)
treea542317cdc4e1c4a693c44999885bf358a2334e0 /drivers/infiniband/hw/mlx5/qp.h
parent5ab90f40121a9f6a9b368274cd92d0f435dc7cfa (diff)
phy: tegra: xusb: reset VBUS & ID OVERRIDE
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. [ 173.765814] usb usb3-port2: Cannot enable. Maybe the USB cable is bad? [ 173.765837] usb usb3-port2: config error Taking virtualization into account, asserting XUSB PADCTL reset would break XUSB functions used by other guest OS, hence only reset VBUS & ID OVERRIDE of the port in utmi_phy_init. Fixes: bbf711682cd5 ("phy: tegra: xusb: Add Tegra186 support") Cc: stable@vger.kernel.org Change-Id: Ic63058d4d49b4a1f8f9ab313196e20ad131cc591 Signed-off-by: BH Hsieh <bhsieh@nvidia.com> Signed-off-by: Henry Lin <henryl@nvidia.com> Link: https://lore.kernel.org/r/20250122105943.8057-1-henryl@nvidia.com Signed-off-by: Vinod Koul <vkoul@kernel.org>
Diffstat (limited to 'drivers/infiniband/hw/mlx5/qp.h')
0 files changed, 0 insertions, 0 deletions