From: Moudy Ho <moudy.ho@mediatek.com>
To: Mauro Carvalho Chehab <mchehab@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
Hans Verkuil <hverkuil-cisco@xs4all.nl>
Cc: Chun-Kuang Hu <chunkuang.hu@kernel.org>,
<linux-media@vger.kernel.org>,
<linux-mediatek@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
<Project_Global_Chrome_Upstream_Group@mediatek.com>,
Moudy Ho <moudy.ho@mediatek.com>
Subject: [PATCH v1 0/6] Add support for multiple chips
Date: Fri, 7 Oct 2022 11:17:31 +0800 [thread overview]
Message-ID: <20221007031737.5125-1-moudy.ho@mediatek.com> (raw)
Hi,
This series are based on following series:
MDP3:
[1] https://patchwork.kernel.org/project/linux-mediatek/list/?series=682204
[2] https://patchwork.kernel.org/project/linux-mediatek/list/?series=682891
[3] https://patchwork.kernel.org/project/linux-mediatek/list/?series=683526
To support multiple chips, a chip configuration header file needs to be created
and the relevant information split and moved into it.
Moudy Ho (6):
media: platform: mtk-mdp3: add chip configuration header file
media: platform: mtk-mdp3: chip config split about component settings
media: platform: mtk-mdp3: chip config split about subcomponents
media: platform: mtk-mdp3: chip config split about color format
media: platform: mtk-mdp3: chip config split about resolution
limitations
media: platform: mtk-mdp3: chip config split about pipe info
.../media/platform/mediatek/mdp3/mt8183_mdp.h | 409 ++++++++++++++++++
.../platform/mediatek/mdp3/mtk-mdp3-cmdq.c | 42 +-
.../platform/mediatek/mdp3/mtk-mdp3-comp.c | 160 ++++---
.../platform/mediatek/mdp3/mtk-mdp3-comp.h | 24 +-
.../platform/mediatek/mdp3/mtk-mdp3-core.c | 48 +-
.../platform/mediatek/mdp3/mtk-mdp3-core.h | 13 +
.../platform/mediatek/mdp3/mtk-mdp3-m2m.c | 10 +-
.../platform/mediatek/mdp3/mtk-mdp3-regs.c | 283 +-----------
.../platform/mediatek/mdp3/mtk-mdp3-regs.h | 7 +-
9 files changed, 603 insertions(+), 393 deletions(-)
create mode 100644 drivers/media/platform/mediatek/mdp3/mt8183_mdp.h
--
2.18.0
next reply other threads:[~2022-10-07 3:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-07 3:17 Moudy Ho [this message]
2022-10-07 3:17 ` [PATCH v1 1/6] media: platform: mtk-mdp3: add chip configuration header file Moudy Ho
2022-10-07 9:07 ` AngeloGioacchino Del Regno
2022-10-11 2:02 ` moudy ho
2022-10-07 3:17 ` [PATCH v1 2/6] media: platform: mtk-mdp3: chip config split about component settings Moudy Ho
2022-10-07 3:17 ` [PATCH v1 3/6] media: platform: mtk-mdp3: chip config split about subcomponents Moudy Ho
2022-10-07 3:17 ` [PATCH v1 4/6] media: platform: mtk-mdp3: chip config split about color format Moudy Ho
2022-10-07 3:17 ` [PATCH v1 5/6] media: platform: mtk-mdp3: chip config split about resolution limitations Moudy Ho
2022-10-07 3:17 ` [PATCH v1 6/6] media: platform: mtk-mdp3: chip config split about pipe info Moudy Ho
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=20221007031737.5125-1-moudy.ho@mediatek.com \
--to=moudy.ho@mediatek.com \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=chunkuang.hu@kernel.org \
--cc=hverkuil-cisco@xs4all.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=mchehab@kernel.org \
/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).