From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Date: Thu, 2 Jul 2015 23:42:18 +0200 (CEST) From: Paul Osmialowski To: Arnd Bergmann cc: Paul Osmialowski , 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 , Thomas Gleixner , Anson Huang Subject: Re: [PATCH v2 3/9] arm: twr-k70f120m: clock driver for Kinetis SoC In-Reply-To: <1861313.aMcV1xHCIq@wuerfel> Message-ID: References: <1435667250-28299-1-git-send-email-pawelo@king.net.pl> <1861313.aMcV1xHCIq@wuerfel> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed List-ID: Hi Arnd, 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. > > Arnd > 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. Thanks, Paul