From: Sudeep KarkadaNagesha <Sudeep.KarkadaNagesha@arm.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: "cpufreq@vger.kernel.org" <cpufreq@vger.kernel.org>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [PATCH v2 0/5] PM / OPP: updates to enable sharing OPPs info
Date: Thu, 17 Oct 2013 18:26:50 +0100 [thread overview]
Message-ID: <52601DDA.1020105@arm.com> (raw)
In-Reply-To: <3220965.oF35vmiThF@vostro.rjw.lan>
Hi Rafael,
On 17/10/13 00:12, Rafael J. Wysocki wrote:
> On Tuesday, October 01, 2013 02:32:57 PM Sudeep KarkadaNagesha wrote:
>> From: Sudeep KarkadaNagesha <sudeep.karkadanagesha@arm.com>
>>
>> Hi,
>>
>> These are few updates to existing device tree binding and the PM/OPP
>> library to support sharing of OPPs between different device nodes.
>>
>> Currently all the cpu nodes are parsed until the OPPs are found. This
>> is essential to support cpuhotplug without having to replicate OPP
>> information in all the cpu nodes.
>>
>> However in systems with multiple cpu power domain, its better to have
>> OPP entry for each cpu. To avoid replication, phandle can be specified
>> to the node which contains the full OPP information.
>>
>> The table node containing all the OPPs and device nodes pointing to an
>> entry into it through phandle might also solve the problem of describing
>> multiple OPP profiles.
>
> It looks like this still is under discussion, isn't it?
>
> If not, care to obtain ACKs from the people involved and resubmit?
>
Thanks for following up on this patches. Since the entire series is based on the
DT binding in PATCH 1, which is still in discussion and subject to change, I
don't think its ready yet.
Regards,
Sudeep
prev parent reply other threads:[~2013-10-17 17:26 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-01 13:32 [PATCH v2 0/5] PM / OPP: updates to enable sharing OPPs info Sudeep KarkadaNagesha
2013-10-01 13:32 ` [PATCH v2 2/5] PM / OPP: add support to specify phandle of another node for OPP Sudeep KarkadaNagesha
[not found] ` <1380634382-15609-3-git-send-email-Sudeep.KarkadaNagesha-5wv7dgnIgG8@public.gmane.org>
2013-10-01 16:46 ` Sudeep KarkadaNagesha
[not found] ` <524AFC52.8080201-5wv7dgnIgG8@public.gmane.org>
2013-10-03 14:20 ` Nishanth Menon
2013-10-03 15:39 ` Sudeep KarkadaNagesha
[not found] ` <1380634382-15609-1-git-send-email-Sudeep.KarkadaNagesha-5wv7dgnIgG8@public.gmane.org>
2013-10-01 13:32 ` [PATCH v2 1/5] PM / OPP: extend DT binding " Sudeep KarkadaNagesha
2013-10-03 12:40 ` Nishanth Menon
[not found] ` <524D65A3.5090906-l0cyMroinI0@public.gmane.org>
2013-10-03 13:05 ` Sudeep KarkadaNagesha
2013-10-03 14:29 ` Nishanth Menon
2013-10-07 12:40 ` Sudeep KarkadaNagesha
2013-10-07 16:01 ` Rob Herring
2013-10-08 12:55 ` Sudeep KarkadaNagesha
2013-10-17 11:15 ` Sudeep KarkadaNagesha
2013-10-17 13:22 ` Rob Herring
2013-10-17 17:22 ` Sudeep KarkadaNagesha
2013-10-17 18:36 ` Nishanth Menon
2013-10-18 8:40 ` Lorenzo Pieralisi
2013-10-01 13:33 ` [PATCH v2 3/5] PM / OPP: check for existing OPP list when initialising from device tree Sudeep KarkadaNagesha
2013-10-03 4:54 ` Viresh Kumar
[not found] ` <1380634382-15609-4-git-send-email-Sudeep.KarkadaNagesha-5wv7dgnIgG8@public.gmane.org>
2013-10-03 14:25 ` Nishanth Menon
2013-10-01 13:33 ` [PATCH v2 4/5] cpufreq: arm_big_little_dt: enhance OPP error checking Sudeep KarkadaNagesha
2013-10-03 4:55 ` Viresh Kumar
[not found] ` <1380634382-15609-5-git-send-email-Sudeep.KarkadaNagesha-5wv7dgnIgG8@public.gmane.org>
2013-10-03 14:26 ` Nishanth Menon
2013-10-01 13:33 ` [PATCH v2 5/5] cpufreq: arm_big_little_dt: return success if OPP list already exists Sudeep KarkadaNagesha
[not found] ` <1380634382-15609-6-git-send-email-Sudeep.KarkadaNagesha-5wv7dgnIgG8@public.gmane.org>
2013-10-03 4:54 ` Viresh Kumar
2013-10-16 23:12 ` [PATCH v2 0/5] PM / OPP: updates to enable sharing OPPs info Rafael J. Wysocki
2013-10-17 17:26 ` Sudeep KarkadaNagesha [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=52601DDA.1020105@arm.com \
--to=sudeep.karkadanagesha@arm.com \
--cc=cpufreq@vger.kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
/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.