From: Matthias Brugger <matthias.bgg@gmail.com>
To: Moudy Ho <moudy.ho@mediatek.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, linux-clk@vger.kernel.org,
Project_Global_Chrome_Upstream_Group@mediatek.com
Subject: Re: [PATCH v7 0/6] add support for MT8195 VPPSYS on MMSYS and MUTEX
Date: Mon, 6 Feb 2023 19:23:39 +0100 [thread overview]
Message-ID: <a94c9b8c-d439-b633-d02a-09d36bc11ad9@gmail.com> (raw)
In-Reply-To: <20230206091109.1324-1-moudy.ho@mediatek.com>
Whole series queued, thanks!
Matthias
On 06/02/2023 10:11, Moudy Ho wrote:
> Changes since v6:
> - Rebase on linux-next.
> - For MMSYS api changes, fix corresponding functionality in [4/6] patch.
>
> Changes since v5:
> - Depend on :
> [1] https://patchwork.kernel.org/project/linux-mediatek/list/?series=713031
>
> Changes since v4:
> - Rebase on linux-next.
> - Remove MMSYS fallback compatible.
> - Migrate MT8195 VPPSYS0/1 from clock to mtk-mmsys driver.
>
> Changes since v3:
> - Rebase on linux-next.
>
> Changes since v2:
> - Depend on :
> [1] https://patchwork.kernel.org/project/linux-mediatek/list/?series=681097
> - Split dts settings into two patches based on belonging to MMSYS or MUTEX.
>
> Changes since v1:
> - Depend on :
> [1] https://patchwork.kernel.org/project/linux-mediatek/list/?series=681097
> - Add compatible names to VPPSYS0 and VPPSYS1 in MMSYS binding file.
> - Fix VPPSYS's MMSYS and MUTEX dts to pass the dtsb_check.
> - Rename mtk_mmsys_merge_config() and mtk_mmsys_rsz_dcm_config() to
> mtk_mmsys_vpp_rsz_merge_config() and mtk_mmsys_vpp_rsz_dcm_config().
> - Clean up mtk_mmsys_vpp_rsz_dcm_config().
> - Add a comment to mtk_mutex_write_mod() and clean it up for use in more
> than 32 mods.
>
> Hi,
>
> This series add support for MT8195's two VPPSYS(Video Processor Pipe Subsystem),
> under which there will be corresponding MMSYS and MUTEX settings that
> need to be configured.
>
> Moudy Ho (1):
> arm64: dts: mediatek: mt8195: add MUTEX configuration for VPPSYS
>
> Roy-CW.Yeh (5):
> dt-bindings: soc: mediatek: Add support for MT8195 VPPSYS
> arm64: dts: mediatek: mt8195: add MMSYS configuration for VPPSYS
> soc: mediatek: mmsys: add config api for RSZ switching and DCM
> soc: mediatek: mutex: Add mtk_mutex_set_mod support to set MOD1
> soc: mediatek: mutex: support MT8195 VPPSYS
>
> .../bindings/soc/mediatek/mediatek,mutex.yaml | 1 +
> arch/arm64/boot/dts/mediatek/mt8195.dtsi | 26 +++-
> drivers/soc/mediatek/mt8195-mmsys.h | 13 ++
> drivers/soc/mediatek/mtk-mmsys.c | 44 ++++++
> drivers/soc/mediatek/mtk-mutex.c | 135 +++++++++++++++++-
> include/linux/soc/mediatek/mtk-mmsys.h | 6 +
> include/linux/soc/mediatek/mtk-mutex.h | 35 +++++
> 7 files changed, 249 insertions(+), 11 deletions(-)
>
prev parent reply other threads:[~2023-02-06 18:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-06 9:11 [PATCH v7 0/6] add support for MT8195 VPPSYS on MMSYS and MUTEX Moudy Ho
2023-02-06 9:11 ` [PATCH v7 3/6] arm64: dts: mediatek: mt8195: add MUTEX configuration for VPPSYS Moudy Ho
2023-02-06 11:14 ` Chen-Yu Tsai
[not found] ` <20230206091109.1324-3-moudy.ho@mediatek.com>
2023-02-06 11:12 ` [PATCH v7 2/6] arm64: dts: mediatek: mt8195: add MMSYS " Chen-Yu Tsai
[not found] ` <20230206091109.1324-6-moudy.ho@mediatek.com>
2023-02-06 11:17 ` [PATCH v7 5/6] soc: mediatek: mutex: Add mtk_mutex_set_mod support to set MOD1 Chen-Yu Tsai
2023-02-06 18:23 ` Matthias Brugger [this message]
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=a94c9b8c-d439-b633-d02a-09d36bc11ad9@gmail.com \
--to=matthias.bgg@gmail.com \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=moudy.ho@mediatek.com \
--cc=mturquette@baylibre.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@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).