linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: myungjoo.ham@samsung.com (함명주)
To: linux-arm-kernel@lists.infradead.org
Subject: Device tree binding for DVFS table
Date: Wed, 11 Jul 2012 13:08:15 +0000 (GMT)	[thread overview]
Message-ID: <20748722.319671342012092123.JavaMail.weblogic@epml17> (raw)

> 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.

Hello,

It seems that in the example, the values in "voltage-array" and
"frequencies" are switched.

Anyway, what about SoCs that reads information from IEM (or any other module)
 to measure gate delays or some other value to set the appriorate voltage values
 for every possible frequency? I remember some of Exynos SoCs have been doing
 it; dynamically measure the characteristics at boot-up time and apply voltages
 accordingly; they couldn't identify it based on the chip-id or simply by reading
 a single register.


Cheers!
MyungJoo.

> 
> Following is the proposed binding for voltage and frequency tables used 
> in DVFS. Looking for comments/suggestions to make it generic.

             reply	other threads:[~2012-07-11 13:08 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-11 13:08 함명주 [this message]
2012-07-11 13:49 ` Device tree binding for DVFS table Peter De Schrijver
2012-07-11 13:49 ` Peter De Schrijver
2012-07-12  4:22   ` Prashant Gaikwad
  -- strict thread matches above, loose matches on Subject: below --
2012-07-11 12:56 Prashant Gaikwad
2012-07-11 14:03 ` Rob Herring
2012-07-11 14:44   ` Mark Brown
2012-07-11 20:04     ` Mike Turquette
2012-07-12  4:14       ` Prashant Gaikwad
2012-07-12 14:10       ` Peter De Schrijver
2012-07-12 17:10         ` Mike Turquette
2012-07-12 17:15           ` Mark Brown
2012-07-13 10:34           ` Peter De Schrijver
2012-07-13 17:25             ` Mike Turquette
2012-07-12  4:17     ` Prashant Gaikwad
2012-07-12 15:23       ` Mark Brown
2012-07-12 17:01       ` Mike Turquette
2012-07-12  8:19     ` Peter De Schrijver
2012-07-12  4:08   ` Prashant Gaikwad
2012-07-13 18:30     ` Prashant Gaikwad
2012-07-15 21:40       ` Mark Brown
2012-07-15 23:42     ` Rob Herring
2012-07-16 18:36       ` Turquette, Mike
2012-07-17 12:37         ` Prashant Gaikwad
2012-07-17 13:20           ` Mark Brown
2012-07-17 14:22             ` Prashant Gaikwad
2012-07-17 14:37               ` Mark Brown
2012-07-18 12:46                 ` Prashant Gaikwad
2012-07-18 21:19                   ` Mark Brown
2012-07-18 17:08 ` Shawn Guo

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=20748722.319671342012092123.JavaMail.weblogic@epml17 \
    --to=myungjoo.ham@samsung.com \
    --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).