public inbox for linux-tegra@vger.kernel.org
 help / color / mirror / Atom feed
From: Lucas Stach <dev-8ppwABl0HbeELgA04lAiVw@public.gmane.org>
To: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
Cc: Prashant Gaikwad
	<pgaikwad-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>,
	linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	Thierry Reding
	<thierry.reding-RM9K5IK7kjKj5M59NBduVrNAH6kLmebB@public.gmane.org>,
	Mark Zhang <nvmarkzhang-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Subject: Re: [PATCH] ARM: tegra: dynamically calculate pll_d parameters
Date: Mon, 17 Dec 2012 23:16:54 +0100	[thread overview]
Message-ID: <1355782614.1490.31.camel@tellur> (raw)
In-Reply-To: <50CF963E.7020506-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>

Am Montag, den 17.12.2012, 15:01 -0700 schrieb Stephen Warren:
> On 12/17/2012 10:58 AM, Lucas Stach wrote:
> > Calculate PLL_D parameters in a dynamically instead of using a fixed
> > table. This allows TegraDRM to drive outputs with CVT compliant modes.
> 
> Prashant, can you please review this, and comment on the best approach
> for dealing with the conflict this has with your clock driver rework.
> Thanks.
> 
> Lucas, I assume this algorithm generates the same cpcon values (and
> indeed M/N/P values) as were in the fixed pll_d_freq_table before?
> 
I know this might not be the nicest thing for validation, but no this
isn't generating exactly the same values. The tables used a fixed 1MHz
Cf, which results in high N values for faster pixel clocks. The new
algorithm tries to use a higher Cf if possible, resulting in smaller N
which provides the opportunity to reduce cpcon, which in turn might be a
win for power consumption.

The cpcon values are set according to the TRM and are indeed the same
when using Cf=1MHz.

To match the old behaviour of the table I would have to further dumb
down the calculation, which might make this more specific to PLL_D and
reduce the possibility to reuse parts of the code for other PLLs later
on. But as apparently there's a rework going on this might not be an
relevant argument.

Regards,
Lucas

  parent reply	other threads:[~2012-12-17 22:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-17 17:58 [PATCH] ARM: tegra: dynamically calculate pll_d parameters Lucas Stach
     [not found] ` <1355767103-5303-1-git-send-email-dev-8ppwABl0HbeELgA04lAiVw@public.gmane.org>
2012-12-17 22:01   ` Stephen Warren
     [not found]     ` <50CF963E.7020506-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2012-12-17 22:16       ` Lucas Stach [this message]
2012-12-18  5:45       ` Prashant Gaikwad
2012-12-18  6:58   ` Thierry Reding
     [not found]     ` <20121218065857.GA5151-RM9K5IK7kjIyiCvfTdI0JKcOhU4Rzj621B7CTYaBSLdn68oJJulU0Q@public.gmane.org>
2012-12-18  8:40       ` Lucas Stach
2012-12-18  8:36   ` Mark Zhang
     [not found]     ` <50D02B0F.4020307-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2012-12-18  9:19       ` Lucas Stach
2012-12-18 16:40         ` Stephen Warren

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=1355782614.1490.31.camel@tellur \
    --to=dev-8ppwabl0hbeelga04laivw@public.gmane.org \
    --cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=nvmarkzhang-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=pgaikwad-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
    --cc=swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org \
    --cc=thierry.reding-RM9K5IK7kjKj5M59NBduVrNAH6kLmebB@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