From: Inki Dae <inki.dae@samsung.com>
To: Javier Martinez Canillas <javier.martinez@collabora.co.uk>
Cc: Kevin Hilman <khilman@deeprootsystems.com>,
linux-samsung-soc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
kernel-build-reports@lists.linaro.org,
Olof Johansson <olof@lixom.net>, Arnd Bergmann <arnd@arndb.de>
Subject: Re: exynos boot falures in linux-next
Date: Tue, 18 Nov 2014 11:30:18 +0900 [thread overview]
Message-ID: <546AAF3A.5090604@samsung.com> (raw)
In-Reply-To: <546A83D6.9060504@collabora.co.uk>
Hello all,
On 2014년 11월 18일 08:25, Javier Martinez Canillas wrote:
> Hello Kevin,
>
> On 11/17/2014 11:24 PM, Kevin Hilman wrote:
>>
>> As might have been expected, reverting the change that enables the
>> DRM/display options in exynos_defconfig fixes the problem.
>>
>> Kevin
>>
>
> I'm sorry for causing a boot failure but when I first posted that patch,
> the Exynos DRM driver was working correctly (at least on the Exynos boards
> I've access to) so it seems the regression was introduced while the patch
> was posted but not yet picked.
>
> I'm not sure what is the correct step in this case but I'm OK with
> reverting the patch until the Exynos DRM driver bug is fixed.
I found out a bug of Exynos DRM, which is infinite loop issue incurred
by -EPROBE_DEFER. I thought that we resolved this issue with some fixups
but not yet. The problem is because -EPROBE_DEFER is returned in case of
adding a component of a crtc device but one of a connector device. I
will fix it up soon.
Thanks for report,
Inki Dae
>
> Best regards,
> Javier
> --
> To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
WARNING: multiple messages have this Message-ID (diff)
From: inki.dae@samsung.com (Inki Dae)
To: linux-arm-kernel@lists.infradead.org
Subject: exynos boot falures in linux-next
Date: Tue, 18 Nov 2014 11:30:18 +0900 [thread overview]
Message-ID: <546AAF3A.5090604@samsung.com> (raw)
In-Reply-To: <546A83D6.9060504@collabora.co.uk>
Hello all,
On 2014? 11? 18? 08:25, Javier Martinez Canillas wrote:
> Hello Kevin,
>
> On 11/17/2014 11:24 PM, Kevin Hilman wrote:
>>
>> As might have been expected, reverting the change that enables the
>> DRM/display options in exynos_defconfig fixes the problem.
>>
>> Kevin
>>
>
> I'm sorry for causing a boot failure but when I first posted that patch,
> the Exynos DRM driver was working correctly (at least on the Exynos boards
> I've access to) so it seems the regression was introduced while the patch
> was posted but not yet picked.
>
> I'm not sure what is the correct step in this case but I'm OK with
> reverting the patch until the Exynos DRM driver bug is fixed.
I found out a bug of Exynos DRM, which is infinite loop issue incurred
by -EPROBE_DEFER. I thought that we resolved this issue with some fixups
but not yet. The problem is because -EPROBE_DEFER is returned in case of
adding a component of a crtc device but one of a connector device. I
will fix it up soon.
Thanks for report,
Inki Dae
>
> Best regards,
> Javier
> --
> To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in
> the body of a message to majordomo at vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2014-11-18 2:30 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1XqKYI-0000pQ-4b@ip-10-35-177-41.ec2.internal>
2014-11-17 15:57 ` exynos boot falures in linux-next (was: next boot: 94 boots: 79 pass, 13 fail, 2 untried (next-20141117)) Kevin Hilman
2014-11-17 16:57 ` exynos boot falures in linux-next Krzysztof Kozłowski
2014-11-17 16:57 ` Krzysztof Kozłowski
2014-11-17 22:24 ` Kevin Hilman
2014-11-17 22:24 ` Kevin Hilman
2014-11-17 23:25 ` Javier Martinez Canillas
2014-11-17 23:25 ` Javier Martinez Canillas
2014-11-18 2:30 ` Inki Dae [this message]
2014-11-18 2:30 ` Inki Dae
2014-11-18 3:49 ` Kevin Hilman
2014-11-18 3:49 ` Kevin Hilman
2014-11-19 17:01 ` Kevin Hilman
2014-11-19 17:01 ` Kevin Hilman
2014-11-19 17:06 ` Javier Martinez Canillas
2014-11-19 17:06 ` Javier Martinez Canillas
2014-11-20 1:55 ` Kukjin Kim
2014-11-20 1:55 ` Kukjin Kim
2014-12-02 8:32 ` Javier Martinez Canillas
2014-12-02 8:32 ` Javier Martinez Canillas
[not found] ` <7h61ed4xm3.fsf@deeprootsystems.com>
2014-11-17 18:21 ` mirabox boot fails in linux-next (was: next boot: 94 boots: 79 pass, 13 fail, 2 untried (next-20141117)) Thomas Petazzoni
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=546AAF3A.5090604@samsung.com \
--to=inki.dae@samsung.com \
--cc=arnd@arndb.de \
--cc=javier.martinez@collabora.co.uk \
--cc=kernel-build-reports@lists.linaro.org \
--cc=khilman@deeprootsystems.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--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 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.