OMAP2xxx: clock: fix interface clocks and clockdomains for modules in the WKUP domain
authorPaul Walmsley <paul@pwsan.com>
Wed, 16 Feb 2011 22:38:38 +0000 (15:38 -0700)
committerPaul Walmsley <paul@pwsan.com>
Tue, 8 Mar 2011 03:19:39 +0000 (20:19 -0700)
commit19c1c0ce9ddc45fe8f84b6cf12ba9dbecd7b1aa1
treecae5b8789dbd3a6f486c5eed7b06f352554f69bd
parent3f9cfd3a47a07c93ff00a1a4ca067ada87e4076a
OMAP2xxx: clock: fix interface clocks and clockdomains for modules in the WKUP domain

The parent of the interface clocks for GPTIMER1, MPU_WDT,
SYNCTIMER_32K, SCM, WDT1, and the ICR (2430 only) were all listed as
being l4_ck.  This isn't accurate; these modules exist inside the WKUP
domain, and the interface clock to these modules runs at the SYS_CLK
rate rather than the CORE L4 rate.

So, create a new clock "wu_l4_ick", similar to the OMAP3
"wkup_l4_ick", that serves as the parent for these clocks.

Also, these clocks were listed as existing inside core_l4_clkdm;
wkup_clkdm is probably more accurate.

Signed-off-by: Paul Walmsley <paul@pwsan.com>
arch/arm/mach-omap2/clock2420_data.c
arch/arm/mach-omap2/clock2430_data.c