From: "Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: rjw@rjwysocki.net, mroos@linux.ee,
linaro-kernel@lists.linaro.org, cpufreq@vger.kernel.org,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] cpufreq: Set CPUFREQ_ASYNC_NOTIFICATION for drivers handling notification
Date: Fri, 25 Apr 2014 13:52:51 +0530 [thread overview]
Message-ID: <535A1B5B.9000705@linux.vnet.ibm.com> (raw)
In-Reply-To: <c6c53fee017018869c7524a487688edf902c1413.1398412138.git.viresh.kumar@linaro.org>
On 04/25/2014 01:22 PM, Viresh Kumar wrote:
> CPUFREQ_ASYNC_NOTIFICATION was initially designed for drivers which don't want
> core to send notifications for them as they wouldn't finish frequency
> transitions in ->target_index().
>
And let's keep it that way. Overloading ASYNC_NOTIFICATION with other meanings
is a bad idea.
> But there were other kinds of drivers as well who don't have straight forward
> implementations of ->target_index() routines and wanted to handle notifications
> themselves.
>
Looking at longhaul, powernow-k6 and powernow-k7, I think we can safely remove
the extra notifications from them and let them depend on the cpufreq core's set
of notifications. The patchset I posted just now uses that design.
Regards,
Srivatsa S. Bhat
prev parent reply other threads:[~2014-04-25 8:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-25 7:52 [PATCH] cpufreq: Set CPUFREQ_ASYNC_NOTIFICATION for drivers handling notification Viresh Kumar
2014-04-25 8:22 ` Srivatsa S. Bhat [this message]
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=535A1B5B.9000705@linux.vnet.ibm.com \
--to=srivatsa.bhat@linux.vnet.ibm.com \
--cc=cpufreq@vger.kernel.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mroos@linux.ee \
--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.