From: Viresh Kumar <viresh.kumar@linaro.org>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Steve Muckle <steve.muckle@linaro.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Lists linaro-kernel <linaro-kernel@lists.linaro.org>,
Linux PM <linux-pm@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
Morten Rasmussen <morten.rasmussen@arm.com>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Juri Lelli <Juri.Lelli@arm.com>,
Patrick Bellasi <patrick.bellasi@arm.com>
Subject: Re: [PATCH V2] cpufreq: Disallow ->resolve_freq() for drivers providing ->target_index()
Date: Fri, 22 Jul 2016 14:09:19 -0700 [thread overview]
Message-ID: <20160722210919.GC3122@ubuntu> (raw)
In-Reply-To: <1635689.iZWBWcBJ5f@vostro.rjw.lan>
On 22-07-16, 23:11, Rafael J. Wysocki wrote:
> No, they aren't deprecated, not even sort of.
>
> Of course, stuff that can use frequency tables should implement ->target_index,
> because there's no valid reason for it not to do that.
>
> However, there are cases (and not legacy) where frequency tables are simply
> impractical and those drivers have no choice but to implement ->target.
>
> And if you want to try to force them into the frequency tables model
> regardless, then think twice, because I'm not going to let you do that.
No I am not :)
Perhaps this was just mis-worded in the Documentation then.
--
viresh
prev parent reply other threads:[~2016-07-22 21:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-21 21:39 [PATCH V2] cpufreq: Disallow ->resolve_freq() for drivers providing ->target_index() Viresh Kumar
2016-07-21 23:22 ` Rafael J. Wysocki
2016-07-21 23:22 ` Steve Muckle
2016-07-21 23:32 ` Rafael J. Wysocki
2016-07-21 23:45 ` Steve Muckle
2016-07-21 23:53 ` Rafael J. Wysocki
2016-07-22 0:09 ` Steve Muckle
2016-07-22 0:18 ` Rafael J. Wysocki
2016-07-22 0:34 ` Steve Muckle
2016-07-22 15:13 ` Viresh Kumar
2016-07-22 21:11 ` Rafael J. Wysocki
2016-07-22 21:09 ` Viresh Kumar [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=20160722210919.GC3122@ubuntu \
--to=viresh.kumar@linaro.org \
--cc=Juri.Lelli@arm.com \
--cc=dietmar.eggemann@arm.com \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=morten.rasmussen@arm.com \
--cc=patrick.bellasi@arm.com \
--cc=peterz@infradead.org \
--cc=rafael@kernel.org \
--cc=rjw@rjwysocki.net \
--cc=steve.muckle@linaro.org \
--cc=vincent.guittot@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.