All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hanjun Guo <hanjun.guo@linaro.org>
To: Kevin Wilson <wkevils@gmail.com>,
	"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>
Subject: Re: Question about ACPI 6 and the Linux kernel
Date: Tue, 04 Aug 2015 18:05:50 +0800	[thread overview]
Message-ID: <55C08E7E.50102@linaro.org> (raw)
In-Reply-To: <CAGXs5wVGn1DUXPw94cEXp5KZWq=bUCBpNPE_irgO32y94V8C0g@mail.gmail.com>

Hi Kevin,

On 08/04/2015 12:35 PM, Kevin Wilson wrote:
> Hi all,
> Is the current ACPI linux subsystem, that you find in the official Linus tree,
>   compliant (even partially) with ACPI 6 ? (which was released in April 2015)
>
> or is it now compliant only with ACPI 5 ?

ACPI 6 have lots of new features, such as add support for NVDIMM
(persistent memory), hierarchical lower-power idle states of CPUs, CPU
clusters, and some support for ARM platforms (GIC, SMMU and etc.),
and more...

so what the specific features are you referring to?

>
> What are the plans for ACPI 6? Is there already some git branch for it ?

For all the ACPI 6 new features, ACPICA already add its support in 4.2,
and some of the ACPI driver support also is ready, such as support for
persistent memory [1] is ready, and Linaro is leading the ACPI 6.0 for
ARM support, but as far as I can know, some of ACPI 6.0 features are
still under development at now.

I think the main support for ACPI 6.0 is in Rafael's tree:
git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git

[1]: https://lwn.net/Articles/640891/

Thanks
Hanjun

  reply	other threads:[~2015-08-04 10:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-04  4:35 Question about ACPI 6 and the Linux kernel Kevin Wilson
2015-08-04 10:05 ` Hanjun Guo [this message]
2015-08-05 13:46   ` 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=55C08E7E.50102@linaro.org \
    --to=hanjun.guo@linaro.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=wkevils@gmail.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.