From: viresh.kumar@linaro.org (viresh kumar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/7] OPP: Redefine bindings to overcome shortcomings
Date: Wed, 25 Feb 2015 09:15:32 +0530 [thread overview]
Message-ID: <54ED455C.3010700@linaro.org> (raw)
In-Reply-To: <7h8ufn8c8q.fsf@deeprootsystems.com>
On Tuesday 24 February 2015 10:42 PM, Kevin Hilman wrote:
> Viresh Kumar <viresh.kumar@linaro.org> writes:
> s/they share clock lines/they share clock and/or voltage lines/
Hmm, will update that.
> OK, fair enough. Looks like it's been thought through.
>
> However, in the end, I don't think it's going to avoid the "help of some
> algorithms." The flag will tell you it's shared, but not how, and that
> will likely still need to be determined.
What did you mean by 'how' here? You wanted to say which devices share the
OPP? Yeah, a small piece of code is required and that's present in my patchset.
next prev parent reply other threads:[~2015-02-25 3:45 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-11 8:16 [PATCH 0/7] OPP: Introduce OPP bindings V2 and supporting code Viresh Kumar
2015-02-11 8:16 ` [PATCH 1/7] OPP: Redefine bindings to overcome shortcomings Viresh Kumar
2015-02-23 22:36 ` Kevin Hilman
2015-02-24 4:24 ` Viresh Kumar
2015-02-24 17:12 ` Kevin Hilman
2015-02-25 3:45 ` viresh kumar [this message]
2015-02-11 8:16 ` [PATCH 2/7] opp: Relocate few routines Viresh Kumar
2015-02-11 8:16 ` [PATCH 3/7] OPP: Break _opp_add_dynamic() into smaller functions Viresh Kumar
2015-02-11 8:16 ` [PATCH 4/7] opp: Parse new (v2) bindings Viresh Kumar
2015-02-11 8:16 ` [PATCH 5/7] opp: convert device_opp->dev to a list of devices Viresh Kumar
2015-02-11 8:16 ` [PATCH 6/7] opp: Add helpers for initializing CPU opps Viresh Kumar
2015-02-11 8:16 ` [PATCH 7/7] cpufreq-dt: Use DT to set policy->cpus/related_cpus Viresh Kumar
2015-02-12 0:52 ` [PATCH 0/7] OPP: Introduce OPP bindings V2 and supporting code Stephen Boyd
2015-02-12 7:22 ` Viresh Kumar
2015-02-12 8:20 ` Stephen Boyd
2015-02-17 7:46 ` Viresh Kumar
2015-03-22 18:56 ` Mark Brown
2015-02-27 5:25 ` Viresh Kumar
2015-03-16 9:54 ` Viresh Kumar
2015-04-01 6:22 ` Viresh Kumar
2015-04-01 16:43 ` Rob Herring
2015-04-02 3:00 ` 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=54ED455C.3010700@linaro.org \
--to=viresh.kumar@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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).