From: Jon Hunter <jonathanh@nvidia.com>
To: Wayne Chang <waynec@nvidia.com>,
jckuo@nvidia.com, vkoul@kernel.org, kishon@kernel.org,
thierry.reding@gmail.com
Cc: linux-phy@lists.infradead.org, linux-tegra@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH V2 0/2] Disable periodic tracking on Tegra234
Date: Tue, 10 Jun 2025 14:46:39 +0100 [thread overview]
Message-ID: <bc15a890-e2ad-466f-8880-2b3a16a1bd5c@nvidia.com> (raw)
In-Reply-To: <9d00d20f-f766-4b44-a162-35a70ebc6041@nvidia.com>
Hi Vinod,
On 20/05/2025 13:06, Jon Hunter wrote:
>
> On 19/05/2025 10:09, Wayne Chang wrote:
>> Decouple CYA_TRK_CODE_UPDATE_ON_IDLE from trk_hw_mode and disable
>> periodic tracking on Tegra234
>>
>> Haotien Hsu (1):
>> phy: tegra: xusb: Disable periodic tracking on Tegra234
>>
>> Wayne Chang (1):
>> phy: tegra: xusb: Decouple CYA_TRK_CODE_UPDATE_ON_IDLE from
>> trk_hw_mode
>>
>> drivers/phy/tegra/xusb-tegra186.c | 16 +++++++++-------
>> drivers/phy/tegra/xusb.h | 1 +
>> 2 files changed, 10 insertions(+), 7 deletions(-)
>
>
> For the series ...
>
> Reviewed-by: Jon Hunter <jonathanh@nvidia.com>
> Tested-by: Jon Hunter <jonathanh@nvidia.com>
Can we get this into -next now?
Thanks!
Jon
--
nvpublic
next prev parent reply other threads:[~2025-06-10 13:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-19 9:09 Wayne Chang
2025-05-19 9:09 ` [PATCH V2 1/2] phy: tegra: xusb: Decouple CYA_TRK_CODE_UPDATE_ON_IDLE from trk_hw_mode Wayne Chang
2025-05-19 9:09 ` [PATCH V2 2/2] phy: tegra: xusb: Disable periodic tracking on Tegra234 Wayne Chang
2025-05-20 12:06 ` [PATCH V2 0/2] " Jon Hunter
2025-06-10 13:46 ` Jon Hunter [this message]
2025-06-15 16:52 ` Vinod Koul
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=bc15a890-e2ad-466f-8880-2b3a16a1bd5c@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=waynec@nvidia.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
all inboxes | Powered by JetHome®