From mboxrd@z Thu Jan 1 00:00:00 1970 From: Julien Grall Subject: [RFC 22/24] xen/arm: exynos5: Blacklist MCT device Date: Fri, 16 Aug 2013 22:05:54 +0100 Message-ID: <1376687156-6737-23-git-send-email-julien.grall@linaro.org> References: <1376687156-6737-1-git-send-email-julien.grall@linaro.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1376687156-6737-1-git-send-email-julien.grall@linaro.org> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: stefano.stabellini@eu.citrix.com, ian.campbell@citrix.com Cc: xen-devel@lists.xen.org, Julien Grall , andre.przywara@linaro.org, patches@linaro.org List-Id: xen-devel@lists.xenproject.org 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 --- xen/arch/arm/platforms/exynos5.c | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/xen/arch/arm/platforms/exynos5.c b/xen/arch/arm/platforms/exynos5.c index 1368a04..036281c 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 /* -- 1.7.10.4