From: Thierry Reding <thierry.reding@avionic-design.de>
To: Dmitry Artamonow <mad_soft@inbox.ru>
Cc: linux-tegra@vger.kernel.org, Colin Cross <ccross@android.com>,
Olof Johansson <olof@lixom.net>,
Stephen Warren <swarren@nvidia.com>,
Mike Rapoport <mike@compulab.co.il>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH/RFC 2/2] arm/tegra: add timeout to PCIe PLL lock detection loop
Date: Wed, 7 Mar 2012 07:38:29 +0100 [thread overview]
Message-ID: <20120307063829.GA16359@avionic-0098.mockup.avionic-design.de> (raw)
In-Reply-To: <1331023544-6439-3-git-send-email-mad_soft@inbox.ru>
[-- Attachment #1: Type: text/plain, Size: 354 bytes --]
* Dmitry Artamonow wrote:
[...]
> diff --git a/arch/arm/mach-tegra/pcie.c b/arch/arm/mach-tegra/pcie.c
[...]
> @@ -639,8 +639,14 @@ static void tegra_pcie_enable_controller(void)
> pads_writel(0xfa5cfa5c, 0xc8);
>
> /* Wait for the PLL to lock */
> + timeout = 2000;
FWIW, the Vibrante kernel uses 300 for the timeout value.
Thierry
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2012-03-07 6:38 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-06 8:45 [PATCH/RFC 0/2] Couple of Tegra2 PCIe fixes(?) Dmitry Artamonow
2012-03-06 8:45 ` [PATCH/RFC 1/2] arm/tegra: fix harmony pinmux for PCIe Dmitry Artamonow
2012-03-06 16:55 ` Stephen Warren
2012-03-06 8:45 ` [PATCH/RFC 2/2] arm/tegra: add timeout to PCIe PLL lock detection loop Dmitry Artamonow
2012-03-06 9:38 ` Andi
2012-03-06 11:19 ` Dmitry Artamonow
2012-03-06 16:58 ` Stephen Warren
2012-03-06 19:09 ` Thierry Reding
2012-03-06 20:15 ` Dmitry Artamonow
2012-03-09 10:09 ` [PATCH v2 " Dmitry Artamonow
2012-03-12 18:09 ` Stephen Warren
2012-03-12 19:30 ` Dmitry Artamonow
2012-03-12 19:56 ` Olof Johansson
2012-03-13 5:46 ` [PATCH] arm/tegra: pcie: fix return value of function Dmitry Artamonow
2012-03-13 19:36 ` Stephen Warren
2012-03-18 17:27 ` Olof Johansson
2012-03-07 6:38 ` Thierry Reding [this message]
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=20120307063829.GA16359@avionic-0098.mockup.avionic-design.de \
--to=thierry.reding@avionic-design.de \
--cc=ccross@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mad_soft@inbox.ru \
--cc=mike@compulab.co.il \
--cc=olof@lixom.net \
--cc=swarren@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
Powered by JetHome