[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Tue, 03 Mar 2015 12:36:08 -0800
From: Kevin Hilman <khilman@...nel.org>
To: Javier Martinez Canillas <javier.martinez@...labora.co.uk>
Cc: Kukjin Kim <kgene@...nel.org>, Olof Johansson <olof@...om.net>,
Marek Szyprowski <m.szyprowski@...sung.com>,
Krzysztof Kozlowski <k.kozlowski@...sung.com>,
Andreas Faerber <afaerber@...e.de>,
linux-samsung-soc@...r.kernel.org, linux-kernel@...r.kernel.org,
tyler.baker@...aro.org
Subject: Re: [PATCH 1/1] ARM: exynos_defconfig: Disable IOMMU support
Javier Martinez Canillas <javier.martinez@...labora.co.uk> writes:
> Enabling Exynos DRM IOMMU support for Exynos is currently broken and
> causes a BUG on exynos-iommu driver. This was not an issue since the
> options was disabled in exynos_defconfig but after commit 8dcc14f82f06
> ("drm/exynos: IOMMU support should not be selectable by user"), it is
> selected if EXYNOS_IOMMU is enabled which is in exynos_defconfig.
>
> So a kernel built using exynos_defconfig after the mentioned commit
> fails to boot [0]. Disable IOMMU support in Exynos defconfig until
> things get sorted out.
So some other exynos boards started failing in next-20150303[1], and
appear are DRM failures.
Interestingly, (re)enabling CONFIG_EXYNOS_IOMMU for these cause things to
work again. Even more intersting, with IOMMU enabled, peach-pi is
I'm starting to think it's the DRM driver that needs to be disabled
until it actually gets some testing, rathre than disabling IOMMU.
Kevin
[1] http://kernelci.org/boot/?next-20150303&fail
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists