From mboxrd@z Thu Jan 1 00:00:00 1970 From: mark.rutland@arm.com (Mark Rutland) Date: Mon, 26 Jan 2015 13:40:53 +0000 Subject: [PATCH RESEND v3 0/3] irqchip: vf610-mscm: add support for MSCM interrupt router In-Reply-To: <36990c90fa3d2ee0849227f31cbafb54@agner.ch> References: <1421309046-22452-1-git-send-email-stefan@agner.ch> <36990c90fa3d2ee0849227f31cbafb54@agner.ch> Message-ID: <20150126134053.GH23313@leverpostej> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org [...] > > What about the DT bindings? I'm relucant to pick that up w/o acks from > > the DT folks. > > The bindings are straight forward interrupt-controller bindings, since > it uses the hierarchic irq domain stuff. The only uncommon thing is that > I also added "syscon" as compatible, since the module has functionality > which might be required by other drivers (e.g. register to generate > CPU2CPU interrupt or processor personality information). I'd expect the CPU2CPU interrupt handling to be part of the interrupt controller driver, so I don't see why that would require "syscon". What exactly do you mean by "processor personality information"? Mark. From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark Rutland Subject: Re: [PATCH RESEND v3 0/3] irqchip: vf610-mscm: add support for MSCM interrupt router Date: Mon, 26 Jan 2015 13:40:53 +0000 Message-ID: <20150126134053.GH23313@leverpostej> References: <1421309046-22452-1-git-send-email-stefan@agner.ch> <36990c90fa3d2ee0849227f31cbafb54@agner.ch> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <36990c90fa3d2ee0849227f31cbafb54-XLVq0VzYD2Y@public.gmane.org> Sender: devicetree-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Stefan Agner Cc: Thomas Gleixner , Marc Zyngier , "jason-NLaQJdtUoK4Be96aLqz0jA@public.gmane.org" , "u.kleine-koenig-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org" , "shawn.guo-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org" , "kernel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org" , "arnd-r2nGTMty4D4@public.gmane.org" , "robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org" , Pawel Moll , "ijc+devicetree-KcIKpvwj1kUDXYZnReoRVg@public.gmane.org" , "galak-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org" , "linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org" , "devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" , "linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org" , "linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" List-Id: devicetree@vger.kernel.org [...] > > What about the DT bindings? I'm relucant to pick that up w/o acks from > > the DT folks. > > The bindings are straight forward interrupt-controller bindings, since > it uses the hierarchic irq domain stuff. The only uncommon thing is that > I also added "syscon" as compatible, since the module has functionality > which might be required by other drivers (e.g. register to generate > CPU2CPU interrupt or processor personality information). I'd expect the CPU2CPU interrupt handling to be part of the interrupt controller driver, so I don't see why that would require "syscon". What exactly do you mean by "processor personality information"? Mark. -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755262AbbAZNlW (ORCPT ); Mon, 26 Jan 2015 08:41:22 -0500 Received: from foss-mx-na.foss.arm.com ([217.140.108.86]:43156 "EHLO foss-mx-na.foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752292AbbAZNlT (ORCPT ); Mon, 26 Jan 2015 08:41:19 -0500 Date: Mon, 26 Jan 2015 13:40:53 +0000 From: Mark Rutland To: Stefan Agner Cc: Thomas Gleixner , Marc Zyngier , "jason@lakedaemon.net" , "u.kleine-koenig@pengutronix.de" , "shawn.guo@linaro.org" , "kernel@pengutronix.de" , "arnd@arndb.de" , "robh+dt@kernel.org" , Pawel Moll , "ijc+devicetree@hellion.org.uk" , "galak@codeaurora.org" , "linux@arm.linux.org.uk" , "devicetree@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" , "linux-kernel@vger.kernel.org" Subject: Re: [PATCH RESEND v3 0/3] irqchip: vf610-mscm: add support for MSCM interrupt router Message-ID: <20150126134053.GH23313@leverpostej> References: <1421309046-22452-1-git-send-email-stefan@agner.ch> <36990c90fa3d2ee0849227f31cbafb54@agner.ch> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <36990c90fa3d2ee0849227f31cbafb54@agner.ch> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org [...] > > What about the DT bindings? I'm relucant to pick that up w/o acks from > > the DT folks. > > The bindings are straight forward interrupt-controller bindings, since > it uses the hierarchic irq domain stuff. The only uncommon thing is that > I also added "syscon" as compatible, since the module has functionality > which might be required by other drivers (e.g. register to generate > CPU2CPU interrupt or processor personality information). I'd expect the CPU2CPU interrupt handling to be part of the interrupt controller driver, so I don't see why that would require "syscon". What exactly do you mean by "processor personality information"? Mark.