From: CK Hu <ck.hu@mediatek.com>
To: Dave Airlie <airlied@gmail.com>,
dri-devel@lists.freedesktop.org,
linux-mediatek@lists.infradead.org
Cc: Daniel Stone <daniels@collabora.com>, Stu Hsieh <stu.hsieh@mediatek.com>
Subject: [GIT PULL] mediatek drm next for 4.19
Date: Tue, 10 Jul 2018 14:34:42 +0800 [thread overview]
Message-ID: <1531204482.14433.6.camel@mtksdaap41> (raw)
Hi, Dave:
This include MT2712 SoC support and removing struct mtk_drm_fb.
Regards,
CK
The following changes since commit
ce397d215ccd07b8ae3f71db689aedb85d56ab40:
Linux 4.18-rc1 (2018-06-17 08:04:49 +0900)
are available in the git repository at:
https://github.com/ckhu-mediatek/linux.git-tags.git
mediatek-drm-next-4.19
for you to fetch changes up to 57c7f58111806faa0165b88155bff15679024122:
drm/mtk: mtk_drm_fb -> drm_framebuffer (2018-06-28 00:27:36 +0800)
----------------------------------------------------------------
CK Hu (1):
drm/mediatek: Split line to not over 80 characters
Daniel Stone (3):
drm/mtk: Remove impossible internal error
drm/mtk: Move GEM BO to drm_framebuffer
drm/mtk: mtk_drm_fb -> drm_framebuffer
stu.hsieh@mediatek.com (29):
drm/mediatek: update dt-bindings for mt2712
drm/mediatek: support maximum 64 mutex mod
drm/mediatek: add ddp component AAL1
drm/mediatek: add ddp component OD1
drm/mediatek: add ddp component PWM1
drm/mediatek: add ddp component PWM2
drm/mediatek: add component DPI1
drm/mediatek: add component DSI2
drm/mediatek: add component DSI3
drm/mediatek: add the DSI1 for component init condition
drm/mediatek: add connection from OD1 to RDMA1
drm/mediatek: Update the definition of connection from RDMA1 to
DPI0
drm/mediatek: add connection from RDMA0 to DPI0
drm/mediatek: add connection from RDMA0 to DSI2
drm/mediatek: add connection from RDMA0 to DSI3
drm/mediatek: add connection from RDMA1 to DPI1
drm/mediatek: add connection from RDMA1 to DSI1
drm/mediatek: add connection from RDMA1 to DSI2
drm/mediatek: add connection from RDMA1 to DSI3
drm/mediatek: add connection from RDMA2 to DPI0
drm/mediatek: add connection from RDMA2 to DPI1
drm/mediatek: add connection from RDMA2 to DSI1
drm/mediatek: add connection from RDMA2 to DSI2
drm/mediatek: add connection from RDMA2 to DSI3
drm/mediatek: add DPI1 support for mutex
drm/mediatek: add DSI2 support for mutex
drm/mediatek: add DSI3 support for mutex
drm/mediatek: add third ddp path
drm/mediatek: Add support for mediatek SOC MT2712
.../bindings/display/mediatek/mediatek,disp.txt | 2 +-
drivers/gpu/drm/mediatek/mtk_drm_crtc.c | 3 +
drivers/gpu/drm/mediatek/mtk_drm_ddp.c | 235
++++++++++++++++++---
drivers/gpu/drm/mediatek/mtk_drm_ddp_comp.c | 15 +-
drivers/gpu/drm/mediatek/mtk_drm_ddp_comp.h | 10 +-
drivers/gpu/drm/mediatek/mtk_drm_drv.c | 102 +++++++--
drivers/gpu/drm/mediatek/mtk_drm_drv.h | 5 +-
drivers/gpu/drm/mediatek/mtk_drm_fb.c | 76 ++-----
drivers/gpu/drm/mediatek/mtk_drm_fb.h | 1 -
drivers/gpu/drm/mediatek/mtk_drm_plane.c | 7 +-
10 files changed, 330 insertions(+), 126 deletions(-)
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
reply other threads:[~2018-07-10 6:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1531204482.14433.6.camel@mtksdaap41 \
--to=ck.hu@mediatek.com \
--cc=airlied@gmail.com \
--cc=daniels@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=stu.hsieh@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