Re: Query: MUSB clock management code

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Arm (vger)]     [ARM Kernel]     [ARM MSM]     [Linux Tegra]     [Linux WPAN Networking]     [Linux Wireless Networking]     [Maemo Users]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux