From: Jon Hunter <jonathanh@nvidia.com>
To: Thierry Reding <thierry.reding@gmail.com>,
Nagarjuna Kristam <nkristam@nvidia.com>,
<gregkh@linuxfoundation.org>
Cc: <linux-usb@vger.kernel.org>, Jui Chang Kuo <jckuo@nvidia.com>,
linux-tegra <linux-tegra@vger.kernel.org>
Subject: Re: [PATCH] usb: host: xhci-tegra: Correct phy enable sequence
Date: Mon, 18 Nov 2019 09:49:52 +0000 [thread overview]
Message-ID: <e36b8dad-768b-bc2e-6aba-1ee96fd9deeb@nvidia.com> (raw)
In-Reply-To: <20191107153231.GC2580600@ulmo>
Hi Greg,
On 07/11/2019 15:32, Thierry Reding wrote:
> On Mon, Nov 04, 2019 at 02:54:30PM +0530, Nagarjuna Kristam wrote:
>> XUSB phy needs to be enabled before un-powergating the power partitions.
>> However in the current sequence, it happens opposite. Correct the phy
>> enable and powergating partition sequence to avoid any boot hangs.
>>
>> Signed-off-by: Nagarjuna Kristam <nkristam@nvidia.com>
>> Signed-off-by: Jui Chang Kuo <jckuo@nvidia.com>
>> ---
>> drivers/usb/host/xhci-tegra.c | 25 +++++++++++++------------
>> 1 file changed, 13 insertions(+), 12 deletions(-)
>
> Acked-by: Thierry Reding <treding@nvidia.com>
Let me know if you can pick this one up? This is fixing a boot
regression on Tegra210.
Tested-by: Jon Hunter <jonathanh@nvidia.com>
Cheers
Jon
--
nvpublic
next prev parent reply other threads:[~2019-11-18 9:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-04 9:24 [PATCH] usb: host: xhci-tegra: Correct phy enable sequence Nagarjuna Kristam
2019-11-04 9:52 ` Thierry Reding
2019-11-05 8:42 ` Nagarjuna Kristam
2019-11-07 15:32 ` Thierry Reding
2019-11-18 9:49 ` Jon Hunter [this message]
2019-11-18 11:30 ` Greg KH
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=e36b8dad-768b-bc2e-6aba-1ee96fd9deeb@nvidia.com \
--to=jonathanh@nvidia.com \
--cc=gregkh@linuxfoundation.org \
--cc=jckuo@nvidia.com \
--cc=linux-tegra@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=nkristam@nvidia.com \
--cc=thierry.reding@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;
as well as URLs for NNTP newsgroup(s).