Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753055AbbGBMll (ORCPT ); Thu, 2 Jul 2015 08:41:41 -0400 Received: from mout.kundenserver.de ([212.227.17.24]:60328 "EHLO mout.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750958AbbGBMla (ORCPT ); Thu, 2 Jul 2015 08:41:30 -0400 From: Arnd Bergmann To: Paul Osmialowski Cc: 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 Date: Thu, 02 Jul 2015 14:40:23 +0200 Message-ID: <1861313.aMcV1xHCIq@wuerfel> User-Agent: KMail/4.11.5 (Linux/3.16.0-10-generic; KDE/4.11.5; x86_64; ; ) In-Reply-To: References: <1435667250-28299-1-git-send-email-pawelo@king.net.pl> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Provags-ID: V03:K0:LrB0RRhlcRuyfJGqZ+Q9Ap8KJLf2WuDGwWeHJ72vnj4PO9i73Jw R+NVBtOl952VPNFUu0FjCETNGsY0mSp7Zwf9tTv+4DnpCvyDH9VsD0ZNzzo/L0Qs+7t9Ddm /utBe7hDaG82r0IqoGI7V3LOZW8tSF4edKQXvTnCNUS7PsV0gXvCaorJWtQVHBaNsIudikS SBplAXc+NAmiGgkAHFz4g== X-UI-Out-Filterresults: notjunk:1;V01:K0:ltXU+QToXmA=:lyOOnOHbW4PW8pdB+eaqgZ uYjUEBRFq1kEEetwyPE7rlsoNN8KVX4Vm83UudpyPkBHdtNaM4ixVPtuCEFzhOQ9kO7ysb6w9 XPuiEJF9MYNJmQT131MSkzD58hVpphxTk1nukl3Je8zZpSG/wzNiSoxT9KRMGVGbSBM9+Fk9B SL3o5KzYlJMLFgJ2mEG76jOenAP2y5JzUI4qFRmufeQCdOjrZ6qZJAqwO4IyclWtcBcVhghL7 P1nURhSuku8fLC0jEqKMXzFg7IDVICMxoEnWRmI0tvG08uI1I/ZvvbmJ55V0X3A78J/HloxwK fXvk1nHr2k9Jx11dI+uV5Odah26tBs6n0oxNI9au/gVbJUrjYDq31ik9zbI5jC49hJA9epeMc VFfYR0h1UShmB7c1o2GSQXZnGfMBhsDz/zzvvSsHdwK1ba9yeWt0kccMtT3ogvPGuFl4AJTtj haAoCi7bU8ZT82BrAmlkSqTuYZvHgokoHAfSU8JY9EdFEtPpaaNJDEZ1vOqYaFyiNXJFrNZJn cMkIGgmYdjs4q4FxuXnLm9yhR+CKJvxZoBOc6W7fp+cmIApwxBL1uZtaCb0TSD4uUNMhDFSDn iiyuRPValMTGO9tmLZrusejAMxksqyWi8WDY+PlIM1h7tLfUc1hT4uP+nsVSZgauLJqiSn1ra UNxRFQNmk7yneg1HUv3w3la82Rco1U6PajboQV028hkKOwQ== Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 739 Lines: 19 On Thursday 02 July 2015 12:08:39 Paul Osmialowski wrote: > Nah, I've found this code hard to maintain. I'm attaching simplified > version. > Looks better to me, but of course needs full review from the clock maintainers. 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 -- 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/