From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754379AbbB0OUb (ORCPT ); Fri, 27 Feb 2015 09:20:31 -0500 Received: from mail-pa0-f49.google.com ([209.85.220.49]:33831 "EHLO mail-pa0-f49.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751066AbbB0OU3 (ORCPT ); Fri, 27 Feb 2015 09:20:29 -0500 Message-ID: <54F07D0F.7080904@linaro.org> Date: Fri, 27 Feb 2015 22:19:59 +0800 From: Hanjun Guo User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 MIME-Version: 1.0 To: Shannon Zhao , Catalin Marinas , "Rafael J. Wysocki" , Will Deacon , Olof Johansson , Grant Likely CC: Lorenzo Pieralisi , Arnd Bergmann , Mark Rutland , Graeme Gregory , Sudeep Holla , Jon Masters , Marc Zyngier , Mark Brown , Robert Richter , Timur Tabi , Ashwin Chaugule , suravee.suthikulpanit@amd.com, linux-acpi@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, linaro-acpi@lists.linaro.org, Al Stone , Yi Li , Mark Langsdorf , "Huangpeng (Peter)" Subject: Re: [PATCH v9 21/21] ARM64 / ACPI: additions of ACPI documentation for arm64 References: <1424853601-6675-1-git-send-email-hanjun.guo@linaro.org> <1424853601-6675-22-git-send-email-hanjun.guo@linaro.org> <54F05385.2080506@huawei.com> In-Reply-To: <54F05385.2080506@huawei.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Shannon, On 2015年02月27日 19:22, Shannon Zhao wrote: > On 2015/2/25 16:40, Hanjun Guo wrote: >> +Not yet implemented are: >> + >> + -- Section 10: power source and power meter devices >> + >> + -- Section 11: thermal management >> + >> + -- Section 12: embedded controllers interface >> + >> + -- Section 13: SMBus interfaces >> + >> + -- Section 17: NUMA support (prototypes have been submitted for >> + review) >> + >> > > Here at the end of the file. Redundant blank line. > >> +ACPI is also important because hardware and OS vendors have already worked >> +out how to use it to support the general purpose ecosystem. The infrastructure >> +is in place, the bindings are in place, and the process is in place. DT does >> +exactly what we need it to when working with vertically integrated devices, >> +but we don’t have good processes for supporting what the server vendors need. >> +We could potentially get there with DT, but doing so doesn’t buy us anything. >> +ACPI already does what the hardware vendors need, Microsoft won’t collaborate >> +with us on DT, and the hardware vendors would still need to provide two >> +completely separate firmware interface; one for Linux and one for Windows. >> + > > And Here at the end of the file. Redundant blank line. Thanks a lot for the pointer, I will update it :) Regards Hanjun