From: Sjoerd Simons <sjoerd.simons@collabora.co.uk>
To: Kevin Hilman <khilman@kernel.org>
Cc: "Javier Martinez Canillas" <javier.martinez@collabora.co.uk>,
"Kukjin Kim" <kgene@kernel.org>,
"Olof Johansson" <olof@lixom.net>,
"Andreas Färber" <afaerber@suse.de>,
"Marek Szyprowski" <m.szyprowski@samsung.com>,
"Doug Anderson" <dianders@chromium.org>,
"Andrzej Hajda" <a.hajda@samsung.com>,
linux-samsung-soc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, inki.dae@samsung.com
Subject: Re: [PATCH 1/1] Revert "ARM: dts: add display power domain for exynos5250"
Date: Wed, 29 Apr 2015 21:45:16 +0200 [thread overview]
Message-ID: <1430336716.19504.92.camel@collabora.co.uk> (raw)
In-Reply-To: <7hr3r2suiw.fsf@deeprootsystems.com>
On Wed, 2015-04-29 at 10:40 -0700, Kevin Hilman wrote:
> Javier Martinez Canillas <javier.martinez@collabora.co.uk> writes:
> Tested-by: Kevin Hilman <khilman@linaro.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@collabora.co.uk>
Collabora Ltd.
next prev parent reply other threads:[~2015-04-29 19:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-23 10:49 [PATCH 1/1] Revert "ARM: dts: add display power domain for exynos5250" Javier Martinez Canillas
2015-03-27 14:29 ` Krzysztof Kozlowski
2015-03-27 14:34 ` Javier Martinez Canillas
2015-04-29 17:40 ` Kevin Hilman
2015-04-29 19:45 ` Sjoerd Simons [this message]
2015-04-30 0:37 ` Javier Martinez Canillas
2015-04-30 14:59 ` Kevin Hilman
2015-04-30 15: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=1430336716.19504.92.camel@collabora.co.uk \
--to=sjoerd.simons@collabora.co.uk \
--cc=a.hajda@samsung.com \
--cc=afaerber@suse.de \
--cc=dianders@chromium.org \
--cc=inki.dae@samsung.com \
--cc=javier.martinez@collabora.co.uk \
--cc=kgene@kernel.org \
--cc=khilman@kernel.org \
--cc=linux-arm-kernel@lists.infradead.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