From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marc Zyngier Subject: Re: [PATCH v7 13/17] ARM64 / ACPI: Add GICv2 specific ACPI boot support Date: Thu, 22 Jan 2015 14:46:09 +0000 Message-ID: <54C10D31.1090203@arm.com> References: <1421247905-3749-1-git-send-email-hanjun.guo@linaro.org> <1421247905-3749-14-git-send-email-hanjun.guo@linaro.org> <54B8F2E3.80306@arm.com> <54B92245.6080306@arm.com> <54C0F133.8060901@linaro.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Return-path: Received: from foss-mx-na.foss.arm.com ([217.140.108.86]:40998 "EHLO foss-mx-na.foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750953AbbAVOqV (ORCPT ); Thu, 22 Jan 2015 09:46:21 -0500 In-Reply-To: <54C0F133.8060901@linaro.org> Sender: linux-acpi-owner@vger.kernel.org List-Id: linux-acpi@vger.kernel.org To: Hanjun Guo , "grant.likely@linaro.org" Cc: Catalin Marinas , "Rafael J. Wysocki" , Olof Johansson , Arnd Bergmann , Mark Rutland , Will Deacon , Lorenzo Pieralisi , "graeme.gregory@linaro.org" , Sudeep Holla , "jcm@redhat.com" , Jason Cooper , Bjorn Helgaas , Mark Brown , Rob Herring , Robert Richter , Randy Dunlap , Charles Garcia-Tobin , "phoenix.liyi@huawei.com" , Timur Tabi , "suravee.suthikulpanit@amd.com" , "wangyijing@huawei.com" , linux-acpi@vger Hi Hanjun, On 22/01/15 12:46, Hanjun Guo wrote: > Hi Marc, > > We (Tomasz, Suravee and me) are working on supporting stacked domain on > ACPI, and rework GIC ACPI related patch, before we going further, we > need your guidance to see if we are going the right direction. > > - You said that we spread GIC related code every where, so how > about put all the ACPI related GIC init code in one file under > drivers/irqchip/ with name irq-gic-acpi.c? That would certainly be an improvement. > - ACPI only support one GICD for now, so we assume that there > only one gicv2/v3 core domain and every device not using MSI > will refer to that irqdomain in default. That's good enough, provided that nobody comes up with any form of chained interrupt controller (in whatever way that's implemented). ACPI doesn't seem to cater for that anyway. But default domains are only a quick optimization (it is only there to cope with code that didn't know about irq domains at all). What we need is a proper integration of the ACPI namespace in the irq domain code. Being able to lookup a domain by ACPI table, for example (just like irq_find_host returns the domain associated to a DT node). This would ensure that we can reuse most of the existing code (stacked domains, per-device MSI domains [WIP]) without too much effort. Thanks, M. -- Jazz is not dead. It just smells funny...