From: David Brownell <david-b@pacbell.net>
To: felipe.balbi@nokia.com
Cc: linux-omap@vger.kernel.org, Paul Walmsley <paul@pwsan.com>,
Tony Lindgren <tony@atomide.com>,
Kevin Hilman <khilman@deeprootsystems.com>
Subject: Re: [PATCH 1/3] [RFC] clk: introduce clk_associate
Date: Wed, 1 Oct 2008 09:15:45 -0700 [thread overview]
Message-ID: <200810010915.46032.david-b@pacbell.net> (raw)
In-Reply-To: <20081001155755.GG7412@gandalf.research.nokia.com>
On Wednesday 01 October 2008, Felipe Balbi wrote:
> > So mirroring "at91_clock_associate()" ... maybe this
> > should be "omap_clock_associate()" not "clk_associate()".
>
> Well, I'm ok with that but I'd rather see clk_associate() moving to
> clk api so anyone who needs that, could use it.
Seems like that's an "implementor's interface" rather
than a "user's interface".
So something like a "clock library" (duck!) might be
a good place for such a call... ;)
- dave
next prev parent reply other threads:[~2008-10-01 16:15 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-01 10:36 [PATCH 0/3] [RFC] introduce clk_associate Felipe Balbi
2008-10-01 10:36 ` [PATCH 1/3] [RFC] clk: " Felipe Balbi
2008-10-01 10:36 ` [PATCH 2/3] [RFC] clk: use clk_associate for musb driver Felipe Balbi
2008-10-01 10:36 ` [PATCH 3/3] [RFC] clk: use clk_associate on watchdog driver Felipe Balbi
2008-10-01 15:51 ` [PATCH 1/3] [RFC] clk: introduce clk_associate David Brownell
2008-10-01 15:57 ` Felipe Balbi
2008-10-01 16:15 ` David Brownell [this message]
2008-10-01 18:34 ` Hiroshi DOYU
2008-10-02 20:50 ` David Brownell
2008-10-02 21:33 ` Felipe Balbi
2008-10-03 6:23 ` Hiroshi DOYU
2008-10-03 7:30 ` Tony Lindgren
2008-10-06 18:42 ` David Brownell
2008-10-06 18:53 ` Felipe Balbi
2008-10-14 16:33 ` Paul Walmsley
2008-10-14 20:19 ` Hiroshi DOYU
2008-10-15 9:13 ` Paul Walmsley
2008-10-15 10:15 ` Hiroshi DOYU
2008-10-15 22:41 ` Woodruff, Richard
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=200810010915.46032.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=felipe.balbi@nokia.com \
--cc=khilman@deeprootsystems.com \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.com \
--cc=tony@atomide.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.