[PATCH 1/8] dt-bindings: phy: tegra-xusb: Add support for Tegra264

[Wayne Chang]

Hi Conor,

Thanks for the review and sorry for the late reply.

A fallback is not suitable here because Tegra264 XUSB padctl is not
programming-compatible with Tegra234 (or Tegra194), even though the
DT property set is the same.

The driver selects per-SoC data from the compatible string. 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. This is 
not required on
Tegra264, where the corresponding handling is not even present.

A fallback of "nvidia,tegra234-xusb-padctl" would let an OS that only
knows Tegra234 probe Tegra264 with the wrong programming sequence.

That is also why Tegra234 did not fall back to Tegra194 in this same
binding: the DT schema is shared, but each generation needs its own
compatible.

Thanks,
Wayne


On 6/29/26 23:19, Conor Dooley wrote:
> On Mon, Jun 29, 2026 at 05:33:59PM +0800, Wayne Chang wrote:
>> Add the compatible string for the Tegra264 XUSB PHY.
>>
>> Signed-off-by: Wayne Chang<waynec at nvidia.com>
> Why is a fallback compatible not suitable here?
>
>
> Thanks,
> Conor.
>
>> ---
>>   .../devicetree/bindings/phy/nvidia,tegra194-xusb-padctl.yaml     | 1 +
>>   1 file changed, 1 insertion(+)
>>
>> diff --git a/Documentation/devicetree/bindings/phy/nvidia,tegra194-xusb-padctl.yaml b/Documentation/devicetree/bindings/phy/nvidia,tegra194-xusb-padctl.yaml
>> index d8de900a4fce..f6fe3c90b5b0 100644
>> --- a/Documentation/devicetree/bindings/phy/nvidia,tegra194-xusb-padctl.yaml
>> +++ b/Documentation/devicetree/bindings/phy/nvidia,tegra194-xusb-padctl.yaml
>> @@ -45,6 +45,7 @@ properties:
>>       enum:
>>         - nvidia,tegra194-xusb-padctl
>>         - nvidia,tegra234-xusb-padctl
>> +      - nvidia,tegra264-xusb-padctl
>>   
>>     reg:
>>       items:
>> -- 
>> 2.25.1
>>