linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: shc_work@mail.ru (Alexander Shiyan)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC v2] ARM: i.MX pllv1: Implement set_rate
Date: Sat, 20 Jul 2013 16:18:01 +0400	[thread overview]
Message-ID: <20130720161801.380bb0d9db75155f5401730b@mail.ru> (raw)
In-Reply-To: <20130720115829.GD29785@pengutronix.de>

On Sat, 20 Jul 2013 13:58:29 +0200
Sascha Hauer <s.hauer@pengutronix.de> wrote:

> > > On Sat, Jul 20, 2013 at 12:29:35PM +0400, Alexander Shiyan wrote:
> > > > This patch implements frequency change for i.MX pllv1.
> > > > Selection of the values of the registers is not optimal, since is
> > > > made by simple enumeration of all possible values.
> > > 
> > > You do not mention why you want to adjust the rate. Normally we've been
> > > happy with the static values from the bootloader.
> > 
> > For CPUfreq.
> > Only one barrier to make it workable.
> 
> Isn't it better to adjust the dividers only? I haven't made good
> experience with adjusting the PLLs.

The frequency value after booting can be quite arbitrary.

Since we define possible frequencies for the CPU (266 and 399 MHz),
I can offer as variant to use a fixed constant values for PLL.

-- 
Alexander Shiyan <shc_work@mail.ru>

  reply	other threads:[~2013-07-20 12:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-20  8:29 [RFC v2] ARM: i.MX pllv1: Implement set_rate Alexander Shiyan
2013-07-20 11:16 ` Sascha Hauer
2013-07-20 11:31   ` Alexander Shiyan
2013-07-20 11:58     ` Sascha Hauer
2013-07-20 12:18       ` Alexander Shiyan [this message]
2013-07-21 12:37         ` Sascha Hauer
2013-07-22 15:18           ` Alexander Shiyan
2013-07-22 15:24             ` Lucas Stach
2013-07-22 15:40               ` Alexander Shiyan

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=20130720161801.380bb0d9db75155f5401730b@mail.ru \
    --to=shc_work@mail.ru \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).