From mboxrd@z Thu Jan 1 00:00:00 1970 From: Arnd Bergmann Subject: Re: [PATCH 0/4] Migrate PXA27x platforms to clock framework Date: Mon, 30 Jun 2014 08:55:15 +0200 Message-ID: <7034630.fvV46PN35C@wuerfel> References: <1404066744-13416-1-git-send-email-robert.jarzmik@free.fr> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Return-path: In-Reply-To: <1404066744-13416-1-git-send-email-robert.jarzmik-GANU6spQydw@public.gmane.org> Sender: devicetree-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org Cc: Robert Jarzmik , devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, Mike Turquette , Haojian Zhuang , Eric Miao , Mark Rutland List-Id: devicetree@vger.kernel.org On Sunday 29 June 2014 20:32:20 Robert Jarzmik wrote: > As the RFC posted in [1] didn't meet an unrivaled success for > review, I'm posting this serie for PXA27x transition to clock > framework. > > This transition is needed : > - to enable device-tree drivers port, as clocks are needed almost > everywhere > - to enable the long term multi-platform kernel to support PXA > > As I had said before, this serie aims at : > - keeping legacy platforms working (ie. without device-tree) > - enable PXA27x to work with a device-tree kernel, and hence > open the way to drivers conversion > - be robust enough to support pxa25x and pxa3xx later inclusion > with almost no change to clk-pxa-dt.c. > > As this serie is holding the rest of the device-tree drivers > port, I'd like it to be reviewed, even it's an old unsexy > platform. I have one basic question about this series: if pxa27x gets moved to used the common-clk framework but the others (pxa25x, pxa26x, pxa3xx, pxa93x) don't, does that imply that they become mutually exclusiv at compile-time? If so, do you plan to first complete all of them before merging upstream, or do you intend to have one or more kernel releases that don't allow building a combined kernel for all pxa platforms? I don't object to doing the latter, but if that is the plan, you need to make that very clear in the changelog and have all the relevant maintainers agree to that. Also (for my understanding) when you say that you plan to do pxa25x and pxa3xx next, does that include pxa26x and pxa93x? I assume it does as they are apparently minor revisions of the former, but it's not completely clear from your description. Arnd -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html From mboxrd@z Thu Jan 1 00:00:00 1970 From: arnd@arndb.de (Arnd Bergmann) Date: Mon, 30 Jun 2014 08:55:15 +0200 Subject: [PATCH 0/4] Migrate PXA27x platforms to clock framework In-Reply-To: <1404066744-13416-1-git-send-email-robert.jarzmik@free.fr> References: <1404066744-13416-1-git-send-email-robert.jarzmik@free.fr> Message-ID: <7034630.fvV46PN35C@wuerfel> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Sunday 29 June 2014 20:32:20 Robert Jarzmik wrote: > As the RFC posted in [1] didn't meet an unrivaled success for > review, I'm posting this serie for PXA27x transition to clock > framework. > > This transition is needed : > - to enable device-tree drivers port, as clocks are needed almost > everywhere > - to enable the long term multi-platform kernel to support PXA > > As I had said before, this serie aims at : > - keeping legacy platforms working (ie. without device-tree) > - enable PXA27x to work with a device-tree kernel, and hence > open the way to drivers conversion > - be robust enough to support pxa25x and pxa3xx later inclusion > with almost no change to clk-pxa-dt.c. > > As this serie is holding the rest of the device-tree drivers > port, I'd like it to be reviewed, even it's an old unsexy > platform. I have one basic question about this series: if pxa27x gets moved to used the common-clk framework but the others (pxa25x, pxa26x, pxa3xx, pxa93x) don't, does that imply that they become mutually exclusiv at compile-time? If so, do you plan to first complete all of them before merging upstream, or do you intend to have one or more kernel releases that don't allow building a combined kernel for all pxa platforms? I don't object to doing the latter, but if that is the plan, you need to make that very clear in the changelog and have all the relevant maintainers agree to that. Also (for my understanding) when you say that you plan to do pxa25x and pxa3xx next, does that include pxa26x and pxa93x? I assume it does as they are apparently minor revisions of the former, but it's not completely clear from your description. Arnd