[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4FB1E5F6.7070401@ti.com>
Date: Tue, 15 May 2012 10:43:26 +0530
From: Rajendra Nayak <rnayak@...com>
To: Saravana Kannan <skannan@...eaurora.org>
CC: "Turquette, Mike" <mturquette@...com>,
Mark Brown <broonie@...nsource.wolfsonmicro.com>,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
Sascha Hauer <s.hauer@...gutronix.de>, andrew@...n.ch,
"linux-arm-msm@...r.kernel.org" <linux-arm-msm@...r.kernel.org>
Subject: Re: [PATCH] clk: Constify struct clk_init_data
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.
regards,
Rajendra
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists