All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@kernel.org>
To: Javier Martinez Canillas <javier.martinez@collabora.co.uk>
Cc: Kukjin Kim <kgene@kernel.org>, Olof Johansson <olof@lixom.net>,
	Marek Szyprowski <m.szyprowski@samsung.com>,
	Krzysztof Kozlowski <k.kozlowski@samsung.com>,
	Andreas Faerber <afaerber@suse.de>,
	linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org,
	tyler.baker@linaro.org
Subject: Re: [PATCH 1/1] ARM: exynos_defconfig: Disable IOMMU support
Date: Tue, 03 Mar 2015 12:36:08 -0800	[thread overview]
Message-ID: <7hioehu8cn.fsf@linaro.org> (raw)
In-Reply-To: <1424173109-30347-1-git-send-email-javier.martinez@collabora.co.uk> (Javier Martinez Canillas's message of "Tue, 17 Feb 2015 12:38:29 +0100")

Javier Martinez Canillas <javier.martinez@collabora.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

  parent reply	other threads:[~2015-03-03 20:36 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-17 11:38 [PATCH 1/1] ARM: exynos_defconfig: Disable IOMMU support Javier Martinez Canillas
2015-02-17 12:20 ` Krzysztof Kozlowski
2015-02-17 12:56   ` Javier Martinez Canillas
2015-02-17 13:08     ` Krzysztof Kozlowski
2015-02-17 12:52 ` Marek Szyprowski
2015-02-27  6:20 ` Javier Martinez Canillas
2015-03-02 19:43   ` Kukjin Kim
2015-03-03  7:01     ` Javier Martinez Canillas
2015-03-03 20:36 ` Kevin Hilman [this message]
2015-03-04  8:50   ` Marek Szyprowski
2015-03-04 10:24     ` Javier Martinez Canillas
2015-03-04 17:39       ` Kevin Hilman
2015-03-06 13:32       ` Inki Dae
2015-03-06 15:07         ` Javier Martinez Canillas
2015-03-10  2:50           ` Inki Dae
2015-03-10  5:23             ` Javier Martinez Canillas

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7hioehu8cn.fsf@linaro.org \
    --to=khilman@kernel.org \
    --cc=afaerber@suse.de \
    --cc=javier.martinez@collabora.co.uk \
    --cc=k.kozlowski@samsung.com \
    --cc=kgene@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=m.szyprowski@samsung.com \
    --cc=olof@lixom.net \
    --cc=tyler.baker@linaro.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.