From: Rex-BC Chen <rex-bc.chen@mediatek.com>
To: <chunkuang.hu@kernel.org>, <matthias.bgg@gmail.com>
Cc: <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-mediatek@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
<Project_Global_Chrome_Upstream_Group@mediatek.com>,
Rex-BC Chen <rex-bc.chen@mediatek.com>
Subject: [v4,PATCH 0/3] mt8183 dpi supports dual edge
Date: Tue, 25 May 2021 20:14:45 +0800 [thread overview]
Message-ID: <20210525121448.30075-1-rex-bc.chen@mediatek.com> (raw)
v4:
Use output_fmts to determine whether it is dual edge.
Rebase to v5.13-rc1
v3:
Modify clock rate for dual edge setting.
Add more bridge function.
v2:
Modify unused code
v1:
DPI can sample on falling, rising or both edge.
When DPI sample the data both rising and falling edge.
It can reduce half data io pins.
Rex-BC Chen (3):
drm/mediatek: dpi dual edge sample mode support
drm/mediatek: config driver data to support dual edge sample
drm/mediatek: dpi: add bus format negotiation
drivers/gpu/drm/mediatek/mtk_dpi.c | 112 +++++++++++++++++++++++++++--
1 file changed, 106 insertions(+), 6 deletions(-)
--
2.18.0
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2021-05-25 12:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-25 12:14 Rex-BC Chen [this message]
2021-05-25 12:14 ` [v4,PATCH 1/3] drm/mediatek: dpi dual edge sample mode support Rex-BC Chen
2021-05-26 0:01 ` Chun-Kuang Hu
2021-05-26 1:51 ` Rex-BC Chen
2021-05-26 2:44 ` Chun-Kuang Hu
2021-05-25 12:14 ` [v4, PATCH 2/3] drm/mediatek: config driver data to support dual edge sample Rex-BC Chen
2021-05-26 2:47 ` [v4,PATCH " Chun-Kuang Hu
2021-05-25 12:14 ` [v4,PATCH 3/3] drm/mediatek: dpi: add bus format negotiation Rex-BC Chen
2021-05-26 2:59 ` Chun-Kuang 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=20210525121448.30075-1-rex-bc.chen@mediatek.com \
--to=rex-bc.chen@mediatek.com \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=chunkuang.hu@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.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).