From: Thierry Reding <thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
Cc: Peter De Schrijver
<pdeschrijver-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>,
Prashant Gaikwad
<pgaikwad-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>,
linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] HACK: clk: tegra: Do not mark PLLE as fixed
Date: Wed, 30 Oct 2013 21:44:33 +0100 [thread overview]
Message-ID: <20131030204432.GA7686@mithrandir> (raw)
In-Reply-To: <52700F86.2080103-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 755 bytes --]
On Tue, Oct 29, 2013 at 01:41:58PM -0600, Stephen Warren wrote:
> On 10/29/2013 08:40 AM, Thierry Reding wrote:
> > Signed-off-by: Thierry Reding <treding-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
>
> What does this patch solve? A description would be nice.
>
> I thought that this PLL essentially was fixed; while it may have some
> registers than /can/ change the rate, hasn't the HW team only
> characterized it to run at the single frequency that PCIe requires,
> hence SW is supposed to treat it as fixed?
Peter fixed it up properly. As indicated by the HACK: tag, this was
really only a workaround to make Dalmore boot again. PLLE didn't use to
be marked as fixed, which seems to be the reason why we've never seen
this.
Thierry
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2013-10-30 20:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-29 14:40 [PATCH] HACK: clk: tegra: Do not mark PLLE as fixed Thierry Reding
[not found] ` <1383057631-32668-1-git-send-email-treding-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2013-10-29 19:41 ` Stephen Warren
[not found] ` <52700F86.2080103-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-10-30 20:44 ` 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=20131030204432.GA7686@mithrandir \
--to=thierry.reding-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=pdeschrijver-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
--cc=pgaikwad-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
--cc=swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org \
/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