From: Al Stone <ahs3 at redhat.com>
To: devel@acpica.org
Subject: Re: [Devel] ACPI 5.0 implementation for armv7 and armv8 architecture
Date: Mon, 17 Dec 2012 16:30:19 -0700 [thread overview]
Message-ID: <50CFAB0B.4000305@redhat.com> (raw)
In-Reply-To: D9DB7F56087E294C83142799ED69E2A0773154C4@G4W3293.americas.hpqcorp.net
[-- Attachment #1: Type: text/plain, Size: 2071 bytes --]
I've only lurked on this list in the past, but this work sounds very
similar to work I've been tasked to take on for Linaro (please see
https://wiki.linaro.org/LEG for the context). I'll be looking at
Cortex A9/A15 and ARMv8 for the same reasons so I'm thinking perhaps
we should coordinate our efforts here...
On 12/02/2012 08:37 PM, Wei, Dong (魏东 UEFI-ACPI) wrote:
> Copying Andrew Sloss from ARM.
>
> -DW
>
> *From:*devel-bounces(a)acpica.org [mailto:devel-bounces(a)acpica.org] *On
> Behalf Of *Ayan Halder
> *Sent:* Sunday, December 02, 2012 5:30 AM
> *To:* devel(a)acpica.org
> *Subject:* [Devel] ACPI 5.0 implementation for armv7 and armv8 architecture
>
> Hi,
>
> I am planning to implement ACPI5.0 on an SOC having Cortex A5 and Atlas
> cpu( based on armv8 architecture) running linux on top of them.
>
> As per the ACPI 5.0 hardware specification(Fixed Hardware/ Generic
> Hardware model) of ACPI5.0, the processor needs to support various low
> power modes(C0, C1, C2, C3) and sleep states(S1, S2, S3, S4, S5) via
> register interfaces as well as OEM provided AML(ACPI Machine Language).
>
> Therefore, which instructions in armv7 and armv8 put the processor into
> the afore-mentioned low power modes and sleep states?
>
> ( The arm instruction manual specifies “wfe” and “wfi” to put the
> processor in a sleep state, but I am not sure if this confirms to the
> ACPI 5.0 requirements )
>
> Besides, does arm provide any AML(ACPI Machine Language) code to put the
> processor to low power modes? If not, then how do we create an ACPI
> machine language code for armv7 and armv8 architecture and do we have an
> AML interpreter for armv7 and armv8 architecture?
>
> Regards,
>
> Ayan Kumar Halder
>
>
>
> _______________________________________________
> Devel mailing list
> Devel(a)acpica.org
> http://lists.acpica.org/listinfo/devel
>
--
ciao,
al
-----------------------------------
Al Stone
Software Engineer
Red Hat, Inc.
ahs3(a)redhat.com
-----------------------------------
next reply other threads:[~2012-12-17 23:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-17 23:30 Al Stone [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-12-18 0:26 [Devel] ACPI 5.0 implementation for armv7 and armv8 architecture Zheng, Lv
2012-12-18 0:00
2012-12-03 3:37
2012-12-02 13:29 Ayan Halder
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=50CFAB0B.4000305@redhat.com \
--to=devel@acpica.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 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.