linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: charles.garcia-tobin@arm.com (Charles Garcia-Tobin)
To: linux-arm-kernel@lists.infradead.org
Subject: [Linaro-acpi] [RFC] ACPI on arm64 TODO List
Date: Wed, 17 Dec 2014 13:43:31 -0000	[thread overview]
Message-ID: <000001d019ff$734ee6d0$59ecb470$@arm.com> (raw)
In-Reply-To: <5490C83A.2080600@linaro.org>

> -----Original Message-----
> From: linaro-acpi-bounces at lists.linaro.org [mailto:linaro-acpi-
> bounces at lists.linaro.org] On Behalf Of Al Stone
> Sent: 17 December 2014 00:03
> To: Catalin Marinas; Arnd Bergmann
> Cc: linaro-acpi at lists.linaro.org; Rafael J. Wysocki; ACPI Devel Mailing
> List; Olof Johansson; linux-arm-kernel at lists.infradead.org
> Subject: Re: [Linaro-acpi] [RFC] ACPI on arm64 TODO List
> 
> On 12/16/2014 08:27 AM, Catalin Marinas wrote:
> > On Tue, Dec 16, 2014 at 11:27:48AM +0000, Arnd Bergmann wrote:
> >> On Monday 15 December 2014 19:18:16 Al Stone wrote:
> >>> TODO List for ACPI on arm64:
> >>> ============================
> [snip..]
> >>> 4. Set clear expectations for those providing ACPI for use with
> Linux
> >>>    * Problem:
> >>>      * Hardware/Firmware vendors can and will create ACPI tables
> that
> >>>        cannot be used by Linux without some guidance
> >>>      * Kernel developers cannot determine whether the kernel or
> firmware
> >>>        is broken without knowing what the firmware should do
> >>>    * Solution: document the expectations, and iterate as needed.
> >>>      Enforce when we must.
> >>>    * Status: initial kernel text available; AMD has offered to make
> >>>      their guidance document generic; firmware summit planned for
> >>>      deeper discussions.
> >>
> [snip...]
> >
> > Another example is SMP booting. The ACPI 5.1 spec mentions the
> parking
> > protocol but I can't find a reference to the latest document. In the
> > meantime, we stick to PSCI.
> 
> Hrm.  A bug in the spec.
> 
> Every external document mentioned in the ACPI spec is supposed to have
> a link that will eventually get you to the source document.  All links
> in the spec should point here http://www.uefi.org/acpi which in turn
> has links to the authoritative original documents.  However, it looks
> like the parking protocol document pointed to (the "Multiprocessor
> Startup" link) may not be the most recent version.  The reference in
> the spec to the protocol (Table 5-61, Section 5.2.12.14)) also appears
> to be useless (it points to http://infocenter.arm.com/help/index.jsp
> which doesn't have the document either).  I've filed a change request
> with ASWG to fix this.

I also raised both of these a while back, I expect the next errata release
to correct this.

> 
> That being said, the early systems still don't provide PSCI.  They will
> at some point in the future, but not now.  Regardless, I think it's
> reasonable for us to say that if you want ACPI support, PSCI must be
> used for secondary CPU startup.  People can hack something up to get
> the parking protocol to work on development branches if they want, but
> I personally see no need to get that into the kernel -- and it needs
> to be said explicitly in arm-acpi.txt.
> 
> 
> --
> ciao,
> al
> -----------------------------------
> Al Stone
> Software Engineer
> Linaro Enterprise Group
> al.stone at linaro.org
> -----------------------------------
> 
> _______________________________________________
> Linaro-acpi mailing list
> Linaro-acpi at lists.linaro.org
> http://lists.linaro.org/mailman/listinfo/linaro-acpi

  parent reply	other threads:[~2014-12-17 13:43 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-16  2:18 [RFC] ACPI on arm64 TODO List Al Stone
2014-12-16 11:27 ` Arnd Bergmann
2014-12-16 15:27   ` Catalin Marinas
2014-12-17  0:03     ` Al Stone
2014-12-17  9:25       ` Catalin Marinas
2014-12-18  4:57         ` Jon Masters
2014-12-18  9:55           ` Catalin Marinas
2014-12-17 13:43       ` Charles Garcia-Tobin [this message]
2014-12-16 15:48   ` [Linaro-acpi] " Mark Rutland
2014-12-17  0:37     ` Al Stone
2014-12-17  9:08       ` G Gregory
2014-12-17 16:02       ` Mark Rutland
2014-12-17 16:52         ` Hurwitz, Sherry
2014-12-17 18:14       ` Lorenzo Pieralisi
2014-12-18  5:04       ` Jon Masters
2014-12-18 14:36         ` Jon Masters
2014-12-16 22:55   ` Al Stone
2014-12-17 17:31     ` Catalin Marinas
2014-12-17 22:26   ` Grant Likely
2015-01-10 14:44     ` Grant Likely
2015-01-12 10:21       ` Arnd Bergmann
2015-01-12 12:00         ` Grant Likely
2015-01-12 19:40           ` [Linaro-acpi] " Arnd Bergmann
2015-01-13 17:22             ` Grant Likely
2015-01-14  0:26               ` Al Stone
2015-01-15  4:07                 ` Hanjun Guo
2015-01-15 17:15                   ` Arnd Bergmann
2015-01-15 17:19                 ` Arnd Bergmann
2015-01-12 14:23       ` Pavel Machek
2015-01-12 14:41         ` Grant Likely
2015-01-12 19:39           ` Pavel Machek
2015-01-12 19:55             ` Arnd Bergmann
2015-01-13 14:12             ` Grant Likely
2015-01-14  1:21             ` Al Stone
2015-01-15 17:45               ` [Linaro-acpi] " Linda Knippers
2015-01-13 17:02         ` Grant Likely
2015-01-05 20:52 ` Pavel Machek
2015-01-06 11:53   ` Catalin Marinas

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='000001d019ff$734ee6d0$59ecb470$@arm.com' \
    --to=charles.garcia-tobin@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).