From: jonathanh@nvidia•com (Jon Hunter)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH] ARM: tegra: Enable CPUFreq support for Tegra124 Chromebooks
Date: Mon, 13 Jul 2015 14:08:24 +0100 [thread overview]
Message-ID: <55A3B848.2080205@nvidia.com> (raw)
In-Reply-To: <556EE8B0.2060205@nvidia.com>
On 03/06/15 12:44, Jon Hunter wrote:
> Adding LAKML. Jon
>
> On 03/06/15 12:43, Jon Hunter wrote:
>> Add the device-tree DFLL clock node and CPU regulator phandle for
>> tegra124 chromebooks to enable CPUFreq support on these boards.
>>
>> Signed-off-by: Jon Hunter <jonathanh@nvidia•com>
>>
>> ---
>> This has been tested on a tegra124 nyan-big by using the userspace
>> CPUFreq governor with a simple CPU benchmark to measure the time taken
>> for the test to execute.
>>
>> The tegra124 chromebooks use the same ams,as3722 PMIC as the Jetson TK1
>> board and hence, this change is based upon that for the Jetson TK1.
>>
>> arch/arm/boot/dts/tegra124-nyan.dtsi | 15 ++++++++++++++-
>> 1 file changed, 14 insertions(+), 1 deletion(-)
>>
>> diff --git a/arch/arm/boot/dts/tegra124-nyan.dtsi b/arch/arm/boot/dts/tegra124-nyan.dtsi
>> index a9aec23e06f2..40c23a0b7cfc 100644
>> --- a/arch/arm/boot/dts/tegra124-nyan.dtsi
>> +++ b/arch/arm/boot/dts/tegra124-nyan.dtsi
>> @@ -159,7 +159,7 @@
>> vin-ldo9-10-supply = <&vdd_5v0_sys>;
>> vin-ldo11-supply = <&vdd_3v3_run>;
>>
>> - sd0 {
>> + vdd_cpu: sd0 {
>> regulator-name = "+VDD_CPU_AP";
>> regulator-min-microvolt = <700000>;
>> regulator-max-microvolt = <1350000>;
>> @@ -397,6 +397,13 @@
>> non-removable;
>> };
>>
>> + /* CPU DFLL clock */
>> + clock at 0,70110000 {
>> + status = "okay";
>> + vdd-cpu-supply = <&vdd_cpu>;
>> + nvidia,i2c-fs-rate = <400000>;
>> + };
>> +
>> ahub at 0,70300000 {
>> i2s at 0,70301100 {
>> status = "okay";
>> @@ -487,6 +494,12 @@
>> };
>> };
>>
>> + cpus {
>> + cpu at 0 {
>> + vdd-cpu-supply = <&vdd_cpu>;
>> + };
>> + };
>> +
>> gpio-keys {
>> compatible = "gpio-keys";
Stephen, Thierry,
Are you ok with this change?
Jon
next prev parent reply other threads:[~2015-07-13 13:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1433331821-9648-1-git-send-email-jonathanh@nvidia.com>
2015-06-03 11:44 ` [PATCH] ARM: tegra: Enable CPUFreq support for Tegra124 Chromebooks Jon Hunter
2015-07-13 13:08 ` Jon Hunter [this message]
2015-09-03 13:40 ` Tomeu Vizoso
2015-09-15 8:12 ` Thierry Reding
2015-09-15 9:00 ` Tomeu Vizoso
2015-11-04 12:16 ` Jon Hunter
2015-11-04 12:19 ` Jon Hunter
2015-11-04 13:23 ` Jon Hunter
2015-11-20 15:20 ` Jon Hunter
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=55A3B848.2080205@nvidia.com \
--to=jonathanh@nvidia$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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