From mboxrd@z Thu Jan 1 00:00:00 1970 From: Arnd Bergmann Subject: Re: [PATCH v2 3/9] arm: twr-k70f120m: clock driver for Kinetis SoC Date: Sat, 04 Jul 2015 21:54:12 +0200 Message-ID: <2009463.YLtdMegFel@wuerfel> References: <1435667250-28299-1-git-send-email-pawelo@king.net.pl> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=m.gmane.org@lists.infradead.org To: linux-arm-kernel@lists.infradead.org Cc: Mark Rutland , Nicolas Pitre , Linus Walleij , Rob Herring , Alexander Potashev , Frank Li , Jiri Slaby , linux-clk@vger.kernel.org, Russell King , Vinod Koul , Geert Uytterhoeven , linux-serial@vger.kernel.org, Uwe Kleine-Koenig , Anson Huang , Michael Turquette , devicetree@vger.kernel.org, Paul Osmialowski , Pawel Moll , Ian Campbell , Kumar Gala , Yuri Tikhonov , linux-gpio@vger.kernel.org, Rob Herring , Thomas Gleixner List-Id: linux-gpio@vger.kernel.org On Friday 03 July 2015 00:08:27 Thomas Gleixner wrote: > 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. I'd disagree with that: The clock controller is the device that owns the registers and that should be one node in DT, as Paul's first version does. The part I'm still struggling with is understanding how the fixed-rate clocks are controlled through those registers. If they are indeed configured through the registers, the name is probably wrong and should be changed to whatever kind of non-fixed clock this is. Arnd