From: Jon Hunter <jonathanh@nvidia.com>
To: Aaron Kling <webgeek1234@gmail.com>
Cc: JC Kuo <jckuo@nvidia.com>, Vinod Koul <vkoul@kernel.org>,
Kishon Vijay Abraham I <kishon@kernel.org>,
Thierry Reding <thierry.reding@gmail.com>,
linux-phy@lists.infradead.org, linux-tegra@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] phy: tegra: xusb: Default otg mode to peripheral
Date: Tue, 6 May 2025 12:04:13 +0100 [thread overview]
Message-ID: <53c531a4-5d75-4595-98d3-b3abf1b1243d@nvidia.com> (raw)
In-Reply-To: <CALHNRZ9tgWTo8tUB1+Whf68CYu+qiMhO_S+KC2R0kFbDAjT9OQ@mail.gmail.com>
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
next prev parent reply other threads:[~2025-05-06 11:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-04 8:17 [PATCH] phy: tegra: xusb: Default otg mode to peripheral Aaron Kling via B4 Relay
2025-04-14 4:45 ` Aaron Kling
2025-04-21 1:44 ` Aaron Kling
2025-05-05 7:44 ` Aaron Kling
2025-05-06 9:51 ` Jon Hunter
2025-05-06 10:03 ` Aaron Kling
2025-05-06 10:30 ` Jon Hunter
2025-05-06 10:44 ` Aaron Kling
2025-05-06 11:04 ` Jon Hunter [this message]
2025-05-06 11:09 ` Jon Hunter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53c531a4-5d75-4595-98d3-b3abf1b1243d@nvidia.com \
--to=jonathanh@nvidia.com \
--cc=jckuo@nvidia.com \
--cc=kishon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=linux-tegra@vger.kernel.org \
--cc=thierry.reding@gmail.com \
--cc=vkoul@kernel.org \
--cc=webgeek1234@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox