From: Javier Martinez Canillas <javier@osg.samsung.com>
To: Inki Dae <inki.dae@samsung.com>, dri-devel@lists.freedesktop.org
Cc: airlied@linux.ie, linux-samsung-soc@vger.kernel.org,
Kevin Hilman <khilman@linaro.org>,
Tyler Baker <tyler.baker@linaro.org>,
Gustavo Padovan <gustavo.padovan@collabora.co.uk>
Subject: Re: [PATCH v2 0/7] drm/exynos: add pm runtime support
Date: Fri, 20 Nov 2015 13:23:13 -0300 [thread overview]
Message-ID: <564F48F1.9070205@osg.samsung.com> (raw)
In-Reply-To: <564EFD13.7040409@samsung.com>
Hello Inki,
On 11/20/2015 07:59 AM, Inki Dae wrote:
> Hi Javier,
>
> 2015년 11월 20일 00:51에 Javier Martinez Canillas 이(가) 쓴 글:
>> On 11/19/2015 11:55 AM, Javier Martinez Canillas wrote:
>>>>>
>>>>
>>>> This series causes a boot failure on at least an Exynos5800 Peach Pi
>>>> Chromebook (tested myself) and seems to be the cause of other Exynos
>>>> boards failing to boot: http://kernelci.org/boot/?exynos&fail
>>>>
>>>> [snip]
>>>>
>>>>> drm/exynos: add pm_runtime to Mixer
>>>>> drm/exynos: add pm_runtime to FIMD
>>>>
>>>> I had to revert these patches in order to get the machine in a bootable
>>>> state again, the sha1 hash for these patches in next-20151119 are:
>>>>
>>>> 045febd5f813 drm/exynos: add pm_runtime to FIMD
>>
>> On a closer look, only reverting the FIMD patch is enough
>> to make at least the Exynos5800 Peach Pi to boot again.
>
> Thanks for report.
>
Thanks to you for the quick answer and providing a fix.
> I assume that the issue is because above patch removed 'suspended' variable
> for checking the suspend status in runtime so I revived it.
>
It seems your assumption was correct...
> I'm not sure that the change could resolve the issue. Could you test it
> with the change again? I have no Exynos5800 Peach Pi board. :(
>
> For this, I pushed it to below exynos-drm/for-next branch,
> https://git.kernel.org/cgit/linux/kernel/git/daeinki/drm-exynos.git/commit/?h=exynos-drm/for-next&id=e84f43e2b2c3388694b0b3a58c2c4447f1fbae7c
>
> If the issue is resolved by the change then I will modify other patches for
> DECON series. And if really so, there may be a corner case we missed.
>
... since I reverted the offending commit and cherry-picked the one
in your for-next branch and the machine booted again.
> Thanks,
> Inki Dae
>
Best regards,
--
Javier Martinez Canillas
Open Source Group
Samsung Research America
next prev parent reply other threads:[~2015-11-20 16:23 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-03 10:47 [PATCH v2 0/7] drm/exynos: add pm runtime support Inki Dae
2015-11-03 10:47 ` [PATCH v2 1/7] drm/exynos: do not start enabling DP at bind() phase Inki Dae
2015-11-03 10:47 ` [PATCH v2 2/7] drm/exynos: add pm_runtime to DP Inki Dae
2015-11-03 10:47 ` [PATCH v2 3/7] drm/exynos: add pm_runtime to HDMI Inki Dae
2015-11-03 10:47 ` [PATCH v2 4/7] drm/exynos: add pm_runtime to Mixer Inki Dae
2015-11-03 10:47 ` [PATCH v2 5/7] drm/exynos: add pm_runtime to FIMD Inki Dae
2015-11-03 10:47 ` [PATCH v2 6/7] drm/exynos: add pm_runtime to DECON 5433 Inki Dae
2015-11-03 10:47 ` [PATCH v2 7/7] drm/exynos: add pm_runtime to DECON 7 Inki Dae
2015-11-03 13:24 ` [PATCH v2 0/7] drm/exynos: add pm runtime support Andrzej Hajda
2015-11-03 15:38 ` Inki Dae
2015-11-04 7:24 ` Andrzej Hajda
2015-11-04 7:56 ` Inki Dae
2015-11-04 10:13 ` Andrzej Hajda
2015-11-04 11:46 ` Inki Dae
2015-11-19 14:51 ` Javier Martinez Canillas
2015-11-19 14:55 ` Javier Martinez Canillas
2015-11-19 15:51 ` Javier Martinez Canillas
2015-11-20 10:59 ` Inki Dae
2015-11-20 11:13 ` Inki Dae
2015-11-20 16:44 ` Javier Martinez Canillas
2015-11-21 9:38 ` Inki Dae
2015-11-21 13:40 ` Daniel Stone
2015-11-21 14:59 ` Inki Dae
2015-11-23 12:25 ` Javier Martinez Canillas
2015-11-23 16:47 ` Inki Dae
2015-11-23 18:38 ` Javier Martinez Canillas
2015-11-24 2:28 ` Inki Dae
2015-11-24 13:19 ` Javier Martinez Canillas
2015-11-25 15:52 ` Inki Dae
2015-11-20 16:23 ` Javier Martinez Canillas [this message]
2015-11-21 9:40 ` Inki Dae
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=564F48F1.9070205@osg.samsung.com \
--to=javier@osg.samsung.com \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=gustavo.padovan@collabora.co.uk \
--cc=inki.dae@samsung.com \
--cc=khilman@linaro.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=tyler.baker@linaro.org \
/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