From: Javier Martinez Canillas <javier.martinez@collabora.co.uk>
To: Kevin Hilman <khilman@kernel.org>
Cc: "Sjoerd Simons" <sjoerd.simons@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: Thu, 30 Apr 2015 17:23:05 +0200 [thread overview]
Message-ID: <554248D9.4030203@collabora.co.uk> (raw)
In-Reply-To: <7hk2wtpsqq.fsf@deeprootsystems.com>
Hello Kevin,
On 04/30/2015 04:59 PM, Kevin Hilman wrote:
> Javier Martinez Canillas <javier.martinez@collabora.co.uk> writes:
>>
>> The regression on Exynos5420/5422/5800 that has been for a while is fixed
>> by "ARM: dts: Make DP a consumer of DISP1 power domain on Exynos5420" [0]
>> which has been posted many weeks ago.
>
> Thanks for clarifying.
>
> I'm not sure how this worked for me. Seems like sometimes, even with
> the imprecise aborts it does actually finish booting to a shell, so I
> must've gotten successful boot and thought it was because of this
> revert.
That is correct, the imprecise external abort error most of the times
lead to a kernel panic but sometimes it doesn't and the the system finish
booting to user-space even after the error.
I've pinged Kukjin again yesterday to pick the fix and he said that will
do it this weekend [0]. So hopefully exynos5420 machines will boot again
in linux-next soon after being broken for weeks.
>
> Kevin
>
Best regards,
Javier
[0]: https://lkml.org/lkml/2015/4/29/781
WARNING: multiple messages have this Message-ID (diff)
From: javier.martinez@collabora.co.uk (Javier Martinez Canillas)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/1] Revert "ARM: dts: add display power domain for exynos5250"
Date: Thu, 30 Apr 2015 17:23:05 +0200 [thread overview]
Message-ID: <554248D9.4030203@collabora.co.uk> (raw)
In-Reply-To: <7hk2wtpsqq.fsf@deeprootsystems.com>
Hello Kevin,
On 04/30/2015 04:59 PM, Kevin Hilman wrote:
> Javier Martinez Canillas <javier.martinez@collabora.co.uk> writes:
>>
>> The regression on Exynos5420/5422/5800 that has been for a while is fixed
>> by "ARM: dts: Make DP a consumer of DISP1 power domain on Exynos5420" [0]
>> which has been posted many weeks ago.
>
> Thanks for clarifying.
>
> I'm not sure how this worked for me. Seems like sometimes, even with
> the imprecise aborts it does actually finish booting to a shell, so I
> must've gotten successful boot and thought it was because of this
> revert.
That is correct, the imprecise external abort error most of the times
lead to a kernel panic but sometimes it doesn't and the the system finish
booting to user-space even after the error.
I've pinged Kukjin again yesterday to pick the fix and he said that will
do it this weekend [0]. So hopefully exynos5420 machines will boot again
in linux-next soon after being broken for weeks.
>
> Kevin
>
Best regards,
Javier
[0]: https://lkml.org/lkml/2015/4/29/781
next prev parent reply other threads:[~2015-04-30 15:23 UTC|newest]
Thread overview: 16+ 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-23 10:49 ` Javier Martinez Canillas
2015-03-27 14:29 ` Krzysztof Kozlowski
2015-03-27 14:29 ` Krzysztof Kozlowski
2015-03-27 14:34 ` Javier Martinez Canillas
2015-03-27 14:34 ` Javier Martinez Canillas
2015-04-29 17:40 ` Kevin Hilman
2015-04-29 17:40 ` Kevin Hilman
2015-04-29 19:45 ` Sjoerd Simons
2015-04-29 19:45 ` Sjoerd Simons
2015-04-30 0:37 ` Javier Martinez Canillas
2015-04-30 0:37 ` Javier Martinez Canillas
2015-04-30 14:59 ` Kevin Hilman
2015-04-30 14:59 ` Kevin Hilman
2015-04-30 15:23 ` Javier Martinez Canillas [this message]
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=554248D9.4030203@collabora.co.uk \
--to=javier.martinez@collabora.co.uk \
--cc=a.hajda@samsung.com \
--cc=afaerber@suse.de \
--cc=dianders@chromium.org \
--cc=inki.dae@samsung.com \
--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 \
--cc=sjoerd.simons@collabora.co.uk \
/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.