From: Mason <slash.tmp@free.fr>
To: Linux PM <linux-pm@vger.kernel.org>
Cc: Viresh Kumar <viresh.kumar@linaro.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Plain DFS (no voltage scaling)
Date: Tue, 2 Feb 2016 22:11:03 +0100 [thread overview]
Message-ID: <56B11B67.3090600@free.fr> (raw)
Hello,
I plan to enable the on-demand governor on the tango platform:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/arch/arm/boot/dts/tango4-smp8758.dtsi
I found the cpufreq-dt binding doc:
https://www.kernel.org/doc/Documentation/devicetree/bindings/cpufreq/cpufreq-dt.txt
https://www.kernel.org/doc/Documentation/devicetree/bindings/opp/opp.txt
Something is not clear to me:
If my platform cannot scale the voltage, what information
should I put in the voltage part of the DT?
Regards.
WARNING: multiple messages have this Message-ID (diff)
From: slash.tmp@free.fr (Mason)
To: linux-arm-kernel@lists.infradead.org
Subject: Plain DFS (no voltage scaling)
Date: Tue, 2 Feb 2016 22:11:03 +0100 [thread overview]
Message-ID: <56B11B67.3090600@free.fr> (raw)
Hello,
I plan to enable the on-demand governor on the tango platform:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/arch/arm/boot/dts/tango4-smp8758.dtsi
I found the cpufreq-dt binding doc:
https://www.kernel.org/doc/Documentation/devicetree/bindings/cpufreq/cpufreq-dt.txt
https://www.kernel.org/doc/Documentation/devicetree/bindings/opp/opp.txt
Something is not clear to me:
If my platform cannot scale the voltage, what information
should I put in the voltage part of the DT?
Regards.
next reply other threads:[~2016-02-02 21:11 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-02 21:11 Mason [this message]
2016-02-02 21:11 ` Plain DFS (no voltage scaling) Mason
2016-02-03 2:10 ` Viresh Kumar
2016-02-03 2:10 ` Viresh Kumar
2016-02-03 15:35 ` Mason
2016-02-03 15:35 ` Mason
2016-02-03 16:14 ` Viresh Kumar
2016-02-03 16:14 ` Viresh Kumar
2016-02-03 18:25 ` Mason
2016-02-03 18:25 ` Mason
2016-02-04 3:23 ` Viresh Kumar
2016-02-04 3:23 ` Viresh Kumar
2016-02-03 15:07 ` Mason
2016-02-03 15:07 ` Mason
2016-02-03 16:13 ` Viresh Kumar
2016-02-03 16:13 ` Viresh Kumar
2016-02-03 18:19 ` Mason
2016-02-03 18:19 ` Mason
2016-02-04 3:23 ` Viresh Kumar
2016-02-04 3:23 ` Viresh Kumar
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=56B11B67.3090600@free.fr \
--to=slash.tmp@free.fr \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=viresh.kumar@linaro.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.