RE: [PATCHV3 3/4] OMAP3: Correct width for CLKSEL Fields

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

 



Hello Vishwanath,

On Tue, 8 Dec 2009, Sripathy, Vishwanath wrote:

> I am thinking of adding a new file called /mach-omap2/clock36xx.h and 
> have complete 36xx clock tree defined over there instead of tweaking 
> 34xx clock tree. Any comments?

Aren't most of the clocks shared between 34xx and 36xx?  If so, it seems 
better to try to keep as many structures shared as possible, no?

Also, there is a fairly major clock update that should go in for .33 that 
moves the clock files around.  You might want to base your changes on that 
branch, until Tony pulls it in.  More info here:

    http://marc.info/?l=linux-omap&m=126034503819371&w=2


- Paul
--
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