[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1430336716.19504.92.camel@collabora.co.uk>
Date: Wed, 29 Apr 2015 21:45:16 +0200
From: Sjoerd Simons <sjoerd.simons@...labora.co.uk>
To: Kevin Hilman <khilman@...nel.org>
Cc: Javier Martinez Canillas <javier.martinez@...labora.co.uk>,
Kukjin Kim <kgene@...nel.org>, Olof Johansson <olof@...om.net>,
Andreas Färber <afaerber@...e.de>,
Marek Szyprowski <m.szyprowski@...sung.com>,
Doug Anderson <dianders@...omium.org>,
Andrzej Hajda <a.hajda@...sung.com>,
linux-samsung-soc@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
inki.dae@...sung.com
Subject: Re: [PATCH 1/1] Revert "ARM: dts: add display power domain for
exynos5250"
On Wed, 2015-04-29 at 10:40 -0700, Kevin Hilman wrote:
> Javier Martinez Canillas <javier.martinez@...labora.co.uk> writes:
> Tested-by: Kevin Hilman <khilman@...aro.org>
>
> FWIW, this patch fixes the boot panics when using MMC rootfs on
> exynos5800-peach-pi with current linux-next that have been happening
> for awhile.
That seems unlikely as this patch changes things in the exynos5250.dtsi,
which isn't used by exynos5800-peach-pi.?
> For several months now, DRM/display related stuff is very routinely
> breaking basic booting on exynos5, which gives the rather strong
> impression that the DRM stuff is not tested well enough to be merged.
Unfortunately it seems to have been that way for ages, but only has
started being visible since Javier turned on the various exynos DRM
drivers on in exynos_defconfig.. So now we're actually seeing bugs
rather then just having broken code sit around :/
--
Sjoerd Simons <sjoerd.simons@...labora.co.uk>
Collabora Ltd.
--
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