From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753356AbbAELF5 (ORCPT ); Mon, 5 Jan 2015 06:05:57 -0500 Received: from foss-mx-na.foss.arm.com ([217.140.108.86]:55184 "EHLO foss-mx-na.foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752827AbbAELF4 (ORCPT ); Mon, 5 Jan 2015 06:05:56 -0500 Date: Mon, 5 Jan 2015 11:05:33 +0000 From: Catalin Marinas To: Hanjun Guo Cc: "Rafael J. Wysocki" , Mark Rutland , Olof Johansson , "grant.likely@linaro.org" , Will Deacon , "graeme.gregory@linaro.org" , Arnd Bergmann , Sudeep Holla , "jcm@redhat.com" , Jason Cooper , Marc Zyngier , Bjorn Helgaas , Daniel Lezcano , Mark Brown , Rob Herring , Robert Richter , Lv Zheng , Robert Moore , Lorenzo Pieralisi , Liviu Dudau , Randy Dunlap , Charles Garcia-Tobin , "Kangkang.Shen@huawei.com" , "linux-acpi@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" , "linux-kernel@vger.kernel.org" , "linaro-acpi@lists.linaro.org" , Al Stone Subject: Re: [PATCH v5 18/18] Documentation: ACPI for ARM64 Message-ID: <20150105110533.GA14967@e104818-lin.cambridge.arm.com> References: <1413553034-20956-1-git-send-email-hanjun.guo@linaro.org> <1413553034-20956-19-git-send-email-hanjun.guo@linaro.org> <20141224171815.GD13399@e104818-lin.cambridge.arm.com> <54A90A4C.60908@linaro.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <54A90A4C.60908@linaro.org> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sun, Jan 04, 2015 at 09:39:24AM +0000, Hanjun Guo wrote: > On 2014年12月25日 01:18, Catalin Marinas wrote: > [...] > > > > In addition to the above and _DSD requirements/banning, I would also add > > some clear statements around: > > > > _OSC: only global/published capabilities are allowed. For > > device-specific _OSC we need a process or maybe we can ban them entirely > > and rely on _DSD once we clarify the process. > > > > _OSI: firmware must not check for certain _OSI strings. Here I'm not > > sure what we would have to do for ARM Linux. Reporting "Windows" does > > not make any sense but not reporting anything can, as Matthew Garrett > > pointed out, can be interpreted by firmware as "Linux". In addition to > > any statements in this document, I suggest you patch > > drivers/acpi/acpica/utosi.c accordingly, maybe report "Linux" for ARM > > and print a kernel warning so that we notice earlier. > > > > ACPI_OS_NAME: this is globally defined as "Microsoft Windows NT". It > > doesn't make much sense in the ARM context. Could we change it to > > "Linux" when CONFIG_ARM64? > > We will work on this both on ASWG and linux ACPI driver side, as Dong > and Charles pointed out, _OSI things can be solved in ACPI spec, when > that is done, we can modify the kernel driver to fix the problems above. Which driver? What about ACPI_OS_NAME? Would you suggest it is fine to report "Microsoft Windows NT" on an ARM system? That _OS_ not _OSI. -- Catalin