From: Julien Grall Date: Fri, 13 Sep 2013 12:49:29 +0000 (+0100) Subject: xen/arm: exynos5: Blacklist MCT device X-Git-Tag: archive/raspbian/4.8.0-1+rpi1~1^2~6338 X-Git-Url: https://dgit.raspbian.org/?a=commitdiff_plain;h=64e2efcad8789bdb09abc4c07f4cc259d8b42676;p=xen.git xen/arm: exynos5: Blacklist MCT device The Multi Core Timer (MCT) is a Samsung specific device. This device tries to route IRQ in non-boot CPU which is not yet handled by Xen. The user will see randomly dom0 hang, but I'm not sure that is the real reason. Signed-off-by: Julien Grall Acked-by: Ian Campbell --- diff --git a/xen/arch/arm/platforms/exynos5.c b/xen/arch/arm/platforms/exynos5.c index 262ded8b98..d9eedc86ce 100644 --- a/xen/arch/arm/platforms/exynos5.c +++ b/xen/arch/arm/platforms/exynos5.c @@ -92,12 +92,23 @@ static const char * const exynos5_dt_compat[] __initdata = NULL }; +static const struct dt_device_match exynos5_blacklist_dev[] __initconst = +{ + /* Multi core Timer + * TODO: this device set up IRQ to CPU 1 which is not yet handled by Xen. + * This is result to random freeze. + */ + DT_MATCH_COMPATIBLE("samsung,exynos4210-mct"), + { /* sentinel */ }, +}; + PLATFORM_START(exynos5, "SAMSUNG EXYNOS5") .compatible = exynos5_dt_compat, .init_time = exynos5_init_time, .specific_mapping = exynos5_specific_mapping, .reset = exynos5_reset, .quirks = exynos5_quirks, + .blacklist_dev = exynos5_blacklist_dev, PLATFORM_END /*