From: Kevin Hilman <khilman@ti.com>
To: Trinabh Gupta <trinabh@linux.vnet.ibm.com>
Cc: venki@google.com, davinci-linux-open-source@linux.davincidsp.com,
ak@linux.intel.com, len.brown@intel.com, peterz@infradead.org,
linux-sh@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-acpi@vger.kernel.org, linux-pm@lists.linux-foundation.org,
linux-omap@vger.kernel.org, arjan@linux.intel.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [RFC PATCH V3 4/4] cpuidle: Single/Global registration of idle states
Date: Fri, 22 Apr 2011 16:06:42 -0700 [thread overview]
Message-ID: <871v0tvqbh.fsf__3609.76047018102$1303513745$gmane$org@ti.com> (raw)
In-Reply-To: <4DAFB847.50404@linux.vnet.ibm.com> (Trinabh Gupta's message of "Thu, 21 Apr 2011 10:23:27 +0530")
Hi Trinabh,
Trinabh Gupta <trinabh@linux.vnet.ibm.com> writes:
[...]
> I just wanted to get comments on the design and understand how it
> affects various architectures in question. It looks to me as if the
> design should be okay and infact better for architectures like ARM
> since they do not have different idle states for different cpus and
> thus do not require per-cpu registration. Global registration would
> work and be simpler; please correct me if I am wrong.
Yes, I agree that the new design is better, I especially like that it's
more clear (and expected) that final state decision making is to be done
directly in the driver without the back-and-forth in the current setup.
Thanks,
Kevin
next prev parent reply other threads:[~2011-04-22 23:06 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-20 6:55 [RFC PATCH V3 0/4] cpuidle: global registration of idle states with per-cpu statistics Trinabh Gupta
2011-04-20 6:55 ` [RFC PATCH V3 0/4] cpuidle: global registration of idle states with Trinabh Gupta
2011-04-20 6:55 ` [RFC PATCH V3 0/4] cpuidle: global registration of idle states with per-cpu statistics Trinabh Gupta
2011-04-20 6:55 ` Trinabh Gupta
2011-04-20 6:55 ` [RFC PATCH V3 1/4] cpuidle: Move dev->last_residency update to driver enter routine; remove dev->last_state Trinabh Gupta
2011-04-20 6:55 ` [RFC PATCH V3 1/4] cpuidle: Move dev->last_residency update to driver Trinabh Gupta
2011-04-20 6:55 ` [RFC PATCH V3 1/4] cpuidle: Move dev->last_residency update to driver enter routine; remove dev->last_state Trinabh Gupta
2011-04-20 17:27 ` [linux-pm] [RFC PATCH V3 1/4] cpuidle: Move dev->last_residency update to driver enter routine; Kevin Hilman
2011-04-20 17:27 ` [linux-pm] [RFC PATCH V3 1/4] cpuidle: Move dev->last_residency update to driver enter routine; remove dev->last_state Kevin Hilman
2011-04-20 17:27 ` Kevin Hilman
2011-04-21 4:42 ` Trinabh Gupta
2011-04-21 4:42 ` [linux-pm] " Trinabh Gupta
2011-04-21 4:54 ` [linux-pm] [RFC PATCH V3 1/4] cpuidle: Move dev->last_residency Trinabh Gupta
2011-04-21 4:42 ` [linux-pm] [RFC PATCH V3 1/4] cpuidle: Move dev->last_residency update to driver enter routine; remove dev->last_state Trinabh Gupta
2011-04-20 17:27 ` Kevin Hilman
2011-04-20 6:55 ` Trinabh Gupta
2011-04-20 6:55 ` Trinabh Gupta
2011-04-20 6:55 ` [RFC PATCH V3 2/4] cpuidle: Remove CPUIDLE_FLAG_IGNORE and dev->prepare() Trinabh Gupta
2011-04-20 6:55 ` Trinabh Gupta
2011-04-20 6:56 ` [RFC PATCH V3 2/4] cpuidle: Remove CPUIDLE_FLAG_IGNORE and Trinabh Gupta
2011-04-20 6:55 ` [RFC PATCH V3 2/4] cpuidle: Remove CPUIDLE_FLAG_IGNORE and dev->prepare() Trinabh Gupta
2011-04-20 6:56 ` [RFC PATCH V3 3/4] Split cpuidle_state structure and move per-cpu statistics fields Trinabh Gupta
2011-04-20 6:56 ` [RFC PATCH V3 3/4] Split cpuidle_state structure and move per-cpu Trinabh Gupta
2011-04-20 6:56 ` [RFC PATCH V3 3/4] Split cpuidle_state structure and move per-cpu statistics fields Trinabh Gupta
2011-04-20 6:56 ` Trinabh Gupta
2011-04-20 6:56 ` [RFC PATCH V3 4/4] cpuidle: Single/Global registration of idle states Trinabh Gupta
2011-04-20 6:56 ` Trinabh Gupta
2011-04-20 6:57 ` Trinabh Gupta
2011-04-20 6:56 ` Trinabh Gupta
2011-04-20 17:33 ` Kevin Hilman
2011-04-20 17:33 ` [linux-pm] " Kevin Hilman
2011-04-20 17:33 ` Kevin Hilman
2011-04-20 17:33 ` Kevin Hilman
2011-04-20 17:33 ` Kevin Hilman
2011-04-21 4:53 ` Trinabh Gupta
2011-04-21 4:53 ` [linux-pm] [RFC PATCH V3 4/4] cpuidle: Single/Global registration Trinabh Gupta
2011-04-21 4:53 ` [linux-pm] [RFC PATCH V3 4/4] cpuidle: Single/Global registration of idle states Trinabh Gupta
2011-04-22 23:06 ` Kevin Hilman
2011-04-22 23:06 ` Kevin Hilman
2011-04-22 23:06 ` Kevin Hilman
2011-04-22 23:06 ` Kevin Hilman [this message]
2011-04-21 4:53 ` Trinabh Gupta
2011-04-25 12:00 ` [linux-pm] " Trinabh Gupta
2011-04-25 12:12 ` [linux-pm] [RFC PATCH V3 4/4] cpuidle: Single/Global registration Trinabh Gupta
2011-04-25 12:00 ` [linux-pm] [RFC PATCH V3 4/4] cpuidle: Single/Global registration of idle states Trinabh Gupta
2011-04-25 12:00 ` Trinabh Gupta
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='871v0tvqbh.fsf__3609.76047018102$1303513745$gmane$org@ti.com' \
--to=khilman@ti.com \
--cc=ak@linux.intel.com \
--cc=arjan@linux.intel.com \
--cc=davinci-linux-open-source@linux.davincidsp.com \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=linux-sh@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=trinabh@linux.vnet.ibm.com \
--cc=venki@google.com \
/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.