From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jon Hunter Subject: Re: [PATCH V2 13/14] dt-bindings: arm-gic: Add documentation for Tegra210 AGIC Date: Wed, 11 May 2016 20:49:31 +0100 Message-ID: <57338CCB.2080805@nvidia.com> References: <20160427173810.GC7359@leverpostej> <5721C597.1010105@nvidia.com> <20160428095525.GB21145@leverpostej> <572C56A6.7020408@nvidia.com> <573358F9.6000108@nvidia.com> <57335AD3.7070109@nvidia.com> <57336397.4000401@nvidia.com> <20160511172823.GC18829@leverpostej> Mime-Version: 1.0 Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20160511172823.GC18829@leverpostej> Sender: linux-kernel-owner@vger.kernel.org To: Mark Rutland Cc: Rob Herring , Geert Uytterhoeven , Thomas Gleixner , Jason Cooper , Marc Zyngier , Pawel Moll , Ian Campbell , Kumar Gala , Stephen Warren , Thierry Reding , Kevin Hilman , Grygorii Strashko , Lars-Peter Clausen , Linus Walleij , "linux-tegra@vger.kernel.org" , "linux-omap@vger.kernel.org" , "devicetree@vger.kernel.org" , "linux-kernel@vger.kernel.org" List-Id: devicetree@vger.kernel.org On 11/05/16 18:28, Mark Rutland wrote: > On Wed, May 11, 2016 at 05:53:43PM +0100, Jon Hunter wrote: >> Hi Rob, Mark, >> >> On 11/05/16 17:30, Rob Herring wrote: >>> A platform driver for just gic-400 is wrong IMO until we have platform >>> drivers for all interrupt controllers. >> >> Yes, that is fine with me, but can we decide on whether the platform >> driver should match "tegra210-agic" or the early driver should bail-out >> if clocks/power-domains are present? >> >> I am fine with either, but I think that Rob prefers the tegra210-agic >> compat string and Mark prefers to bail-out of the early driver if >> clocks/power-domains are present. > > If anything, I wasn't too keen on bailing out becuase of those > properties, as I mentioned for the case of a root interrupt controller. > > I am happy to match the "tegra210-agic" string specifically. Thanks guys. I will stick with tegra210-agic for now. Cheers Jon