From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753599AbbGXI2H (ORCPT ); Fri, 24 Jul 2015 04:28:07 -0400 Received: from mail-pd0-f176.google.com ([209.85.192.176]:36721 "EHLO mail-pd0-f176.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752057AbbGXI2D (ORCPT ); Fri, 24 Jul 2015 04:28:03 -0400 Message-ID: <55B1F708.3010804@linaro.org> Date: Fri, 24 Jul 2015 16:27:52 +0800 From: Hanjun Guo User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: Marc Zyngier , Thomas Gleixner , Jiang Liu , Jason Cooper CC: linux-acpi@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, Lorenzo Pieralisi , Tomasz Nowicki , "Rafael J. Wysocki" , Suravee Suthikulpanit , Graeme Gregory Subject: Re: [PATCH v2 0/7] Making the generic ACPI GSI layer irqdomain aware References: <1437656713-9677-1-git-send-email-marc.zyngier@arm.com> In-Reply-To: <1437656713-9677-1-git-send-email-marc.zyngier@arm.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Marc, On 07/23/2015 09:05 PM, Marc Zyngier wrote: > The irqdomain code is not entierely really ACPI friendly, as it has > some built-in knowledge of the device-tree. Nothing too harmful, but > enough to scare the ARM ACPI developpers which end up with their own > version of the square wheel. > > This small patch series adapt the irqdomain code to remove the hurdles > that prevent the full blown irqdomain subsystem to be used on ACPI, > creates an interface between the GSI layer and the irqdomain, and as > an example, convert the ARM GIC ACPI support to use irqdomains as > originally intended. > > Overall, this gives us a way to use irqdomains on both DT and ACPI > enabled platforms, having very little changes made to the actual > drivers (other than the probing infrastructure). Because we keep the > flow of information between the various layers identical between ACPI > and DT, we immediately benefit from the existing infrastructure. > > I'd really like to hear what people think of that approach, as it > looks to me a lot simpler than the other approaches currently put on > the list. The "convert the GSI information to be DT friendly" is > admitedly not very pretty, but I see it as a stepping stone towards > unifying the two structures. > > This has been test-booted on Juno, is based on my irq/ncpi-msi-v3 > branch, and available at: > > git://git.kernel.org/pub/scm/linux/kernel/git/maz/arm-platforms.git irq/gsi-irq-domain-v2 Pulled and rebased my self-probing and GICv3 ACPI support patches on top of it, tested on FVP and QEMU, booted OK, for this patch set, Tested-by: Hanjun Guo I will sync with Suravee to prepare a single patch for ACPI self-probing, GICv2m and GICv3 support. Thank you for putting thing together! Hanjun