For previous MediaTek SoCs, such as MT8173, there are 2 display HW pipelines binding to 1 mmsys with the same power domain, the same clock driver and the same mediatek-drm driver. For MT8195, VDOSYS0 and VDOSYS1 are 2 display HW pipelines binding to 2 different power domains, different clock drivers and different mediatek-drm drivers. Moreover, Hardware pipeline of VDOSYS0 has these components: COLOR, CCORR, AAL, GAMMA, DITHER. They are related to the PQ (Picture Quality) and they makes VDOSYS0 supports PQ function while they are not including in VDOSYS1. Hardware pipeline of VDOSYS1 has the component ETHDR (HDR related component). It makes VDOSYS1 supports the HDR function while it's not including in VDOSYS0. To summarize0: Only VDOSYS0 can support PQ adjustment. Only VDOSYS1 can support HDR adjustment. Therefore, we need to separate these two different mmsys hardwares to 2 different compatibles for MT8195. --- Change in v3: 1. Keep the original compatible "mediatek,mt8195-mmsys" and add "mediatek,mt8195-vdosys0" into the same item to make the tree fallback compatible. Change in v2: 1. Remove Ack tag in the first patch 2. Change the compatible name changing patch to one revert patch and one add vdosys0 support patch. --- Jason-JH.Lin (6): dt-bindings: arm: mediatek: mmsys: change compatible for MT8195 Revert "soc: mediatek: add mtk-mmsys support for mt8195 vdosys0" soc: mediatek: add mtk-mmsys support for mt8195 vdosys0 Revert "drm/mediatek: Add mediatek-drm of vdosys0 support for mt8195" drm/mediatek: add mediatek-drm of vdosys0 support for mt8195 soc: mediatek: remove DDP_DOMPONENT_DITHER from enum .../bindings/arm/mediatek/mediatek,mmsys.yaml | 4 + drivers/gpu/drm/mediatek/mtk_disp_rdma.c | 6 + drivers/gpu/drm/mediatek/mtk_drm_drv.c | 128 ++-------------- drivers/gpu/drm/mediatek/mtk_drm_drv.h | 6 - drivers/soc/mediatek/mtk-mmsys.c | 145 ++---------------- drivers/soc/mediatek/mtk-mmsys.h | 6 - include/linux/soc/mediatek/mtk-mmsys.h | 3 +- 7 files changed, 37 insertions(+), 261 deletions(-) -- 2.18.0
