linux-kernel - Re: [PATCH] phy: tegra: xusb: Default otg mode to peripheral

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <53c531a4-5d75-4595-98d3-b3abf1b1243d@nvidia.com>
Date: Tue, 6 May 2025 12:04:13 +0100
From: Jon Hunter <jonathanh@...dia.com>
To: Aaron Kling <webgeek1234@...il.com>
Cc: JC Kuo <jckuo@...dia.com>, Vinod Koul <vkoul@...nel.org>,
 Kishon Vijay Abraham I <kishon@...nel.org>,
 Thierry Reding <thierry.reding@...il.com>, linux-phy@...ts.infradead.org,
 linux-tegra@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] phy: tegra: xusb: Default otg mode to peripheral


On 06/05/2025 11:44, Aaron Kling wrote:

...

>> Rather than reference 'synopsys dwc3' which is not related to the Tegra,
>> it would be better to update the binding doc for Tegra XUSB padctl device
>> to list this property and define the default mode.
> 
> Let me make sure I understand you correctly. You're requesting to
> update the binding as above, listing peripheral as default when unset;
> fix my commit message; and leave my code change as-is? I'm unclear on
> if the code is okay as-is or not.

If the dt-binding doc states that the default is peripheral mode when 
the property is not present, then yes your patch should be OK as-is.

Jon

-- 
nvpublic