From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753148AbbB0LOA (ORCPT ); Fri, 27 Feb 2015 06:14:00 -0500 Received: from szxga03-in.huawei.com ([119.145.14.66]:11241 "EHLO szxga03-in.huawei.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750837AbbB0LN5 (ORCPT ); Fri, 27 Feb 2015 06:13:57 -0500 Message-ID: <54F05162.7010609@huawei.com> Date: Fri, 27 Feb 2015 19:13:38 +0800 From: Shannon Zhao User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: Hanjun Guo , Catalin Marinas , "Rafael J. Wysocki" , "Will Deacon" , Olof Johansson , Grant Likely CC: Mark Rutland , Ashwin Chaugule , Lorenzo Pieralisi , Robert Richter , Arnd Bergmann , "Graeme Gregory" , , "Marc Zyngier" , Jon Masters , Timur Tabi , , Al Stone , , Mark Brown , , Sudeep Holla , "Huangpeng (Peter)" , Subject: Re: [PATCH v9 20/21] Documentation: ACPI for ARM64 References: <1424853601-6675-1-git-send-email-hanjun.guo@linaro.org> <1424853601-6675-21-git-send-email-hanjun.guo@linaro.org> <54F04C92.6010206@huawei.com> In-Reply-To: <54F04C92.6010206@huawei.com> Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit X-Originating-IP: [10.177.16.142] X-CFilter-Loop: Reflected X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020203.54F05173.012E,ss=1,re=0.001,recu=0.000,reip=0.000,cl=1,cld=1,fgs=0, ip=0.0.0.0, so=2013-05-26 15:14:31, dmn=2013-03-21 17:37:32 X-Mirapoint-Loop-Id: c639e20a6a28d18ed99c7df678a78fb7 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2015/2/27 18:53, Shannon Zhao wrote: > On 2015/2/25 16:40, Hanjun Guo wrote: >> From: Graeme Gregory >> >> Add documentation for the guidelines of how to use ACPI >> on ARM64. >> >> Reviewed-by: Suravee Suthikulpanit >> Reviewed-by: Yi Li >> Reviewed-by: Mark Langsdorf >> Reviewed-by: Ashwin Chaugule >> Acked-by: Robert Richter >> Signed-off-by: Graeme Gregory >> Signed-off-by: Al Stone >> Signed-off-by: Hanjun Guo >> --- >> Documentation/arm64/arm-acpi.txt | 506 +++++++++++++++++++++++++++++++++++++++ >> 1 file changed, 506 insertions(+) >> create mode 100644 Documentation/arm64/arm-acpi.txt >> >> diff --git a/Documentation/arm64/arm-acpi.txt b/Documentation/arm64/arm-acpi.txt >> new file mode 100644 >> index 0000000..24cf832 >> --- /dev/null >> +++ b/Documentation/arm64/arm-acpi.txt >> @@ -0,0 +1,506 @@ >> +ACPI on ARMv8 Servers >> +--------------------- >> +ACPI can be used for ARMv8 general purpose servers designed to follow >> +the ARM SBSA (Server Base System Architecture) [0] and SBBR (Server >> +Base Boot Requirements) [1] specifications. Please note that the SBBR >> +can be retrieved simply by visiting [1], but the SBSA is currently only >> +available to those with an ARM login due to ARM IP licensing concerns. >> + >> +The ARMv8 kernel implements the reduced hardware model of ACPI version >> +5.1 or later. Links to the specification and all external documents >> +it refers to are managed by the UEFI Forum. The specification is >> +available at http://www.uefi.org/specifications and documents referenced >> +by the specification can be found via http://www.uefi.org/acpi. >> + >> +If an ARMv8 system does not meet the requirements of the SBSA and SBBR, >> +or cannot be described using the mechanisms defined in the required ACPI >> +specifications, then ACPI may not be a good fit for the hardware. >> + >> +While the documents mentioned above set out the requirements for building >> +industry-standard ARMv8 servers, they also apply to more than one operating >> +system. The purpose of this document is to describe the interaction between >> +ACPI and Linux only, on an ARMv8 system -- that is, what Linux expects of >> +ACPI and what ACPI can expect of Linux. >> + >> + > > Here. Two blank lines. > >> +Why ACPI on ARM? > > not here. ignore this :-) -- Thanks, Shannon