From: Jon Hunter <jonathanh-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
To: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>,
Thierry Reding
<thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Alexandre Courbot
<gnurou-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
"linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org"
<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>,
Paul Walmsley <pwalmsley-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
Subject: Re: [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-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
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-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
>>
>> ---
>> 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@0,70110000 {
>> + status = "okay";
>> + vdd-cpu-supply = <&vdd_cpu>;
>> + nvidia,i2c-fs-rate = <400000>;
>> + };
>> +
>> ahub@0,70300000 {
>> i2s@0,70301100 {
>> status = "okay";
>> @@ -487,6 +494,12 @@
>> };
>> };
>>
>> + cpus {
>> + cpu@0 {
>> + vdd-cpu-supply = <&vdd_cpu>;
>> + };
>> + };
>> +
>> gpio-keys {
>> compatible = "gpio-keys";
Stephen, Thierry,
Are you ok with this change?
Jon
WARNING: multiple messages have this Message-ID (diff)
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: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-03 11:43 [PATCH] ARM: tegra: Enable CPUFreq support for Tegra124 Chromebooks Jon Hunter
2015-06-03 11:44 ` Jon Hunter
2015-06-03 11:44 ` Jon Hunter
[not found] ` <556EE8B0.2060205-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2015-07-13 13:08 ` Jon Hunter [this message]
2015-07-13 13:08 ` Jon Hunter
[not found] ` <55A3B848.2080205-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2015-09-03 13:40 ` Tomeu Vizoso
2015-09-03 13:40 ` Tomeu Vizoso
[not found] ` <CAAObsKA0N50gfPA9sMZfnM8N+N9Oo-YHMCDdF7JdWjpxXtFJbA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-09-15 8:12 ` Thierry Reding
2015-09-15 8:12 ` Thierry Reding
[not found] ` <20150915081234.GA25970-AwZRO8vwLAwmlAP/+Wk3EA@public.gmane.org>
2015-09-15 9:00 ` Tomeu Vizoso
2015-09-15 9:00 ` Tomeu Vizoso
2015-11-04 12:16 ` Jon Hunter
2015-11-04 12:16 ` Jon Hunter
[not found] ` <5639F728.6090808-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2015-11-04 12:19 ` Jon Hunter
2015-11-04 12:19 ` Jon Hunter
[not found] ` <5639F7EC.2000508-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2015-11-04 13:23 ` Jon Hunter
2015-11-04 13:23 ` Jon Hunter
[not found] ` <563A06B4.2070005-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2015-11-20 15:20 ` 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-ddmlm1+adcrqt0dzr+alfa@public.gmane.org \
--cc=gnurou-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=pwalmsley-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
--cc=swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org \
--cc=thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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.