linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: sudeep.holla@arm.com (Sudeep Holla)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v9 0/7] ACPI / processor_idle: Add ACPI v6.0 LPI support
Date: Tue, 12 Jul 2016 13:59:23 +0100	[thread overview]
Message-ID: <5784E9AB.1070507@arm.com> (raw)
In-Reply-To: <2164074.OnkmXO2GSJ@vostro.rjw.lan>



On 12/07/16 13:09, Rafael J. Wysocki wrote:
> On Tuesday, July 12, 2016 12:42:06 PM Sudeep Holla wrote:
>>
>> On 08/07/16 18:07, Sudeep Holla wrote:
>>> ACPI 6.0 introduced LPI(Low Power Idle) states that provides an alternate
>>> method to describe processor idle states. It extends the specification
>>> to allow the expression of idle states like C-states selectable by the
>>> OSPM when a processor goes idle, but may affect more than one processor,
>>> and may affect other system components.
>>>
>>> LPI extensions leverages the processor container device(again introduced
>>> in ACPI 6.0) allowing to express which parts of the system are affected
>>> by a given LPI state. It defines the local power states for each node
>>> in a hierarchical processor topology. The OSPM can use _LPI object to
>>> select a local power state for each level of processor hierarchy in the
>>> system. They used to produce a composite power state request that is
>>> presented to the platform by the OSPM.
>>>
>>> Since multiple processors affect the idle state for any non-leaf hierarchy
>>> node, coordination of idle state requests between the processors is
>>> required. ACPI supports two different coordination schemes: Platform
>>> coordinated and  OS initiated.
>>>
>>
>> I was hoping to get this in v4.8 now that merge window is
>> delayed/extended if you have no further comments on this series.
>
> I'll get to it in the next couple of days.  If it looks all good and there are
> no comments, I'll queue it up.
>

Thanks for the update.

-- 
Regards,
Sudeep

  reply	other threads:[~2016-07-12 12:59 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-08 17:07 [PATCH v9 0/7] ACPI / processor_idle: Add ACPI v6.0 LPI support Sudeep Holla
2016-07-08 17:07 ` [PATCH v9 1/7] ACPI / processor_idle: introduce ACPI_PROCESSOR_CSTATE Sudeep Holla
2016-07-08 17:07 ` [PATCH v9 2/7] ACPI / processor_idle: Add support for Low Power Idle(LPI) states Sudeep Holla
2016-07-16  0:32   ` Rafael J. Wysocki
2016-07-18 15:48     ` Sudeep Holla
2016-07-08 17:07 ` [PATCH v9 3/7] arm64: cpuidle: drop __init section marker to arm_cpuidle_init Sudeep Holla
2016-07-12 15:23   ` Catalin Marinas
2016-07-08 17:07 ` [PATCH v9 4/7] cpuidle: introduce CPU_PM_CPU_IDLE_ENTER macro for ARM{32, 64} Sudeep Holla
2016-07-08 17:07 ` [PATCH v9 5/7] drivers: firmware: psci: initialise idle states using ACPI LPI Sudeep Holla
2016-07-08 17:07 ` [PATCH v9 6/7] arm64: add support for ACPI Low Power Idle(LPI) Sudeep Holla
2016-07-12 15:22   ` Catalin Marinas
2016-07-08 17:07 ` [PATCH v9 7/7] ACPI : enable ACPI_PROCESSOR_IDLE on ARM64 Sudeep Holla
2016-07-12 11:42 ` [PATCH v9 0/7] ACPI / processor_idle: Add ACPI v6.0 LPI support Sudeep Holla
2016-07-12 12:09   ` Rafael J. Wysocki
2016-07-12 12:59     ` Sudeep Holla [this message]
2016-07-14  1:15       ` Rafael J. Wysocki

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=5784E9AB.1070507@arm.com \
    --to=sudeep.holla@arm.com \
    --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).