linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jon Hunter <jonathanh@nvidia.com>
To: Rhyland Klein <rklein@nvidia.com>,
	Thierry Reding <thierry.reding@gmail.com>
Cc: Peter De Schrijver <pdeschrijver@nvidia.com>,
	Mike Turquette <mturquette@baylibre.com>,
	Stephen Warren <swarren@wwwdotorg.org>,
	"Stephen Boyd" <sboyd@codeaurora.org>,
	Alexandre Courbot <gnurou@gmail.com>,
	"linux-clk@vger.kernel.org" <linux-clk@vger.kernel.org>,
	"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Andrew Bresticker" <abrestic@chromium.org>
Subject: Re: [PATCH v5] clk: tegra: Initialize UTMIPLL when enabling PLLU
Date: Tue, 28 Jun 2016 17:30:16 +0100	[thread overview]
Message-ID: <5772A618.4020207@nvidia.com> (raw)
In-Reply-To: <dc524c6236144234a341fedaa22dbacb@HQMAIL112.nvidia.com>

Hi Rhyland,

On 27/06/16 19:11, Rhyland Klein wrote:
> Jonathan, can you confirm replacing usleep_range(100, 200) with udelay(2) works for you?

Yes for me, using a udelay(2) does seem to work. I have made sure that a
usb device is still detected on the Jetson TX1. However, I am not sure
the best way to test this thoroughly.

If we do make this change it would be good to propagate downstream as
well to get wider testing.

Cheers
Jon

-- 
nvpublic

  reply	other threads:[~2016-06-28 16:32 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-26 16:41 [PATCH v5] clk: tegra: Initialize UTMIPLL when enabling PLLU Rhyland Klein
2016-06-14 11:33 ` Thierry Reding
2016-06-17 13:49 ` Jon Hunter
2016-06-17 15:23   ` Thierry Reding
2016-06-20 17:24     ` Rhyland Klein
2016-06-27 18:11     ` Rhyland Klein
2016-06-28 16:30       ` Jon Hunter [this message]
2016-06-30 15:32     ` Rhyland Klein
2016-06-30 15:37       ` Thierry Reding
2016-06-30 15:40         ` Rhyland Klein
2016-06-30 15:43           ` Thierry Reding

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=5772A618.4020207@nvidia.com \
    --to=jonathanh@nvidia.com \
    --cc=abrestic@chromium.org \
    --cc=gnurou@gmail.com \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=pdeschrijver@nvidia.com \
    --cc=rklein@nvidia.com \
    --cc=sboyd@codeaurora.org \
    --cc=swarren@wwwdotorg.org \
    --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).