From: Matthias Brugger <matthias.bgg@gmail.com>
To: YT Shen <yt.shen@mediatek.com>,
dri-devel@lists.freedesktop.org,
Philipp Zabel <p.zabel@pengutronix.de>
Cc: David Airlie <airlied@linux.ie>,
Daniel Kurtz <djkurtz@chromium.org>,
Mao Huang <littlecvr@chromium.org>, CK Hu <ck.hu@mediatek.com>,
Bibby Hsieh <bibby.hsieh@mediatek.com>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Thierry Reding <thierry.reding@gmail.com>,
Jie Qiu <jie.qiu@mediatek.com>,
Maxime Ripard <maxime.ripard@free-electrons.com>,
Chris Wilson <chris@chris-wilson.co.uk>,
shaoming chen <shaoming.chen@mediatek.com>,
Jitao Shi <jitao.shi@mediatek.com>,
Boris Brezillon <boris.brezillon@free-electrons.com>,
Dan Carpenter <dan.carpenter@oracle.com>,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org,
srv_heupstream@mediatek.com, Sascha Hauer <kernel@pengutronix.de>,
yingjoe.chen@mediatek.com, emil.l.velikov
Subject: Re: [PATCH v10 13/13] drm/mediatek: add support for Mediatek SoC MT2701
Date: Wed, 30 Nov 2016 15:03:04 +0100 [thread overview]
Message-ID: <1be9b66b-eff2-4232-fe17-5d1735999d0b@gmail.com> (raw)
In-Reply-To: <1480070076-6196-14-git-send-email-yt.shen@mediatek.com>
On 25/11/16 11:34, YT Shen wrote:
> static const struct of_device_id mtk_disp_rdma_driver_dt_match[] = {
> + { .compatible = "mediatek,mt2701-disp-rdma",
> + .data = &mt2701_rdma_driver_data},
> { .compatible = "mediatek,mt8173-disp-rdma",
> .data = &mt8173_rdma_driver_data},
> {},
[...]
> static const struct of_device_id ddp_driver_dt_match[] = {
> + { .compatible = "mediatek,mt2701-disp-mutex", .data = mt2701_mutex_mod},
> { .compatible = "mediatek,mt8173-disp-mutex", .data = mt8173_mutex_mod},
> {},
> };
[...]
>
> static const struct of_device_id mtk_disp_color_driver_dt_match[] = {
> + { .compatible = "mediatek,mt2701-disp-color",
> + .data = &mt2701_color_driver_data},
> { .compatible = "mediatek,mt8173-disp-color",
> .data = &mt8173_color_driver_data},
> {},
[...]
> static const struct of_device_id mtk_drm_of_ids[] = {
> + { .compatible = "mediatek,mt2701-mmsys",
> + .data = &mt2701_mmsys_driver_data},
> { .compatible = "mediatek,mt8173-mmsys",
> .data = &mt8173_mmsys_driver_data},
> { }
> diff --git a/drivers/gpu/drm/mediatek/mtk_dsi.c b/drivers/gpu/drm/mediatek/mtk_dsi.c
> index 0569f2e..f63cc91 100644
> --- a/drivers/gpu/drm/mediatek/mtk_dsi.c
> +++ b/drivers/gpu/drm/mediatek/mtk_dsi.c
> @@ -1203,6 +1203,7 @@ static int mtk_dsi_remove(struct platform_device *pdev)
> }
>
> static const struct of_device_id mtk_dsi_of_match[] = {
> + { .compatible = "mediatek,mt2701-dsi" },
> { .compatible = "mediatek,mt8173-dsi" },
> { },
> };
[...]
>
> static const struct of_device_id mtk_mipi_tx_match[] = {
> + { .compatible = "mediatek,mt2701-mipi-tx",
> + .data = &mt2701_mipitx_data },
> { .compatible = "mediatek,mt8173-mipi-tx",
> .data = &mt8173_mipitx_data },
> {},
I'm not sure if I missed some, but you should update the binding
description for newly added bindings.
Thanks a lot,
Matthias
next prev parent reply other threads:[~2016-11-30 14:03 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-25 10:34 [PATCH v10 00/13] MT2701 DRM support YT Shen
2016-11-25 10:34 ` [PATCH v10 01/13] drm/mediatek: add helpers for coverting from the generic components YT Shen
2016-11-25 10:34 ` [PATCH v10 02/13] drm/mediatek: add *driver_data for different hardware settings YT Shen
2016-11-30 6:42 ` Daniel Kurtz
2016-12-05 12:50 ` YT Shen
2016-11-25 10:34 ` [PATCH v10 03/13] drm/mediatek: add shadow register support YT Shen
2016-11-25 10:34 ` [PATCH v10 04/13] drm/mediatek: add BLS component YT Shen
2016-11-25 10:34 ` [PATCH v10 05/13] drm/mediatek: update display module connections YT Shen
2016-11-25 10:34 ` [PATCH v10 06/13] drm/mediatek: cleaning up and refine YT Shen
2016-11-25 10:34 ` [PATCH v10 07/13] drm/mediatek: add dsi interrupt control YT Shen
2016-11-25 10:34 ` [PATCH v10 08/13] drm/mediatek: add dsi transfer function YT Shen
2016-11-25 10:34 ` [PATCH v10 09/13] drm/mediatek: add mipi_tx data rate check YT Shen
2016-11-30 11:05 ` CK Hu
2016-11-25 10:34 ` [PATCH v10 10/13] drm/mediatek: add dsi ulp mode control YT Shen
2016-12-01 1:10 ` CK Hu
2016-11-25 10:34 ` [PATCH v10 11/13] drm/mediatek: add dsi rxtx control YT Shen
2016-11-30 10:47 ` CK Hu
2016-11-25 10:34 ` [PATCH v10 12/13] drm/mediatek: update DSI sub driver flow for sending commands to panel YT Shen
2016-11-30 7:58 ` CK Hu
2016-12-05 12:43 ` YT Shen
2016-11-25 10:34 ` [PATCH v10 13/13] drm/mediatek: add support for Mediatek SoC MT2701 YT Shen
2016-11-30 14:03 ` Matthias Brugger [this message]
2016-12-05 13:01 ` YT Shen
2016-11-30 8:59 ` [PATCH v10 00/13] MT2701 DRM support 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=1be9b66b-eff2-4232-fe17-5d1735999d0b@gmail.com \
--to=matthias.bgg@gmail.com \
--cc=airlied@linux.ie \
--cc=bibby.hsieh@mediatek.com \
--cc=boris.brezillon@free-electrons.com \
--cc=chris@chris-wilson.co.uk \
--cc=ck.hu@mediatek.com \
--cc=dan.carpenter@oracle.com \
--cc=daniel.vetter@ffwll.ch \
--cc=djkurtz@chromium.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jie.qiu@mediatek.com \
--cc=jitao.shi@mediatek.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=littlecvr@chromium.org \
--cc=maxime.ripard@free-electrons.com \
--cc=p.zabel@pengutronix.de \
--cc=shaoming.chen@mediatek.com \
--cc=srv_heupstream@mediatek.com \
--cc=thierry.reding@gmail.com \
--cc=yingjoe.chen@mediatek.com \
--cc=yt.shen@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;
as well as URLs for NNTP newsgroup(s).