aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/include/linux/reset/ssh:/git@git.zx2c4.com
diff options
context:
space:
mode:
authorWayne Chang <waynec@nvidia.com>2026-05-04 11:33:05 +0800
committerVinod Koul <vkoul@kernel.org>2026-05-10 17:01:18 +0530
commitda110228b54f2e2143d97ea7151e0dc22e539d67 (patch)
tree453c86b5f8b71361d0a1e5ad5a25393e966a0f44 /include/linux/reset/ssh:/git@git.zx2c4.com
parentphy: marvell: mvebu-a3700-utmi: fix incorrect USB2_PHY_CTRL register access (diff)
phy: tegra: xusb: Fix per-pad high-speed termination calibration
The existing code reads a single hs_term_range_adj value from bit field [10:7] of FUSE_SKU_CALIB_0 and applies it to all USB2 pads uniformly. However, on SoCs that support per-pad termination, each pad has its own hs_term_range_adj field: pad 0 in FUSE_SKU_CALIB_0[10:7], and pads 1-3 in FUSE_USB_CALIB_EXT_0 at bit offsets [8:5], [12:9], and [16:13] respectively. Fix the calibration by reading per-pad values from the appropriate fuse registers. For SoCs that do not support per-pad termination, replicate pad 0's value to all pads to maintain existing behavior. Add a has_per_pad_term flag to the SoC data to indicate whether per-pad termination values are available in FUSE_USB_CALIB_EXT_0. Fixes: 1ef535c6ba8e ("phy: tegra: xusb: Add Tegra194 support") Cc: stable@vger.kernel.org Signed-off-by: Wayne Chang <waynec@nvidia.com> Signed-off-by: Wei-Cheng Chen <weichengc@nvidia.com> Reviewed-by: Jon Hunter <jonathanh@nvidia.com> Tested-by: Jon Hunter <jonathanh@nvidia.com> Link: https://patch.msgid.link/20260504033305.2283145-1-weichengc@nvidia.com Signed-off-by: Vinod Koul <vkoul@kernel.org>
Diffstat (limited to 'include/linux/reset/ssh:/git@git.zx2c4.com')
0 files changed, 0 insertions, 0 deletions