From: Rajendra Nayak <rnayak@ti.com>
To: Saravana Kannan <skannan@codeaurora.org>
Cc: "Turquette, Mike" <mturquette@ti.com>,
Mark Brown <broonie@opensource.wolfsonmicro.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Sascha Hauer <s.hauer@pengutronix.de>,
andrew@lunn.ch,
"linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>
Subject: Re: [PATCH] clk: Constify struct clk_init_data
Date: Tue, 15 May 2012 10:43:26 +0530 [thread overview]
Message-ID: <4FB1E5F6.7070401@ti.com> (raw)
In-Reply-To: <4FB1AC79.7000901@codeaurora.org>
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
next prev parent reply other threads:[~2012-05-15 5:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-14 14:12 [PATCH] clk: Constify struct clk_init_data Mark Brown
2012-05-14 21:53 ` Turquette, Mike
2012-05-15 1:08 ` Saravana Kannan
2012-05-15 5:13 ` Rajendra Nayak [this message]
2012-05-15 5:59 ` Turquette, Mike
2012-05-15 1:19 ` Saravana Kannan
2012-05-15 7:00 ` Sascha Hauer
2012-05-15 16:42 ` Saravana Kannan
2012-05-15 18:15 ` Saravana Kannan
2012-06-12 17:10 ` Mike Turquette
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4FB1E5F6.7070401@ti.com \
--to=rnayak@ti.com \
--cc=andrew@lunn.ch \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@ti.com \
--cc=s.hauer@pengutronix.de \
--cc=skannan@codeaurora.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox