From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757257AbbA2SqJ (ORCPT ); Thu, 29 Jan 2015 13:46:09 -0500 Received: from mx1.redhat.com ([209.132.183.28]:42819 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752168AbbA2SqH (ORCPT ); Thu, 29 Jan 2015 13:46:07 -0500 Message-ID: <54CA7F94.6000305@redhat.com> Date: Thu, 29 Jan 2015 13:44:36 -0500 From: Jon Masters Organization: Red Hat, Inc. User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: Timur Tabi , Ard Biesheuvel CC: Catalin Marinas , Mark Rutland , Rob Herring , "phoenix.liyi@huawei.com" , Robert Richter , "linux-acpi@vger.kernel.org" , Arnd Bergmann , "linaro-acpi@lists.linaro.org" , Marc Zyngier , Will Deacon , Randy Dunlap , "Rafael J. Wysocki" , lkml , "grant.likely@linaro.org" , "wangyijing@huawei.com" , Mark Brown , "hanjun.guo@linaro.org" , Olof Johansson , Bjorn Helgaas , "linux-arm-kernel@lists.infradead.org" , Jason Cooper Subject: Re: [Linaro-acpi] [PATCH v7 04/17] ARM64 / ACPI: Introduce early_param for "acpi" and pass acpi=force to enable ACPI References: <1421247905-3749-1-git-send-email-hanjun.guo@linaro.org> <1421247905-3749-5-git-send-email-hanjun.guo@linaro.org> <20150128181453.GG31752@e104818-lin.cambridge.arm.com> <54C92804.5090806@codeaurora.org> <20150129151956.GF8951@e104818-lin.cambridge.arm.com> <54CA7A42.5080800@codeaurora.org> <54CA7D4A.5090709@codeaurora.org> In-Reply-To: <54CA7D4A.5090709@codeaurora.org> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 01/29/2015 01:34 PM, Timur Tabi wrote: > On 01/29/2015 12:28 PM, Ard Biesheuvel wrote: >> The UEFI stub in the kernel uses the DTB file format (FDT) to pass >> information about the UEFI memory map and system table to the kernel. >> It does so even if there is no device tree that describes the >> platform. In this case, the file only contains a /chosen DT node, and >> nothing else, and it is up to the kernel to figure out that it can ask >> UEFI for a set of ACPI tables that it can use instead to configure the >> system. Otherwise, the /chosen node properties are added to a device >> tree that contains the full platform description. >> >> The problem is that we have to decide how to distinguish a >> conventional device tree DTB from a DTB that only exists to >> communicate the UEFI entry points. > > Ah, that's exactly what I'm seeing. The UEFI stub in our kernel > generates a DTB, and therefore I always need to put acpi=force on our > kernel command line. I expect some of the distros to patch ACPI always enabled. So from my point of view this affects only those wanting to follow upstream. Jon.