summaryrefslogtreecommitdiff
path: root/rust/kernel/alloc/allocator
diff options
context:
space:
mode:
authorWayne Chang <waynec@nvidia.com>2026-09-03 15:19:34 +0800
committerVinod Koul <vkoul@kernel.org>2026-10-03 22:42:57 +0200
commitc850a8821901163998ec4b7932b3d79dbe480543 (patch)
tree5dae97053a06db3e6c7108bf873e183a2e5d22d3 /rust/kernel/alloc/allocator
parentc01ccf91b257741e9edc374a465126bae9ae4711 (diff)
dt-bindings: phy: tegra-xusb: Add support for Tegra264
Add the compatible string for the Tegra264 XUSB PHY. A dedicated compatible string is used instead of falling back to nvidia,tegra234-xusb-padctl, because Tegra264 is not programming-compatible with Tegra234, even though they share the same DT property set. The driver selects per-SoC data from the compatible string, and Tegra264 differs from Tegra234 in at least: - Tegra264 uses hardware tracking mode (trk_hw_mode), while Tegra234 disables it. - On Tegra234, CYA_TRK_CODE_UPDATE_ON_IDLE needs to be cleared so that the calibration values can be captured while the controller is still in reset. Tegra264 does not require this, and the corresponding handling is not even present for it. A fallback of nvidia,tegra234-xusb-padctl would let an OS that only knows about Tegra234 probe Tegra264 with the wrong programming sequence. This is also why Tegra234 did not fall back to nvidia,tegra194-xusb-padctl in this same binding: the DT schema is shared, but each generation needs its own compatible. Signed-off-by: Wayne Chang <waynec@nvidia.com> Acked-by: Conor Dooley <conor.dooley@microchip.com> Reviewed-by: Jon Hunter <jonathanh@nvidia.com> Tested-by: Jon Hunter <jonathanh@nvidia.com> Link: https://patch.msgid.link/20260903071937.533646-2-waynec@nvidia.com Signed-off-by: Vinod Koul <vkoul@kernel.org>
Diffstat (limited to 'rust/kernel/alloc/allocator')
0 files changed, 0 insertions, 0 deletions