[PATCH 3/6] omap4: l2x0: Override the default l2x0_disable
Tony Lindgren
tony at atomide.com
Wed Sep 15 20:21:35 EDT 2010
* Santosh Shilimkar <santosh.shilimkar at ti.com> [100907 00:50]:
> The machine_kexec() calls outer_disable which can crash on OMAP4
> becasue of trustzone restrictions.
>
> This patch overrides the default l2x0_disable with a OMAP4
> specific implementation taking care of trustzone
<snip>
> @@ -66,6 +73,12 @@ static int __init omap_l2_cache_init(void)
>
> */
> l2x0_init(l2cache_base, 0x0e050000, 0xc0000fff);
>
> + /*
> + * Override default outer_cache.disable with a OMAP4
> + * specific one
> + */
> + outer_cache.disable = omap4_l2x0_disable;
> +
> return 0;
> }
> early_initcall(omap_l2_cache_init);
Just to be sure.. No outer_cache functions get set unless
l2x0_init gets called, right? So omap2 and omap3 functions
always stay NULL with omap3_defconfig?
Tony
More information about the linux-arm-kernel
mailing list