From: Inki Dae <inki.dae@samsung.com>
To: Javier Martinez Canillas <javier@osg.samsung.com>,
dri-devel@lists.freedesktop.org
Cc: airlied@linux.ie, linux-samsung-soc@vger.kernel.org
Subject: Re: [PATCH 2/3] drm/exynos: fimd: add HW trigger support
Date: Wed, 01 Jun 2016 14:56:36 +0900 [thread overview]
Message-ID: <574E7914.3020201@samsung.com> (raw)
In-Reply-To: <a8e410dd-ef60-f8cd-f4ea-cf60414db5bd@osg.samsung.com>
Hi Javier,
2016년 05월 31일 07:58에 Javier Martinez Canillas 이(가) 쓴 글:
> Hello Inki,
>
> On 04/05/2016 04:27 AM, Inki Dae wrote:
>> This patch adds HW trigger support on i80 mode.
>>
>> Until now, Exynos DRM only supported SW trigger which was set
>> SWTRGCMD bit of TRIGCON register by CPU to transfer scanout
>> buffer to Display bus device or panel.
>>
>> With this patch, the transmission to Display bus device or
>> panel will be initiated by FIMD controller.
>>
>> Signed-off-by: Inki Dae <inki.dae@samsung.com>
>> ---
>
> There is a regression for the Exynos5800 Peach Pi Chromebook display due
> this patch. The display is blank and I noticed that it only happens when
> HW start trigger is enabled, but works with SW trigger (as it was before).
Posted below pathch,
[PATCH] drm/exynos: fimd: fix trigger mode change regression
Can you test it again with the patch? I have no HW to test it. :(
Thanks,
Inki Dae
>
> So for example with the following diff on top of v4.7-rc1, display works
> again. Do you have any hints about what could be the issue?
>
> diff --git a/drivers/gpu/drm/exynos/exynos_drm_fimd.c b/drivers/gpu/drm/exynos/exynos_drm_fimd.c
> index 0444d7fc400d..8c62830e9514 100644
> --- a/drivers/gpu/drm/exynos/exynos_drm_fimd.c
> +++ b/drivers/gpu/drm/exynos/exynos_drm_fimd.c
> @@ -171,7 +171,7 @@ static struct fimd_driver_data exynos5420_fimd_driver_data = {
> .lcdblk_vt_shift = 24,
> .lcdblk_bypass_shift = 15,
> .lcdblk_mic_bypass_shift = 11,
> - .trg_type = I80_HW_TRG,
> .has_shadowcon = 1,
> .has_vidoutcon = 1,
> .has_vtsel = 1,
>
> Best regards,
>
next prev parent reply other threads:[~2016-06-01 5:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-05 8:27 [PATCH 0/3] drm/exynos: support HW trigger on i80 mode Inki Dae
2016-04-05 8:27 ` [PATCH 1/3] drm/exynos: clean up wait_for_vblank Inki Dae
2016-04-05 8:27 ` [PATCH 2/3] drm/exynos: fimd: add HW trigger support Inki Dae
2016-05-30 22:58 ` Javier Martinez Canillas
2016-05-31 15:18 ` Marc Zyngier
2016-05-31 23:50 ` Inki Dae
2016-06-01 5:56 ` Inki Dae [this message]
2016-06-01 13:13 ` Javier Martinez Canillas
2016-04-05 8:27 ` [PATCH 3/3] drm/exynos: decon: clean up interface type Inki Dae
2016-04-05 11:07 ` Andrzej Hajda
2016-04-05 12:52 ` Inki Dae
2016-04-12 0:40 ` Inki Dae
2016-04-12 5:55 ` Andrzej Hajda
2016-04-12 6:05 ` 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=574E7914.3020201@samsung.com \
--to=inki.dae@samsung.com \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=javier@osg.samsung.com \
--cc=linux-samsung-soc@vger.kernel.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 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.