Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751997Ab3FJHkK (ORCPT ); Mon, 10 Jun 2013 03:40:10 -0400 Received: from mail-ob0-f180.google.com ([209.85.214.180]:61737 "EHLO mail-ob0-f180.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751872Ab3FJHkI (ORCPT ); Mon, 10 Jun 2013 03:40:08 -0400 MIME-Version: 1.0 In-Reply-To: <1370825362-11145-11-git-send-email-grant.likely@linaro.org> References: <1370825362-11145-1-git-send-email-grant.likely@linaro.org> <1370825362-11145-11-git-send-email-grant.likely@linaro.org> Date: Mon, 10 Jun 2013 09:40:08 +0200 Message-ID: Subject: Re: [RFC 10/10] irqchip: Make versatile fpga irq driver a generic chip From: Linus Walleij To: Grant Likely Cc: "linux-kernel@vger.kernel.org" , Arnd Bergmann , Benjamin Herrenschmidt , Thomas Gleixner , "linuxppc-dev@lists.ozlabs.org list" , Russell King Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1040 Lines: 26 On Mon, Jun 10, 2013 at 2:49 AM, Grant Likely wrote: > This is an RFC patch to convert the versatile FPGA irq controller driver > to use generic irq chip. It builds on the series that extends the > generic chip code to allow a linear irq domain to contain one or more > generic irq chips so that each interrupt controller doesn't need to hand > code the generic chip setup. > > I've written this as a proof of concept to see if the new generic irq > code does what it needs to. I had to extend it slightly to properly > handle the valid mask used by the versatile FPGA driver. > > Tested on QEMU, but not on real hardware. Is this the same as the one I tested previously? If it need re-testing please push a branch and I'll take it for a spin. Yours. Linus Walleij -- 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/