Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754410Ab2EOGAG (ORCPT ); Tue, 15 May 2012 02:00:06 -0400 Received: from na3sys009aog103.obsmtp.com ([74.125.149.71]:44658 "EHLO na3sys009aog103.obsmtp.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750972Ab2EOGAE (ORCPT ); Tue, 15 May 2012 02:00:04 -0400 MIME-Version: 1.0 In-Reply-To: <4FB1E5F6.7070401@ti.com> References: <1337004763-21250-1-git-send-email-broonie@opensource.wolfsonmicro.com> <20120514215304.GB3075@gmail.com> <4FB1AC79.7000901@codeaurora.org> <4FB1E5F6.7070401@ti.com> From: "Turquette, Mike" Date: Mon, 14 May 2012 22:59:41 -0700 Message-ID: Subject: Re: [PATCH] clk: Constify struct clk_init_data To: Rajendra Nayak Cc: Saravana Kannan , Mark Brown , linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, Sascha Hauer , andrew@lunn.ch, "linux-arm-msm@vger.kernel.org" Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1594 Lines: 39 On Mon, May 14, 2012 at 10:13 PM, Rajendra Nayak wrote: > Hi Saravana, > > > On Tuesday 15 May 2012 06:38 AM, Saravana Kannan wrote: >> >> Btw, I didn't follow up on the other thread we were having, but can you >> remind me again what was the reason that you thought that only >> __clk_init() would work for your static init code and __clk_register() >> won't work? > > > One of the main reason has been the platform implementation we have to > handle some complex mux/divider combo clocks in OMAP2/3 which rely on > 'struct clk' pointers. Maybe we can do away with the existing > implementation and redo it so we don't have any such limitation, but the > quantum of change moving to common clk has been so much that we are > trying to minimize on the platform code changes for now. So while > we move to common clk it would still be useful to have __clk_init() > around for a while till we figure out how to get rid of it for OMAP. > Just to add to what Rajendra has stated for OMAP: after OMAP's conversion is finally made initcall-able then I'll get rid of lots of the gross macros and before-the-memory-allocator-is-alive stuff. I'll make sure that no other platforms are using those bits of course, but I plan on removing some of this stuff from the core once my platform is up to speed. Regards, Mike > regards, > Rajendra -- 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/