From: Inki Dae <inki.dae@samsung.com>
To: Gustavo Padovan <gustavo@padovan.org>,
linux-samsung-soc@vger.kernel.org,
dri-devel@lists.freedesktop.org, jy0922.shim@samsung.com,
tjakobi@math.uni-bielefeld.de,
Gustavo Padovan <gustavo.padovan@collabora.co.uk>
Subject: Re: [PATCH v3 1/9] drm/exynos: pass the correct pipe number
Date: Mon, 03 Aug 2015 17:11:37 +0900 [thread overview]
Message-ID: <55BF2239.6080000@samsung.com> (raw)
In-Reply-To: <20150729201104.GA15429@joana>
Hi Gustavo,
For 1 through 9 merged. And I guess you have the rest we have to review
but this patch series doesn't have consistency of previous, v2.
So please, post the rest again re-basing on top of exynos-drm-next.
Thanks,
Inki Dae
On 2015년 07월 30일 05:11, Gustavo Padovan wrote:
> Hi Inki,
>
> Any comments about this series?
>
> Thanks,
>
> Gustavo
>
> 2015-07-16 Gustavo Padovan <gustavo@padovan.org>:
>
>> From: Gustavo Padovan <gustavo.padovan@collabora.co.uk>
>>
>> Instead of giving -1 to as arg to drm_send_vblank_event() pass the
>> correct pipe number to it.
>>
>> Signed-off-by: Gustavo Padovan <gustavo.padovan@collabora.co.uk>
>> Reviewed-by: Joonyoung Shim <jy0922.shim@samsung.com>
>> ---
>> drivers/gpu/drm/exynos/exynos_drm_crtc.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/gpu/drm/exynos/exynos_drm_crtc.c b/drivers/gpu/drm/exynos/exynos_drm_crtc.c
>> index 644b4b7..22b9ca0 100644
>> --- a/drivers/gpu/drm/exynos/exynos_drm_crtc.c
>> +++ b/drivers/gpu/drm/exynos/exynos_drm_crtc.c
>> @@ -203,7 +203,7 @@ void exynos_drm_crtc_finish_pageflip(struct drm_device *dev, int pipe)
>> spin_lock_irqsave(&dev->event_lock, flags);
>> if (exynos_crtc->event) {
>>
>> - drm_send_vblank_event(dev, -1, exynos_crtc->event);
>> + drm_send_vblank_event(dev, pipe, exynos_crtc->event);
>> drm_vblank_put(dev, pipe);
>> wake_up(&exynos_crtc->pending_flip_queue);
>>
>> --
>> 2.1.0
>>
>
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2015-08-03 8:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-16 15:23 [PATCH v3 1/9] drm/exynos: pass the correct pipe number Gustavo Padovan
2015-07-16 15:23 ` [PATCH v3 2/9] drm/exynos: use KMS version of DRM vblanks functions Gustavo Padovan
2015-07-16 15:23 ` [PATCH v3 3/9] drm/exynos: remove duplicated check for suspend Gustavo Padovan
2015-07-16 15:23 ` [PATCH v3 4/9] drm/exynos: rename win_commit/disable to atomic-like names Gustavo Padovan
2015-07-16 15:23 ` [PATCH v3 5/9] drm/exynos: pass struct exynos_drm_plane in update/enable Gustavo Padovan
2015-07-16 15:23 ` [PATCH v3 6/9] drm/exynos: use drm atomic state directly Gustavo Padovan
2015-07-16 15:23 ` [PATCH v3 7/9] drm/exynos: remove unused fields from struct exynos_drm_plane Gustavo Padovan
2015-07-16 15:23 ` [PATCH v3 8/9] drm/exynos: unify exynos_drm_plane names with drm core Gustavo Padovan
2015-07-16 15:23 ` [PATCH v3 9/9] drm/exynos: return return value of exynos_crtc->enable_vblank Gustavo Padovan
2015-07-29 20:11 ` [PATCH v3 1/9] drm/exynos: pass the correct pipe number Gustavo Padovan
2015-07-30 4:26 ` Inki Dae
2015-08-03 8:11 ` Inki Dae [this message]
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=55BF2239.6080000@samsung.com \
--to=inki.dae@samsung.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gustavo.padovan@collabora.co.uk \
--cc=gustavo@padovan.org \
--cc=jy0922.shim@samsung.com \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=tjakobi@math.uni-bielefeld.de \
/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