From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Dirk Brandewie <dirk.brandewie@gmail.com>,
Lists linaro-kernel <linaro-kernel@lists.linaro.org>,
Patch Tracking <patches@linaro.org>,
"cpufreq@vger.kernel.org" <cpufreq@vger.kernel.org>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Nishanth Menon <nm@ti.com>, Carlos Hernandez <ceh@ti.com>
Subject: Re: [PATCH V2] cpufreq: Make sure CPU is running on a freq from freq-table
Date: Wed, 27 Nov 2013 15:22:01 +0100 [thread overview]
Message-ID: <4759452.7dXrrSTGCc@vostro.rjw.lan> (raw)
In-Reply-To: <CAKohpokjAuUA-o4cJi=N7mO93kTwrmfVqtL-zOHAs6awKoXn1A@mail.gmail.com>
On Wednesday, November 27, 2013 08:31:02 AM Viresh Kumar wrote:
> On 27 November 2013 01:51, Rafael J. Wysocki <rjw@rjwysocki.net> wrote:
> > I was talking about the case when your
> >
> > __cpufreq_driver_target(policy, policy->cur - 1, CPUFREQ_RELATION_L);
> >
> > fails. The other case is not really interesting.
>
> Okay.. I actually thought the context of this chat is about "not fixing the
> frequency silently". That's what Dirk pointed out, if I am not wrong.
In that case you can simply print a message bashing the boot loader. :-)
> And hence I also support the new pr_warn I have added in those cases.
Sure.
> But yes a WARN_ON() can be printed out in case
> __cpufreq_driver_target() fails.
And here my question was: Is it safe to continue at all in that case?
Rafael
next prev parent reply other threads:[~2013-11-27 14:13 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-25 4:23 Viresh Kumar
2013-11-25 16:38 ` Dirk Brandewie
2013-11-25 17:01 ` Viresh Kumar
2013-11-25 17:43 ` Dirk Brandewie
2013-11-25 21:13 ` Rafael J. Wysocki
2013-11-26 2:01 ` Viresh Kumar
2013-11-26 6:14 ` viresh kumar
2013-11-26 20:21 ` Rafael J. Wysocki
2013-11-27 3:01 ` Viresh Kumar
2013-11-27 14:22 ` Rafael J. Wysocki [this message]
2013-11-27 15:52 ` Viresh Kumar
2013-11-27 20:21 ` Rafael J. Wysocki
2013-11-28 3:20 ` Viresh Kumar
2013-11-28 13:09 ` Rafael J. Wysocki
2013-11-28 13:41 ` Viresh Kumar
2013-11-28 14:12 ` Rafael J. Wysocki
2013-11-28 14:14 ` Viresh Kumar
2013-11-28 20:31 ` Rafael J. Wysocki
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=4759452.7dXrrSTGCc@vostro.rjw.lan \
--to=rjw@rjwysocki.net \
--cc=ceh@ti.com \
--cc=cpufreq@vger.kernel.org \
--cc=dirk.brandewie@gmail.com \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=nm@ti.com \
--cc=patches@linaro.org \
--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
Powered by JetHome