linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lucas Stach <l.stach@pengutronix.de>
To: Stefan Wahren <stefan.wahren@i2se.com>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
	Viresh Kumar <viresh.kumar@linaro.org>,
	linux-pm@vger.kernel.org, festevam@gmail.com,
	gregkh@linuxfoundation.org
Subject: Re: cpufreq: Unable to set cpufreq to maximum
Date: Thu, 02 Oct 2014 15:59:12 +0200	[thread overview]
Message-ID: <1412258352.4875.5.camel@pengutronix.de> (raw)
In-Reply-To: <936524880.154802.1412255867221.JavaMail.open-xchange@oxbaltgw07.schlund.de>

Am Donnerstag, den 02.10.2014, 15:17 +0200 schrieb Stefan Wahren:
> Hi,
> 
> i currently try to get cpufreq-cpu0 aka cpufreq-dt running on Freescale i.MX28
> (ARM). First i ported the regulator driver and now i want to test it with
> cpufreq-cpu0. Everything works fine except changing back to maximum frequency
> 454736 kHz. I get the following error:
> 
> root@duckbill:/sys/devices/system/cpu/cpu0/cpufreq# echo "454736" >
> scaling_setspeed
> [ 1111.226006] cpu cpu0: failed to find OPP for 454736842
> [ 1111.231399] cpufreq: __target_index: Failed to change cpu frequency: -34
> 
> I'm using 3.17.0-rc7-00466-g6f28c5c-dirty #1 Thu Oct 2 12:07:49 UTC 2014
> armv5tejl GNU/Linux and here is the relevant part of the dts file:
> 
> cpus {
> 	#address-cells = <1>;
> 	#size-cells = <0>;
> 
> 	cpu@0 {
> 		compatible = "arm,arm926ej-s";
> 		device_type = "cpu";
> 		reg = <0x0>;
> 		operating-points = <
> 			/* kHz	uV */
> 			454736  1550000
> 			392727  1475000
> 			360000  1375000
> 			261818  1275000
> 			64000   1050000
> 		>;
> 		clocks = <&clks 4>;
> 		clock-latency = <61036>; /* two CLK32 periods */
> 		cpu0-supply = <&reg_vddd>;
> 	};
> };
> 
> It looks to me like a rounding problem.
> 
> For the complete history look at:
> http://www.spinics.net/lists/arm-kernel/msg365504.html
> 
> Any ideas?

Isn't your highest OPP just wrong? Apparently the CPU clock (which is a
fixed PLL plus a divider on MX28 if I'm not mistaken) is only able to
provide a slightly higher frequency than your OPP. cpufreq handles that
as an error, which is valid behavior as going higher than the defined
OPP may not be qualified by the vendor.

Does it work if you just change this OPP to 454737 kHz?

Regards,
Lucas
-- 
Pengutronix e.K.             | Lucas Stach                 |
Industrial Linux Solutions   | http://www.pengutronix.de/  |


  reply	other threads:[~2014-10-02 13:59 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-02 13:17 cpufreq: Unable to set cpufreq to maximum Stefan Wahren
2014-10-02 13:59 ` Lucas Stach [this message]
2014-10-02 15:01   ` Stefan Wahren
2014-10-02 15:22     ` Lucas Stach
2014-10-02 16:10       ` Stefan Wahren
2014-10-06  4:21       ` Viresh Kumar
2014-10-06  6:41         ` Stefan Wahren
2014-10-06  8:50           ` Viresh Kumar
2014-10-06  9:13             ` Stefan Wahren
2014-10-06  9:26               ` Viresh Kumar
2014-10-06 10:05                 ` Stefan Wahren
2014-10-06 10:16                   ` Viresh Kumar
2014-10-06 11:12                     ` Stefan Wahren
2014-10-06 11:18                       ` 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=1412258352.4875.5.camel@pengutronix.de \
    --to=l.stach@pengutronix.de \
    --cc=festevam@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    --cc=stefan.wahren@i2se.com \
    --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 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).