From baee1ca8e61aa9df034e1706052a0eefc193f688 Mon Sep 17 00:00:00 2001 From: Paul Walmsley Date: Tue, 12 Aug 2008 15:31:44 -0600 Subject: [PATCH] OMAP2 clock: associate clocks with clockdomains at startup The OMAP2 clock code was missing code to associate clocks with clockdomains at registration time; fix this. Resolves "Unhandled fault: alignment exception (0x001) at 0xc02c1b4e" (address may vary) panic during clock framework init on OMAP2. The alignment error was caused by an attempt to dereference a pointer to a string (1-byte aligned) as if it were a pointer to a structure. Thanks to Felipe Balbi for originally reporting this bug. Signed-off-by: Paul Walmsley Signed-off-by: Tony Lindgren --- arch/arm/mach-omap2/clock24xx.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/arch/arm/mach-omap2/clock24xx.c b/arch/arm/mach-omap2/clock24xx.c index 370f4f042fe..0d9d91f7072 100644 --- a/arch/arm/mach-omap2/clock24xx.c +++ b/arch/arm/mach-omap2/clock24xx.c @@ -567,11 +567,13 @@ int __init omap2_clk_init(void) if ((*clkp)->flags & CLOCK_IN_OMAP242X && cpu_is_omap2420()) { clk_register(*clkp); + omap2_init_clk_clkdm(*clkp); continue; } if ((*clkp)->flags & CLOCK_IN_OMAP243X && cpu_is_omap2430()) { clk_register(*clkp); + omap2_init_clk_clkdm(*clkp); continue; } } -- 2.41.1