From: Prashant Gaikwad <pgaikwad@nvidia.com> To: linux-arm-kernel@lists.infradead.org Subject: Re: Device tree binding for DVFS table Date: Tue, 17 Jul 2012 14:34:12 +0000 [thread overview] Message-ID: <50057514.5070501@nvidia.com> (raw) In-Reply-To: <20120717132032.GD27595@sirena.org.uk> On Tuesday 17 July 2012 06:50 PM, Mark Brown wrote: > On Tue, Jul 17, 2012 at 06:07:23PM +0530, Prashant Gaikwad wrote: >> On Tuesday 17 July 2012 12:06 AM, Turquette, Mike wrote: >> reg : operating voltage in microvolt > What happens if there's more than one supply that needs to be varied? Each rail's dvfs-table will have OPP nodes defined for different voltages and each OPP node contains frequency for all clocks affecting that rail. Just for presentation: In following example when <&ref 1> clock rate is set to 500000, sm0 need to operate at 750000000 micrvolt and sm1 at 800000000. dvfs-rail-1 { reg_id = <&sm0>; opp@750000000 { frequency-table@102 { frequencies = <&osc 0 314000>, <&ref 1 500000>; }; }; }; dvfs-rail-2 { reg_id = <&sm1>; opp@800000000 { frequency-table@102 { frequencies = <&ref 1 5000000>; }; }; }; >> tolerance : can be used to calculate required voltage. (optional, >> can be replaced by other relevant parameter to calculate required >> voltage) > What are the semantics of this field? I used "tolerance" just for example to derive the range of voltage. May be as done for OMAP, regulator_set_voltage(mpu_reg, volt - tol, volt + tol);
WARNING: multiple messages have this Message-ID (diff)
From: pgaikwad@nvidia.com (Prashant Gaikwad) To: linux-arm-kernel@lists.infradead.org Subject: Device tree binding for DVFS table Date: Tue, 17 Jul 2012 19:52:12 +0530 [thread overview] Message-ID: <50057514.5070501@nvidia.com> (raw) In-Reply-To: <20120717132032.GD27595@sirena.org.uk> On Tuesday 17 July 2012 06:50 PM, Mark Brown wrote: > On Tue, Jul 17, 2012 at 06:07:23PM +0530, Prashant Gaikwad wrote: >> On Tuesday 17 July 2012 12:06 AM, Turquette, Mike wrote: >> reg : operating voltage in microvolt > What happens if there's more than one supply that needs to be varied? Each rail's dvfs-table will have OPP nodes defined for different voltages and each OPP node contains frequency for all clocks affecting that rail. Just for presentation: In following example when <&ref 1> clock rate is set to 500000, sm0 need to operate at 750000000 micrvolt and sm1 at 800000000. dvfs-rail-1 { reg_id = <&sm0>; opp at 750000000 { frequency-table at 102 { frequencies = <&osc 0 314000>, <&ref 1 500000>; }; }; }; dvfs-rail-2 { reg_id = <&sm1>; opp at 800000000 { frequency-table at 102 { frequencies = <&ref 1 5000000>; }; }; }; >> tolerance : can be used to calculate required voltage. (optional, >> can be replaced by other relevant parameter to calculate required >> voltage) > What are the semantics of this field? I used "tolerance" just for example to derive the range of voltage. May be as done for OMAP, regulator_set_voltage(mpu_reg, volt - tol, volt + tol);
next prev parent reply other threads:[~2012-07-17 14:34 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 [this message] 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 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=50057514.5070501@nvidia.com \ --to=pgaikwad@nvidia.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: linkBe 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.