From: Enric Balletbo i Serra <enric.balletbo@collabora.com>
To: linux-kernel@vger.kernel.org
Cc: matthias.bgg@gmail.com, drinkcat@chromium.org,
hsinyi@chromium.org, weiyi.lu@mediatek.com,
Collabora Kernel ML <kernel@collabora.com>,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org
Subject: [PATCH v2 0/2] soc: mediatek: Prepare MMSYS for DDP routing using tables
Date: Wed, 17 Mar 2021 19:17:08 +0100 [thread overview]
Message-ID: <20210317181711.795245-1-enric.balletbo@collabora.com> (raw)
Dear all,
This is the second version of this series intended to prepare the
mtk-mmsys driver to allow different DDP (Data Display Path) routing
tables per SoC. Note that the series has been tested only on MT8173 platform,
for MT2701 and MT2712 based devices we're using a default routing table
that should just work.
Thanks,
Enric
Changes in v2:
- Use a default table for mt2701, mt2712 and mt8173.
- Remove the mask field from routes struct as is not needed.
CK Hu (2):
soc: mediatek: mmsys: Create struct mtk_mmsys to store context data
soc: mediatek: mmsys: Use an array for setting the routing registers
drivers/soc/mediatek/mtk-mmsys.c | 300 +++++--------------------------
drivers/soc/mediatek/mtk-mmsys.h | 215 ++++++++++++++++++++++
2 files changed, 257 insertions(+), 258 deletions(-)
create mode 100644 drivers/soc/mediatek/mtk-mmsys.h
--
2.30.2
next reply other threads:[~2021-03-17 18:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-17 18:17 Enric Balletbo i Serra [this message]
2021-03-17 18:17 ` [PATCH v2 1/2] soc: mediatek: mmsys: Create struct mtk_mmsys to store context data Enric Balletbo i Serra
2021-03-17 18:17 ` [PATCH v2 2/2] soc: mediatek: mmsys: Use an array for setting the routing registers Enric Balletbo i Serra
2021-03-30 9:10 ` [PATCH v2 0/2] soc: mediatek: Prepare MMSYS for DDP routing using tables Matthias Brugger
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=20210317181711.795245-1-enric.balletbo@collabora.com \
--to=enric.balletbo@collabora.com \
--cc=drinkcat@chromium.org \
--cc=hsinyi@chromium.org \
--cc=kernel@collabora.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=weiyi.lu@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
all inboxes | Powered by JetHome®