From: Rajendra Nayak <rnayak@ti.com>
To: Paul Walmsley <paul@pwsan.com>
Cc: linux-omap@vger.kernel.org
Subject: RE: [PATCH] OMAP: hwmod: Do not expect an entry in clkdev to add alias for opt_clks
Date: Wed, 2 Feb 2011 09:40:45 +0530 [thread overview]
Message-ID: <64895f98b88c90709eb4f571d0582407@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1102010948320.15746@utopia.booyaka.com>
> -----Original Message-----
> From: Paul Walmsley [mailto:paul@pwsan.com]
> Sent: Tuesday, February 01, 2011 10:23 PM
> To: Rajendra Nayak
> Cc: linux-omap@vger.kernel.org
> Subject: RE: [PATCH] OMAP: hwmod: Do not expect an entry in clkdev to
add alias for opt_clks
>
> On Tue, 1 Feb 2011, Rajendra Nayak wrote:
>
> > One other thing I was thinking of is if the function name
> > _add_optional_clock_alias need to be changed to something like
> > _add_optional_clock_clkdev since we are adding a new clkdev entry,
> > if it does not exist, and no longer adding an 'alias' for an existing
> > entry.
>
> Fine with me.
>
> > Also, the adding of an entry in clkdev is today done for
> > optional clocks alone. Is there any reason why we should not do
> > this at runtime for all main clks and interface clks also.
> > That way we get rid of all dependencies with the static clkdev
> > table, and we might infact not need one if all entries are added
> > runtime.
>
> Heh, you've just uncovered my "secret" plan. It seemed best to me to
wait
> until all of the hwmod conversions were done to avoid alarming certain
> people who might be consulting the static clkdev table in
> mach-omap2/clock*_data.c as a platform reference...
Ok, sounds good to me, thanks.
Will repost this one with the mentioned changes.
>
>
> - Paul
prev parent reply other threads:[~2011-02-02 4:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-28 11:17 [PATCH] OMAP: hwmod: Do not expect an entry in clkdev to add alias for opt_clks Rajendra Nayak
2011-01-31 23:08 ` Paul Walmsley
2011-02-01 5:23 ` Rajendra Nayak
2011-02-01 16:53 ` Paul Walmsley
2011-02-02 4:10 ` Rajendra Nayak [this message]
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=64895f98b88c90709eb4f571d0582407@mail.gmail.com \
--to=rnayak@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.com \
/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