From mboxrd@z Thu Jan 1 00:00:00 1970 From: Catalin Marinas Subject: Re: [PATCH v5 18/18] Documentation: ACPI for ARM64 Date: Fri, 2 Jan 2015 16:47:51 +0000 Message-ID: References: <1413553034-20956-1-git-send-email-hanjun.guo@linaro.org> <1413553034-20956-19-git-send-email-hanjun.guo@linaro.org> <8fc9550c96a468b3e50d51a37db68a33.squirrel@www.codeaurora.org> <54A3B526.9040903@linaro.org> <20150101200424.GB12770@xora-haswell.xora.org.uk> <54A664AB.3030101@linaro.org> Mime-Version: 1.0 (1.0) Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: Received: from service87.mimecast.com ([91.220.42.44]:36499 "EHLO service87.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750801AbbABQrz convert rfc822-to-8bit (ORCPT ); Fri, 2 Jan 2015 11:47:55 -0500 In-Reply-To: <54A664AB.3030101@linaro.org> Sender: linux-acpi-owner@vger.kernel.org List-Id: linux-acpi@vger.kernel.org To: Hanjun Guo Cc: Graeme Gregory , "ashwinc@codeaurora.org" , "rjw@rjwysocki.net" , Mark Rutland , "olof@lixom.net" , "grant.likely@linaro.org" , Will Deacon , "linaro-acpi@lists.linaro.org" , Liviu Dudau , "lv.zheng@intel.com" , "robh@kernel.org" , Lorenzo Pieralisi , "al.stone@linaro.org" , "daniel.lezcano@linaro.org" , "robert.moore@intel.com" , "linux-acpi@vger.kernel.org" , Charles Garcia-Tobin , "rric@kernel.org" , "jason@lakedaemon.net" , arnd@arndb.de On 2 Jan 2015, at 09:28, Hanjun Guo wrote: >>> On 2015=E5=B9=B401=E6=9C=8802=E6=97=A5 04:04, Graeme Gregory wrote: >>>> On Wed, Dec 31, 2014 at 04:34:46PM +0800, Hanjun Guo wrote: >>>> On 2014=E5=B9=B412=E6=9C=8831=E6=97=A5 04:13, ashwinc@codeaurora.o= rg wrote: >>>> Hi Hanjun, >>>>=20 >>>> Overall the document looks good to us. Some minor clarifications b= elow. >>>>=20 >>>>> ---------- Forwarded message ---------- >>>>> From: Graeme Gregory >>>>>=20 >>>>> Add documentation for the guidelines of how to use ACPI >>>>> on ARM64. >>>>>=20 >>>>> Signed-off-by: Graeme Gregory >>>>> Signed-off-by: Al Stone >>>>> Signed-off-by: Hanjun Guo >>>>> --- >>>>> Documentation/arm64/arm-acpi.txt | 323 >>>>> ++++++++++++++++++++++++++++++++++++++ >>>>> 1 file changed, 323 insertions(+) >>>>> create mode 100644 Documentation/arm64/arm-acpi.txt >>>>=20 >>>> [..] >>>>=20 >>>>> +Relationship with Device Tree >>>>> +----------------------------- >>>>=20 >>>> [..] >>>>=20 >>>>> +When booting using ACPI tables, the /chosen node in DT will stil= l be >>>>> parsed >>>>> +to extract the kernel command line and initrd path. No other se= ction of >>>>> the >>>>> +DT will be used. >>>>=20 >>>> Is this still true? >>>=20 >>> No, we can booting the ACPI system in EFI stub without dtb. Catalin >>> also pointed out this issue, I will remove this paragraph. >>=20 >> The paragraph is still correct, the /chosen node is always present e= ven >> if nothing else is. >=20 > Sorry for the confusing, I mean no dtb needed for the command line if > ACPI tables are available. >=20 > efi will create a empty dtb if no dtb found, and add the cmd line int= o > the new created dtb, I'm just wondering, can we remove the limitation > for passing the cmd line in /chosen node in the future? My point is that on an ACPI based system, we don't really care how EFI_= STUB passes the command line to the rest of the kernel. Since UEFI doesn't need to = know about such detail and since ACPI is only supported with EFI_STUB, we don't ne= ed to mention the chosen node in this document.=20 At some point we may even change the way EFI_STUB passes the command li= ne to the=20 kernel but this is still irrelevant to ACPI.=20 Catalin -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" i= n the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html