public inbox for linux-mediatek@lists.infradead.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: CK Hu <ck.hu@mediatek.com>
Cc: dri-devel@lists.freedesktop.org,
	linux-mediatek@lists.infradead.org,
	Yongqiang Niu <yongqiang.niu@mediatek.com>,
	Hsin-Yi Wang <hsinyi@chromium.org>,
	Daniel Vetter <daniel.vetter@intel.com>
Subject: Re: [GIT,PULL] mediatek drm fixes for 5.2
Date: Wed, 12 Jun 2019 18:25:38 +0200	[thread overview]
Message-ID: <20190612162538.GA8035@phenom.ffwll.local> (raw)
In-Reply-To: <1560325868.3259.6.camel@mtksdaap41>

On Wed, Jun 12, 2019 at 03:51:08PM +0800, CK Hu wrote:
> Hi Dave, Daniel:
> 
> This include unbind error fix, clock control flow refinement, and PRIME
> mmap with page offset.
> 
> Regards,
> CK
> 
> The following changes since commit
> a188339ca5a396acc588e5851ed7e19f66b0ebd9:
> 
>   Linux 5.2-rc1 (2019-05-19 15:47:09 -0700)
> 
> are available in the Git repository at:
> 
>   https://github.com/ckhu-mediatek/linux.git-tags.git
> mediatek-drm-fixes-5.2

For next time around, please make this a signed annotated tag. annotated
because then it's less typing for me, and signed because it's on a server
we don't necessarily trust.

> 
> for you to fetch changes up to 2458d9d6d94be982b917e93c61a89b4426f32e31:
> 
>   drm/mediatek: call mtk_dsi_stop() after mtk_drm_crtc_atomic_disable()
> (2019-06-04 09:54:42 +0800)
> 
> ----------------------------------------------------------------
> Hsin-Yi Wang (5):
>       drm/mediatek: fix unbind functions
>       drm/mediatek: unbind components in mtk_drm_unbind()
>       drm/mediatek: call drm_atomic_helper_shutdown() when unbinding
> driver
>       drm/mediatek: clear num_pipes when unbind driver
>       drm/mediatek: call mtk_dsi_stop() after
> mtk_drm_crtc_atomic_disable()
> 
> Yongqiang Niu (2):
>       drm/mediatek: adjust ddp clock control flow
>       drm/mediatek: respect page offset for PRIME mmap calls

You might want to look into all the recently added helpers for mmap, I
don't think mtk does anything special here.


> 
>  drivers/gpu/drm/mediatek/mtk_drm_crtc.c | 30
> ++++++------------------------
>  drivers/gpu/drm/mediatek/mtk_drm_drv.c  |  8 +++-----
>  drivers/gpu/drm/mediatek/mtk_drm_gem.c  |  7 ++++++-
>  drivers/gpu/drm/mediatek/mtk_dsi.c      | 12 +++++++++++-
>  4 files changed, 26 insertions(+), 31 deletions(-)

Pulled, thanks.
-Daniel

> 
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dri-devel

-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2019-06-12 16:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-12  7:51 [GIT,PULL] mediatek drm fixes for 5.2 CK Hu
2019-06-12 16:25 ` Daniel Vetter [this message]
2019-06-13  6:31   ` CK Hu
2019-06-13  8:27     ` Daniel Vetter
2019-06-14  2:06       ` CK Hu

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=20190612162538.GA8035@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=ck.hu@mediatek.com \
    --cc=daniel.vetter@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=hsinyi@chromium.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=yongqiang.niu@mediatek.com \
    /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