From: Stefan Wahren <stefan.wahren@i2se.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Shawn Guo <shawn.guo@freescale.com>,
Lucas Stach <l.stach@pengutronix.de>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Fabio Estevam <festevam@gmail.com>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>
Subject: Re: cpufreq: Unable to set cpufreq to maximum
Date: Mon, 06 Oct 2014 13:12:36 +0200 [thread overview]
Message-ID: <54327924.9090600@i2se.com> (raw)
In-Reply-To: <CAKohpon2VHvfCkGWYQyz1=jhiS4zifX6iY50WV71oGpa2TNSYQ@mail.gmail.com>
Am 06.10.2014 um 12:16 schrieb Viresh Kumar:
> On 6 October 2014 15:35, Stefan Wahren <stefan.wahren@i2se.com> wrote:
>> but cpufreq-cpu0 will select next lower
> Where did this come from in the above theory ?
>
I was wrong. cpufreq-cpu0 will search for a higher OPP than 454736842
and fails:
[ 1111.226006] cpu cpu0: failed to find OPP for 454736842
May be Shawn has an idea or solution.
Sorry for that noise.
Stefan
next prev parent reply other threads:[~2014-10-06 11:12 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
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 [this message]
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=54327924.9090600@i2se.com \
--to=stefan.wahren@i2se.com \
--cc=festevam@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=l.stach@pengutronix.de \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=shawn.guo@freescale.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 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.