Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754576AbbGBWJc (ORCPT ); Thu, 2 Jul 2015 18:09:32 -0400 Received: from www.linutronix.de ([62.245.132.108]:44912 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754308AbbGBWJH (ORCPT ); Thu, 2 Jul 2015 18:09:07 -0400 Date: Fri, 3 Jul 2015 00:08:27 +0200 (CEST) From: Thomas Gleixner To: Paul Osmialowski cc: Arnd Bergmann , linux-arm-kernel@lists.infradead.org, Greg Kroah-Hartman , Ian Campbell , Jiri Slaby , Kumar Gala , Linus Walleij , Mark Rutland , Michael Turquette , Pawel Moll , Rob Herring , Russell King , Stephen Boyd , Vinod Koul , linux-kernel@vger.kernel.org, linux-clk@vger.kernel.org, linux-gpio@vger.kernel.org, linux-serial@vger.kernel.org, devicetree@vger.kernel.org, dmaengine@vger.kernel.org, Nicolas Pitre , Sergei Poselenov , Paul Bolle , Jingchang Lu , Yuri Tikhonov , Rob Herring , Geert Uytterhoeven , Uwe Kleine-Koenig , Alexander Potashev , Frank Li , Anson Huang Subject: Re: [PATCH v2 3/9] arm: twr-k70f120m: clock driver for Kinetis SoC In-Reply-To: Message-ID: References: <1435667250-28299-1-git-send-email-pawelo@king.net.pl> <1861313.aMcV1xHCIq@wuerfel> User-Agent: Alpine 2.11 (DEB 23 2013-08-11) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Linutronix-Spam-Score: -1.0 X-Linutronix-Spam-Level: - X-Linutronix-Spam-Status: No , -1.0 points, 5.0 required, ALL_TRUSTED=-1,SHORTCIRCUIT=-0.0001 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1016 Lines: 24 On Thu, 2 Jul 2015, Paul Osmialowski wrote: > On Thu, 2 Jul 2015, Arnd Bergmann wrote: > > > I wonder if you could move out the fixed rate clocks into their own > > nodes. Are they actually controlled by the same block? If they are > > just fixed, you can use the normal binding for fixed rate clocks > > and only describe the clocks that are related to the driver. > > In my view having these clocks grouped together looks more convincing. After > all, they all share the same I/O regs in order to read configuration. The fact that they share a register is not making them a group. That's just a HW design decision and you need to deal with that by protecting the register access, but not by trying to group them artificially at the functional level. Thanks, tglx -- 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/