mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <k.kozlowski@samsung.com>
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>,
	Andreas Faerber <afaerber@suse.de>,
	linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] ARM: exynos_defconfig: Disable IOMMU support
Date: Tue, 17 Feb 2015 14:08:03 +0100	[thread overview]
Message-ID: <1424178483.19861.1.camel@AMDC1943> (raw)
In-Reply-To: <54E33A79.3060904@collabora.co.uk>

On wto, 2015-02-17 at 13:56 +0100, Javier Martinez Canillas wrote:
> Hello Krzysztof,
> 
> On 02/17/2015 01:20 PM, Krzysztof Kozlowski wrote:
> > On wto, 2015-02-17 at 12:38 +0100, Javier Martinez Canillas wrote:
> >> 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.
> > 
> > On which board you got this error?
> > 
> 
> Sorry, I should had mention it in the commit message. I get that error
> with at least Exynos5800 Peach Pi, Exynos5420 Peach Pit and Exynos5250
> Snow Chromebooks with today's next (next-20150217).
> 
> The problem is that the Exynos IOMMU driver does not set a struct
> exynos_iommu_owner in dev.archdata.iommu but __exynos_sysmmu_enable()
> has a BUG_ON(!has_sysmmu(dev)).
> 
> Marek's series [1] solves this issue by filling sysmmu devices from DT
> but causes boot failures on the Exynos Chromebooks because the display
> is left enabled by the bootloader [2].
> 
> So I think that this option should be disabled until is known to not
> cause issues on any platform.

Sure, I am completely fine with that change. I just wanted to know the
hardware.

Anyway Marek already acked this I won't duplicate the effort :).

Best regards,
Krzysztof




  reply	other threads:[~2015-02-17 13:08 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-17 11:38 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 [this message]
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
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=1424178483.19861.1.camel@AMDC1943 \
    --to=k.kozlowski@samsung.com \
    --cc=afaerber@suse.de \
    --cc=javier.martinez@collabora.co.uk \
    --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 \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome