Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753131AbbEZPT3 (ORCPT ); Tue, 26 May 2015 11:19:29 -0400 Received: from [217.140.101.70] ([217.140.101.70]:50232 "EHLO foss.arm.com" rhost-flags-FAIL-FAIL-OK-OK) by vger.kernel.org with ESMTP id S1752927AbbEZPTY (ORCPT ); Tue, 26 May 2015 11:19:24 -0400 Date: Tue, 26 May 2015 16:18:42 +0100 From: Will Deacon To: Ashwin Chaugule Cc: "fu.wei@linaro.org" , "suravee.suthikulpanit@amd.com" , "linaro-acpi@lists.linaro.org" , "linux-watchdog@vger.kernel.org" , "devicetree@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "linux-doc@vger.kernel.org" , "tekkamanninja@gmail.com" , "graeme.gregory@linaro.org" , "al.stone@linaro.org" , "hanjun.guo@linaro.org" , "timur@codeaurora.org" , "arnd@arndb.de" , "linux@roeck-us.net" , "vgandhi@codeaurora.org" , "wim@iguana.be" , "jcm@redhat.com" , "leo.duran@amd.com" , "corbet@lwn.net" , Mark Rutland , Catalin Marinas Subject: Re: [PATCH v3 6/6] ACPI: import watchdog info of GTDT into platform device Message-ID: <20150526151842.GP1565@arm.com> References: <=fu.wei@linaro.org> <1432548193-19569-1-git-send-email-fu.wei@linaro.org> <1432548193-19569-7-git-send-email-fu.wei@linaro.org> <20150526122858.GJ1565@arm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: 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 Content-Length: 2795 Lines: 63 On Tue, May 26, 2015 at 04:02:56PM +0100, Ashwin Chaugule wrote: > On 26 May 2015 at 08:28, Will Deacon wrote: > > On Mon, May 25, 2015 at 11:03:13AM +0100, fu.wei@linaro.org wrote: > >> From: Fu Wei > >> > >> Parse SBSA Generic Watchdog Structure in GTDT table of ACPI, > >> and create a platform device with that information. > >> This platform device can be used by the ARM SBSA Generic > >> Watchdog driver. > >> > >> Tested-by: Suravee Suthikulpanit > >> Tested-by: Timur Tabi > >> Signed-off-by: Fu Wei > >> --- > >> arch/arm64/kernel/acpi.c | 145 +++++++++++++++++++++++++++++++++++++++++++++++ > >> 1 file changed, 145 insertions(+) > > > > Why does this all need to be under arch/arm64? The GTDT really isn't > > architecture-specific, so I'd *much* rather it was parsed in the driver code > > itself, like we already do for the architected timer. The GIC is an > > exception because it's in the MADT, which we need to parse in the arch code > > to configure SMP properly. > > I'm not really against refactoring the code. But the GTDT looks quite > specific to ARM.. > > ---8<---- > 5.2.24 Generic Timer Description Table (GTDT) > This section describes the format of the Generic Timer Description > Table (GTDT), which provides > OSPM with information about a system’s Generic Timers configuration. > The Generic Timer (GT) is > a standard timer interface implemented on ARM processor-based systems. > The GT hardware > specification can be found at Links to ACPI-Related Documents > (http://uefi.org/acpi) under the > heading ARM Architecture. The GTDT provides OSPM with information > about a system's GT > interrupt configurations, for both per-processor timers, and platform > (memory-mapped) timers. > The GT specification defines the following per-processor timers: > • Secure privilege level 1 (EL1) timer, > • Non-Secure EL1 timer, > • Non-Secure privilege level 2 (EL2) timer, > • Virtual timer, > and the following Platform (memory-mapped) timers. > • GT Block > • Server Base System Architecture (SBSA) Generic Watchdog > ---8<---- Sure, the device it describes may only ever exist on ARM systems, but by that logic then we should be moving lots of drivers back under arch/arm[64]. The ARM architecture says precisely *nothing* about ACPI, so we should try to keep arch/arm64/kernel/acpi.c to a minimum and not shovel all sorts of table conversion code in there for random peripherals. Will -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/