From: Felipe Balbi <felipe.balbi@nokia.com>
To: ext Paul Walmsley <paul@pwsan.com>
Cc: "Balbi Felipe (Nokia-D/Helsinki)" <felipe.balbi@nokia.com>,
Tony Lindgren <tony@atomide.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
Kevin Hilman <kjh@hilman.org>
Subject: Re: [rfc/rft/patch-v2.6.32-omap1+ 1/2] arm: omap: clock: add omap_udc to clkdev
Date: Mon, 21 Dec 2009 09:05:29 +0200 [thread overview]
Message-ID: <20091221070529.GA30969@nokia.com> (raw)
In-Reply-To: <alpine.DEB.2.00.0912171904330.12561@utopia.booyaka.com>
On Fri, Dec 18, 2009 at 03:05:09AM +0100, ext Paul Walmsley wrote:
>Hi Felipe,
>
>On Wed, 16 Dec 2009, Felipe Balbi wrote:
>
>> then we can later remove all of those cpu conditionals
>> on drivers/usb/gadget/omap_udc.c
>>
>> Cc: Paul Walmsley <paul@pwsan.com>
>> Signed-off-by: Felipe Balbi <felipe.balbi@nokia.com>
>> ---
>>
>> Paul, do you think the following is correct ? Judging
>> by omap_udc.c those are the clocks used by that driver
>> but I don't have boards to try out.
>
>I guess these can also be used by ohci-omap.c ?
in that case do we add two CLK() entries ?
--
balbi
next prev parent reply other threads:[~2009-12-21 7:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-16 21:52 [rfc/rft/patch-v2.6.32-omap1+ 0/2] misc patches Felipe Balbi
2009-12-16 21:52 ` [rfc/rft/patch-v2.6.32-omap1+ 1/2] arm: omap: clock: add omap_udc to clkdev Felipe Balbi
2009-12-18 2:05 ` Paul Walmsley
2009-12-21 7:05 ` Felipe Balbi [this message]
2009-12-16 21:52 ` [rfc/rft/patch-v2.6.32-omap1+ 2/2] arm: omap: add missing __initdata to omap_board_config_kernel Felipe Balbi
2009-12-16 23:41 ` Ladislav Michl
2010-01-05 23:44 ` Tony Lindgren
2010-01-07 11:29 ` Tomi Valkeinen
2010-01-07 18:54 ` Tony Lindgren
2010-01-07 0:49 ` [APPLIED] [rfc/rft/patch-v2.6.32-omap1+ 2/2] arm: omap: add missing Tony Lindgren
2010-01-07 0:53 ` [_NOT_ APPLIED] " Tony Lindgren
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=20091221070529.GA30969@nokia.com \
--to=felipe.balbi@nokia.com \
--cc=kjh@hilman.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox