From: l.stach@pengutronix.de (Lucas Stach)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/4] cpufreq: add i.MX5 cpufreq driver
Date: Mon, 26 May 2014 17:28:35 +0200 [thread overview]
Message-ID: <1401118115.4829.60.camel@weser.hi.pengutronix.de> (raw)
In-Reply-To: <CAKohponvWLVfBL06HURnTq4nmdKjROV-bd4pVcbNmsAUYYC+nA@mail.gmail.com>
Am Montag, den 26.05.2014, 20:52 +0530 schrieb Viresh Kumar:
> On 26 May 2014 19:28, Lucas Stach <l.stach@pengutronix.de> wrote:
> > Right, the OPP in my example define the minimum required voltage for
> > each frequency. This is in accordance to the OPP binding. But for this
> > chip the datasheet explicitly says that it is ok to power the cpu rail
> > with up to 1.4V, regardless of the current operating frequency. So this
> > 1.4V is really the upper bound I would like to pass to the regulator
> > framework. This ensures that the driver still works properly even if the
> > external regulator can't scale down to the minimum (or in other words
> > optimal) voltage.
>
> One more query. You have mentioned earlier and I just wanted to confirm
> this. In your platform/board regulator only supports one voltage, i.e. 1.4 uV,
> and it we can't get lower values out of regulator ?
>
> If that's the case, why are you looking to use regulator at all?
The platform I'm working on supports cpu rail voltage regulation just
fine.
I just want to make sure that the driver works properly on platforms
where this isn't the case. As the datasheet explicitly allows this case
I want to make sure to not introduce a software only restriction, where
there isn't any in hardware.
Regards,
Lucas
--
Pengutronix e.K. | Lucas Stach |
Industrial Linux Solutions | http://www.pengutronix.de/ |
next prev parent reply other threads:[~2014-05-26 15:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-26 10:15 [PATCH 1/4] clk: imx5: add step and cpu_podf mux Lucas Stach
2014-05-26 10:15 ` [PATCH 2/4] cpufreq: add i.MX5 cpufreq driver Lucas Stach
2014-05-26 10:32 ` Viresh Kumar
2014-05-26 10:45 ` Lucas Stach
2014-05-26 11:06 ` Viresh Kumar
2014-05-26 12:35 ` Lucas Stach
2014-05-26 12:56 ` Viresh Kumar
2014-05-26 13:11 ` Lucas Stach
2014-05-26 13:44 ` Viresh Kumar
2014-05-26 13:58 ` Lucas Stach
2014-05-26 15:22 ` Viresh Kumar
2014-05-26 15:28 ` Lucas Stach [this message]
2014-05-26 15:35 ` Viresh Kumar
2014-05-26 15:57 ` Lucas Stach
2014-05-26 16:22 ` Viresh Kumar
2014-05-26 10:15 ` [PATCH 3/4] ARM: imx53: instanciate cpufreq device Lucas Stach
2014-05-26 10:15 ` [PATCH 4/4] ARM: imx53: add basic cpufreq properties to dtsi Lucas Stach
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=1401118115.4829.60.camel@weser.hi.pengutronix.de \
--to=l.stach@pengutronix.de \
--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).