All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nishanth Menon <nm@ti.com>
To: Lucas Stach <l.stach@pengutronix.de>, linux-pm@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Len Brown <len.brown@intel.com>, Pavel Machek <pavel@ucw.cz>,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>
Subject: Re: [RFC 2/2] PM / OPP: extend DT parsing to allow voltage ranges
Date: Tue, 20 May 2014 09:32:34 -0500	[thread overview]
Message-ID: <537B6782.5080505@ti.com> (raw)
In-Reply-To: <1400596060-5330-3-git-send-email-l.stach@pengutronix.de>

On 05/20/2014 09:27 AM, Lucas Stach wrote:
> Following the introduction of voltage ranges into OPP
> we need a way to encode them in the device tree in a
> similar fashion to the non-ranged versions.
> 
> To keep compatibility with old DTs the parsing function
> is changed to understand both versions.
> 
> Signed-off-by: Lucas Stach <l.stach@pengutronix.de>
> ---
>  Documentation/devicetree/bindings/power/opp.txt | 23 ++++++++++++++++++
>  drivers/base/power/opp.c                        | 31 ++++++++++++++++++-------
>  2 files changed, 46 insertions(+), 8 deletions(-)
> 
> diff --git a/Documentation/devicetree/bindings/power/opp.txt b/Documentation/devicetree/bindings/power/opp.txt
> index 74499e5033fc..5b520ff321f5 100644
> --- a/Documentation/devicetree/bindings/power/opp.txt
> +++ b/Documentation/devicetree/bindings/power/opp.txt
> @@ -10,6 +10,16 @@ Properties:
>  	freq: clock frequency in kHz
>  	vol: voltage in microvolt
>  
> +or
> +
> +- operating-points-range: An array of 4-tuple items, each item consisting
> +  of a frequency and a related voltage range in the following form:
> +  <freq min-vol-uV nom-vol-uV max-vol-uV>
> +	freq: clock frequency in kHz
> +	min-vol-uV: absolute minimum required voltage for this frequency
> +	nom-vol-uV: nominal voltage for this frequency
> +	max-vol-uV: absolute maximum allowed voltage for this frequency

And, Why cant we function at min-volt-uV? because PMIC cannot support
it? then why add voltage tolerance? This is not clear in the dt
description.



> +
>  Examples:
>  
>  cpu@0 {
> @@ -23,3 +33,16 @@ cpu@0 {
>  		198000  850000
>  	>;
>  };
> +
> +cpu@0 {
> +	compatible = "arm,cortex-a8";
> +	reg = <0x0>;
> +	operating-points-range = <
> +		/*  kHz min(uV) nom(uV) max(uV) */
> +		 166666  850000  900000 1400000
> +		 400000  900000  950000 1400000
> +		 800000 1050000 1100000 1400000
> +		1000000 1200000 1250000 1400000
> +		1200000 1300000 1350000 1400000
> +	>;
> +};

[...]

-- 
Regards,
Nishanth Menon

  reply	other threads:[~2014-05-20 14:32 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-20 14:27 [RFC 0/2] extends OPP for voltage ranges Lucas Stach
2014-05-20 14:27 ` [RFC 1/2] PM / OPP: allow to use " Lucas Stach
2014-05-21 13:46   ` Pavel Machek
2014-05-20 14:27 ` [RFC 2/2] PM / OPP: extend DT parsing to allow " Lucas Stach
2014-05-20 14:32   ` Nishanth Menon [this message]
2014-05-20 14:41     ` Lucas Stach
2014-05-20 14:53       ` Nishanth Menon
2014-05-20 15:07         ` Lucas Stach
2014-05-20 15:23           ` Nishanth Menon
2014-05-20 15:29             ` Nishanth Menon
2014-05-20 15:48               ` Lucas Stach
2014-05-20 16:09                 ` Nishanth Menon
2014-05-20 16:45                   ` Lucas Stach
2014-05-20 17:02                     ` Nishanth Menon
2014-05-21  9:47                       ` Lucas Stach
2014-05-21 23:33                         ` Mark Brown
2014-05-22 10:24                           ` Lucas Stach
2014-05-22 17:58                             ` Mark Brown
2014-05-30  0:06                               ` Nishanth Menon
2014-05-21 13:49   ` Pavel Machek

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=537B6782.5080505@ti.com \
    --to=nm@ti.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=l.stach@pengutronix.de \
    --cc=len.brown@intel.com \
    --cc=linux-pm@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --cc=rjw@rjwysocki.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.