From: Shawn Guo <shawn.guo@linaro.org>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: Device tree binding for DVFS table
Date: Wed, 18 Jul 2012 17:08:41 +0000 [thread overview]
Message-ID: <20120718170838.GA27581@S2101-09.ap.freescale.net> (raw)
In-Reply-To: <4FFD77FE.8050206@nvidia.com>
On Wed, Jul 11, 2012 at 06:26:30PM +0530, Prashant Gaikwad wrote:
> Hi,
>
> I am working on DT binding for Tegra DVFS.
>
> For Tegra, DVFS node mainly consists of frequency and voltage pairs.
> Frequency in the pair may change for different process. E.g. for
> process 1 CPU clock frequency could be 900MHz at 1V while for
> process 2 it could be 1GHz at 1V.
> Tegra uses vendor specific ids to identify the correct frequency table.
>
> Following is the proposed binding for voltage and frequency tables
> used in DVFS. Looking for comments/suggestions to make it generic.
>
It seems we are trying to approach a generic binding for DVFS operating
points. In that case, we will need a generic library helper function
to parse it. But since we already have such a library - OPP
(drivers/base/power/opp.c) in place, I would approach the same goal
in other way around, adding device tree binding for OPP. Please see
the patch I just sent out below and comment.
[PATCH] PM / OPP: Initialize OPP table from device tree
--
Regards,
Shawn
WARNING: multiple messages have this Message-ID (diff)
From: shawn.guo@linaro.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: Device tree binding for DVFS table
Date: Thu, 19 Jul 2012 01:08:41 +0800 [thread overview]
Message-ID: <20120718170838.GA27581@S2101-09.ap.freescale.net> (raw)
In-Reply-To: <4FFD77FE.8050206@nvidia.com>
On Wed, Jul 11, 2012 at 06:26:30PM +0530, Prashant Gaikwad wrote:
> Hi,
>
> I am working on DT binding for Tegra DVFS.
>
> For Tegra, DVFS node mainly consists of frequency and voltage pairs.
> Frequency in the pair may change for different process. E.g. for
> process 1 CPU clock frequency could be 900MHz at 1V while for
> process 2 it could be 1GHz at 1V.
> Tegra uses vendor specific ids to identify the correct frequency table.
>
> Following is the proposed binding for voltage and frequency tables
> used in DVFS. Looking for comments/suggestions to make it generic.
>
It seems we are trying to approach a generic binding for DVFS operating
points. In that case, we will need a generic library helper function
to parse it. But since we already have such a library - OPP
(drivers/base/power/opp.c) in place, I would approach the same goal
in other way around, adding device tree binding for OPP. Please see
the patch I just sent out below and comment.
[PATCH] PM / OPP: Initialize OPP table from device tree
--
Regards,
Shawn
next prev parent reply other threads:[~2012-07-18 17:08 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-11 12:56 Device tree binding for DVFS table Prashant Gaikwad
2012-07-11 13:08 ` Prashant Gaikwad
2012-07-11 14:03 ` Rob Herring
2012-07-11 14:03 ` Rob Herring
2012-07-11 14:44 ` Mark Brown
2012-07-11 14:44 ` Mark Brown
2012-07-11 20:04 ` Mike Turquette
2012-07-11 20:04 ` Mike Turquette
2012-07-12 4:14 ` Prashant Gaikwad
2012-07-12 4:26 ` Prashant Gaikwad
2012-07-12 14:10 ` Peter De Schrijver
2012-07-12 14:10 ` Peter De Schrijver
2012-07-12 17:10 ` Mike Turquette
2012-07-12 17:10 ` Mike Turquette
2012-07-12 17:15 ` Mark Brown
2012-07-12 17:15 ` Mark Brown
2012-07-13 10:34 ` Peter De Schrijver
2012-07-13 10:34 ` Peter De Schrijver
2012-07-13 17:25 ` Mike Turquette
2012-07-13 17:25 ` Mike Turquette
2012-07-12 4:17 ` Prashant Gaikwad
2012-07-12 4:29 ` Prashant Gaikwad
2012-07-12 15:23 ` Mark Brown
2012-07-12 15:23 ` Mark Brown
2012-07-12 17:01 ` Mike Turquette
2012-07-12 17:01 ` Mike Turquette
2012-07-12 8:19 ` Peter De Schrijver
2012-07-12 8:19 ` Peter De Schrijver
2012-07-12 4:08 ` Prashant Gaikwad
2012-07-12 4:20 ` Prashant Gaikwad
2012-07-13 18:30 ` Prashant Gaikwad
2012-07-13 18:42 ` Prashant Gaikwad
2012-07-15 21:40 ` Mark Brown
2012-07-15 21:40 ` Mark Brown
2012-07-15 23:42 ` Rob Herring
2012-07-15 23:42 ` Rob Herring
2012-07-16 18:36 ` Turquette, Mike
2012-07-16 18:36 ` Turquette, Mike
2012-07-17 12:37 ` Prashant Gaikwad
2012-07-17 12:49 ` Prashant Gaikwad
2012-07-17 13:20 ` Mark Brown
2012-07-17 13:20 ` Mark Brown
2012-07-17 14:22 ` Prashant Gaikwad
2012-07-17 14:34 ` Prashant Gaikwad
2012-07-17 14:37 ` Mark Brown
2012-07-17 14:37 ` Mark Brown
2012-07-18 12:46 ` Prashant Gaikwad
2012-07-18 12:58 ` Prashant Gaikwad
2012-07-18 21:19 ` Mark Brown
2012-07-18 21:19 ` Mark Brown
2012-07-18 17:08 ` Shawn Guo [this message]
2012-07-18 17:08 ` Shawn Guo
2012-07-11 13:08 함명주
2012-07-11 13:08 ` 함명주
2012-07-11 13:49 ` Peter De Schrijver
2012-07-11 13:49 ` Peter De Schrijver
2012-07-11 13:49 ` Peter De Schrijver
2012-07-11 13:49 ` Peter De Schrijver
2012-07-12 4:22 ` Prashant Gaikwad
2012-07-12 4:34 ` Prashant Gaikwad
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=20120718170838.GA27581@S2101-09.ap.freescale.net \
--to=shawn.guo@linaro.org \
--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 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.