* Query: MUSB clock management code
@ 2009-08-24 11:09 Gadiyar, Anand
2009-08-25 9:05 ` Felipe Balbi
0 siblings, 1 reply; 2+ messages in thread
From: Gadiyar, Anand @ 2009-08-24 11:09 UTC (permalink / raw)
To: linux-omap@vger.kernel.org
Hi all,
Is there a reason to have a wrapper code around the clock
enable/disable code in arch/arm/mach-omap2/usb-musb.c?
Is it not okay for the glue-layer code in
drivers/usb/musb/omap2430.c to do this?
Thanks in advance,
Anand
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Query: MUSB clock management code
2009-08-24 11:09 Query: MUSB clock management code Gadiyar, Anand
@ 2009-08-25 9:05 ` Felipe Balbi
0 siblings, 0 replies; 2+ messages in thread
From: Felipe Balbi @ 2009-08-25 9:05 UTC (permalink / raw)
To: ext Gadiyar, Anand; +Cc: linux-omap@vger.kernel.org
On Mon, Aug 24, 2009 at 01:09:43PM +0200, ext Gadiyar, Anand wrote:
> Hi all,
>
> Is there a reason to have a wrapper code around the clock
> enable/disable code in arch/arm/mach-omap2/usb-musb.c?
> Is it not okay for the glue-layer code in
> drivers/usb/musb/omap2430.c to do this?
most likely, not anymore, but we needed that as means not to pass clock
name to musb driver. Once all other users of musb move to clkdev, we can
remove that and use plain clk fw calls.
--
balbi
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2009-08-25 9:07 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-08-24 11:09 Query: MUSB clock management code Gadiyar, Anand
2009-08-25 9:05 ` Felipe Balbi
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox