From: Al Stone <al.stone@linaro.org>
To: Will Deacon <will.deacon@arm.com>, ahs3@redhat.com
Cc: linux-doc@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
linaro-kernel@lists.linaro.org, patches@linaro.org,
Catalin Marinas <catalin.marinas@arm.com>,
linaro-acpi@lists.linaro.org
Subject: Re: [PATCH v3] ARM64: ACPI: Update documentation for latest specification version
Date: Fri, 8 Apr 2016 08:28:08 -0600 [thread overview]
Message-ID: <5707BFF8.3030704@linaro.org> (raw)
In-Reply-To: <20160408131208.GE23750@arm.com>
On 04/08/2016 07:12 AM, Will Deacon wrote:
> On Thu, Apr 07, 2016 at 03:50:55PM -0600, Al Stone wrote:
>> On 03/28/2016 06:06 PM, Al Stone wrote:
>>> The ACPI 6.1 specification was recently released at the end of January
>>> 2016, but the arm64 kernel documentation for the use of ACPI was written
>>> for the 5.1 version of the spec. There were significant additions to the
>>> spec that had not yet been mentioned -- for example, the 6.0 mechanisms
>>> added to make it easier to define processors and low power idle states,
>>> as well as the 6.1 addition allowing regular interrupts (not just from
>>> GPIO) be used to signal ACPI general purpose events.
>>>
>>> This patch reflects going back through and examining the specs in detail
>>> and updating content appropriately. Whilst there, a few odds and ends of
>>> typos were caught as well. This brings the documentation up to date with
>>> ACPI 6.1 for arm64.
>>>
>>> Changes for v3:
>>> -- Clarify use of _LPI/_RDI (Vikas Sajjan)
>>> -- Whitespace cleanup as pointed out by checkpatch
>>>
>>> Changes for v2:
>>> -- Clean up white space (Harb Abdulhahmid)
>>> -- Clarification on _CCA usage (Harb Abdulhamid)
>>> -- IORT moved to required from recommended (Hanjun Guo)
>>> -- Clarify IORT description (Hanjun Guo)
>>>
>>> Signed-off-by: Al Stone <al.stone@linaro.org>
>>> Cc: Catalin Marinas <catalin.marinas@arm.com>
>>> Cc: Will Deacon <will.deacon@arm.com>
>>> Cc: Jonathan Corbet <corbet@lwn.net>
>>> ---
>>> Documentation/arm64/acpi_object_usage.txt | 446 ++++++++++++++++++++++--------
>>> Documentation/arm64/arm-acpi.txt | 28 +-
>>> 2 files changed, 357 insertions(+), 117 deletions(-)
>>> [snip...]
>>
>> Ping? Any further comments or is this good to go?
>
> It would be nice to see an ack from some other ACPI people, if that's
> possible. Which tree were you planning to merge this through?
>
> Will
>
Agreed. I was hoping the ping would elicit some of that.
I assumed this would go through the arm64 tree since it's pretty specific
to the architecture.
--
ciao,
al
-----------------------------------
Al Stone
Software Engineer
Linaro Enterprise Group
al.stone@linaro.org
-----------------------------------
next prev parent reply other threads:[~2016-04-08 14:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-29 0:06 Al Stone
2016-04-07 21:50 ` Al Stone
2016-04-08 13:12 ` Will Deacon
2016-04-08 14:28 ` Al Stone [this message]
2016-04-11 2:12 ` Hanjun Guo
2016-04-15 14:37 ` Lorenzo Pieralisi
2016-04-15 16:41 ` Al Stone
2016-04-15 17:47 ` Lorenzo Pieralisi
2016-04-15 17:54 ` Al Stone
2016-04-18 9:07 ` Lorenzo Pieralisi
2016-04-15 21:35 ` Jonathan Corbet
2016-04-15 21:58 ` Al Stone
2016-04-18 2:58 ` Jon Masters
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=5707BFF8.3030704@linaro.org \
--to=al.stone@linaro.org \
--cc=ahs3@redhat.com \
--cc=catalin.marinas@arm.com \
--cc=corbet@lwn.net \
--cc=linaro-acpi@lists.linaro.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@linaro.org \
--cc=will.deacon@arm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®