From: Sudeep Holla <sudeep.holla@arm.com>
To: Daniel Lezcano <daniel.lezcano@linaro.org>
Cc: Sudeep Holla <sudeep.holla@arm.com>,
rjw@rjwysocki.net, lorenzo.pieralisi@arm.com, leo.yan@linaro.org,
"open list:CPUIDLE DRIVERS" <linux-pm@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ARM: cpuidle: Support asymmetric idle definition
Date: Wed, 31 May 2017 18:33:52 +0100 [thread overview]
Message-ID: <160c3091-2d10-9c7b-c55b-e76abf23653f@arm.com> (raw)
In-Reply-To: <77df6298-945b-7663-0cb9-cd24fa583c6a@linaro.org>
On 31/05/17 17:40, Daniel Lezcano wrote:
> Hi Sudeep, Lorenzo,
>
> I have been thinking and looking at the domain-idle-state and I don't
> see an obvious connection between what is describing the power domain,
> the cpu idle driver and what we are trying to achieve.
>
I am not sure what you mean by *connection* above.
1. With old flat list of idle states, we should get the cpumask sharing
the idle states from the phandle or something similar.
2. With new domain-idle-state and hierarchical DT binding, you just need
to infer that from the hierarchy.
> I would like to suggest something much more simple, register a cpuidle
> driver per cpu, so every cpu can have its own idle definitions, that
> should work for dynamiQ, smp and hmp. The impact on the driver will be
> minimal.
>
Sounds simple, but not sure if it's scalable on platforms with
relatively large number of CPUs like 48 or 96(e.g. Cavium Thunder
--
Regards,
Sudeep
next prev parent reply other threads:[~2017-05-31 17:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-19 16:45 [PATCH] ARM: cpuidle: Support asymmetric idle definition Daniel Lezcano
2017-05-22 10:11 ` Sudeep Holla
2017-05-22 10:20 ` Daniel Lezcano
2017-05-22 10:32 ` Sudeep Holla
2017-05-22 12:41 ` Daniel Lezcano
2017-05-22 13:02 ` Sudeep Holla
2017-05-22 13:34 ` Leo Yan
2017-05-22 13:59 ` Sudeep Holla
2017-05-22 14:48 ` Daniel Lezcano
2017-05-22 15:02 ` Sudeep Holla
2017-05-31 16:40 ` Daniel Lezcano
2017-05-31 17:33 ` Sudeep Holla [this message]
2017-06-01 7:37 ` Daniel Lezcano
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=160c3091-2d10-9c7b-c55b-e76abf23653f@arm.com \
--to=sudeep.holla@arm.com \
--cc=daniel.lezcano@linaro.org \
--cc=leo.yan@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox