Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1030359AbcCQUO5 (ORCPT ); Thu, 17 Mar 2016 16:14:57 -0400 Received: from mail.kernel.org ([198.145.29.136]:51105 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933182AbcCQUOy (ORCPT ); Thu, 17 Mar 2016 16:14:54 -0400 MIME-Version: 1.0 In-Reply-To: <1458224359-32665-15-git-send-email-jonathanh@nvidia.com> References: <1458224359-32665-1-git-send-email-jonathanh@nvidia.com> <1458224359-32665-15-git-send-email-jonathanh@nvidia.com> From: Rob Herring Date: Thu, 17 Mar 2016 15:14:30 -0500 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH 14/15] dt-bindings: arm-gic: Drop 'clock-names' from binding document To: Jon Hunter Cc: Thomas Gleixner , Jason Cooper , Marc Zyngier , =?UTF-8?Q?Beno=C3=AEt_Cousson?= , Tony Lindgren , Pawel Moll , Mark Rutland , Ian Campbell , Kumar Gala , Stephen Warren , Thierry Reding , Kevin Hilman , Geert Uytterhoeven , Grygorii Strashko , Lars-Peter Clausen , Linus Walleij , "linux-tegra@vger.kernel.org" , linux-omap , "devicetree@vger.kernel.org" , "linux-kernel@vger.kernel.org" Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1149 Lines: 28 On Thu, Mar 17, 2016 at 9:19 AM, Jon Hunter wrote: > Commit afbbd2338176 ("irqchip/gic: Document optional Clock and Power > Domain properties") documented optional clock and power-dmoain properties > for the ARM GIC. Currently, there are no users of these and for the > Tegra210 Audio GIC (based upon the GIC-400) there are two clocks, a > functional clock and interface clock, that need to be enabled. > > To allow flexibility, drop the 'clock-names' from the GIC binding and > just provide a list of clocks which the driver can parse. It is assumed > that any clocks that are listed, need to be enabled in order to access > the GIC. > > Signed-off-by: Jon Hunter > > --- > > Please note that I am not sure if this will be popular, but I am trying > to come up with a generic way to handle multiple clocks that may be > required for accessing a GIC. It's not. :) We need to specify the number and order of clocks by compatible string at a minimum. Sadly, ARM's GICs are well documented and include clock names, so you can't just make up genericish names either which is probably often the case. Rob