From: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
To: chunkuang.hu@kernel.org, ck.hu@mediatek.com
Cc: robh@kernel.org, krzysztof.kozlowski+dt@linaro.org,
conor+dt@kernel.org, p.zabel@pengutronix.de, airlied@gmail.com,
daniel@ffwll.ch, maarten.lankhorst@linux.intel.com,
mripard@kernel.org, tzimmermann@suse.de, matthias.bgg@gmail.com,
shawn.sung@mediatek.com, yu-chang.lee@mediatek.com,
jitao.shi@mediatek.com, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
linux-mediatek@lists.infradead.org,
linux-arm-kernel@lists.infradead.org, wenst@chromium.org,
kernel@collabora.com, sui.jingfeng@linux.dev, michael@walle.cc
Subject: Re: [PATCH v8 0/3] drm/mediatek: Add support for OF graphs
Date: Thu, 4 Jul 2024 10:29:15 +0200 [thread overview]
Message-ID: <eef10e9f-dac5-4a05-a79c-f8026f27f051@collabora.com> (raw)
In-Reply-To: <d84f1469-e82a-42de-94a0-8ee0da0cba02@collabora.com>
Il 19/06/24 12:56, AngeloGioacchino Del Regno ha scritto:
> Il 18/06/24 12:17, AngeloGioacchino Del Regno ha scritto:
>> Changes in v8:
>> - Rebased on next-20240617
>> - Changed to allow probing a VDO with no available display outputs
>>
>
> Hello CK,
>
> At the time of writing, this series was well reviewed and tested by multiple people
> on multiple SoCs and boards.
>
> We've got a bunch of series that are waiting for this to get upstreamed, including
> the addition of support for MT8365-EVK (already on mailing lists), MT8395 Radxa
> NIO 12L, MT8395 Kontron SBC i1200 (not on mailing lists yet, waiting for this to
> get merged), other than some other conversion commits for other MediaTek DTs from
> myself.
>
> As for the MT8195/NIO12L commits, I'm planning to send them on the lists tomorrow,
> along with some code to properly support devicetree overlays (DTBO) generation for
> MediaTek boards.
>
> Alexandre tested it on MT8365-EVK;
> Michael tested on Kontron SBC-i1200;
> I tested on Radxa NIO-12L, Cherry Tomato Chromebook, MT6795 Sony Xperia
> M5 (dsi video panel) smartphone and MT8192 Asurada Chromebook.
>
> So, is there anything else to address on this, or can we proceed?
>
Gentle ping
Regards,
Angelo
> Many thanks,
> Angelo
>
>> Changes in v7:
>> - Fix typo in patch 3/3
>>
>> Changes in v6:
>> - Added EPROBE_DEFER check to fix dsi/dpi false positive DT fallback case
>> - Dropped refcount of ep_out in mtk_drm_of_get_ddp_ep_cid()
>> - Fixed double refcount drop during path building
>> - Removed failure upon finding a DT-disabled path as requested
>> - Tested again on MT8195, MT8395 boards
>>
>> Changes in v5:
>> - Fixed commit [2/3], changed allOf -> anyOf to get the
>> intended allowance in the binding
>>
>> Changes in v4:
>> - Fixed a typo that caused pure OF graphs pipelines multiple
>> concurrent outputs to not get correctly parsed (port->id);
>> - Added OVL_ADAPTOR support for OF graph specified pipelines;
>> - Now tested with fully OF Graph specified pipelines on MT8195
>> Chromebooks and MT8395 boards;
>> - Rebased on next-20240516
>>
>> Changes in v3:
>> - Rebased on next-20240502 because of renames in mediatek-drm
>>
>> Changes in v2:
>> - Fixed wrong `required` block indentation in commit [2/3]
>>
>>
>> The display IPs in MediaTek SoCs are *VERY* flexible and those support
>> being interconnected with different instances of DDP IPs (for example,
>> merge0 or merge1) and/or with different DDP IPs (for example, rdma can
>> be connected with either color, dpi, dsi, merge, etc), forming a full
>> Display Data Path that ends with an actual display.
>>
>> This series was born because of an issue that I've found while enabling
>> support for MT8195/MT8395 boards with DSI output as main display: the
>> current mtk_drm_route variations would not work as currently, the driver
>> hardcodes a display path for Chromebooks, which have a DisplayPort panel
>> with DSC support, instead of a DSI panel without DSC support.
>>
>> There are other reasons for which I wrote this series, and I find that
>> hardcoding those paths - when a HW path is clearly board-specific - is
>> highly suboptimal. Also, let's not forget about keeping this driver from
>> becoming a huge list of paths for each combination of SoC->board->disp
>> and... this and that.
>>
>> For more information, please look at the commit description for each of
>> the commits included in this series.
>>
>> This series is essential to enable support for the MT8195/MT8395 EVK,
>> Kontron i1200, Radxa NIO-12L and, mainly, for non-Chromebook boards
>> and Chromebooks to co-exist without conflicts.
>>
>> Besides, this is also a valid option for MT8188 Chromebooks which might
>> have different DSI-or-eDP displays depending on the model (as far as I
>> can see from the mtk_drm_route attempt for this SoC that is already
>> present in this driver).
>>
>> This series was tested on MT8195 Cherry Tomato and on MT8395 Radxa
>> NIO-12L with both hardcoded paths, OF graph support and partially
>> hardcoded paths, and pure OF graph support including pipelines that
>> require OVL_ADAPTOR support.
>>
>> AngeloGioacchino Del Regno (3):
>> dt-bindings: display: mediatek: Add OF graph support for board path
>> dt-bindings: arm: mediatek: mmsys: Add OF graph support for board path
>> drm/mediatek: Implement OF graphs support for display paths
>>
>> .../bindings/arm/mediatek/mediatek,mmsys.yaml | 28 ++
>> .../display/mediatek/mediatek,aal.yaml | 40 +++
>> .../display/mediatek/mediatek,ccorr.yaml | 21 ++
>> .../display/mediatek/mediatek,color.yaml | 22 ++
>> .../display/mediatek/mediatek,dither.yaml | 22 ++
>> .../display/mediatek/mediatek,dpi.yaml | 25 +-
>> .../display/mediatek/mediatek,dsc.yaml | 24 ++
>> .../display/mediatek/mediatek,dsi.yaml | 27 +-
>> .../display/mediatek/mediatek,ethdr.yaml | 22 ++
>> .../display/mediatek/mediatek,gamma.yaml | 19 ++
>> .../display/mediatek/mediatek,merge.yaml | 23 ++
>> .../display/mediatek/mediatek,od.yaml | 22 ++
>> .../display/mediatek/mediatek,ovl-2l.yaml | 22 ++
>> .../display/mediatek/mediatek,ovl.yaml | 22 ++
>> .../display/mediatek/mediatek,postmask.yaml | 21 ++
>> .../display/mediatek/mediatek,rdma.yaml | 22 ++
>> .../display/mediatek/mediatek,ufoe.yaml | 21 ++
>> drivers/gpu/drm/mediatek/mtk_disp_drv.h | 1 +
>> .../gpu/drm/mediatek/mtk_disp_ovl_adaptor.c | 40 ++-
>> drivers/gpu/drm/mediatek/mtk_dpi.c | 21 +-
>> drivers/gpu/drm/mediatek/mtk_drm_drv.c | 291 ++++++++++++++++--
>> drivers/gpu/drm/mediatek/mtk_drm_drv.h | 2 +-
>> drivers/gpu/drm/mediatek/mtk_dsi.c | 14 +-
>> 23 files changed, 731 insertions(+), 41 deletions(-)
>>
>
>
next prev parent reply other threads:[~2024-07-04 8:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-18 10:17 AngeloGioacchino Del Regno
2024-06-18 10:17 ` [PATCH v8 1/3] dt-bindings: display: mediatek: Add OF graph support for board path AngeloGioacchino Del Regno
2024-08-07 5:26 ` CK Hu (胡俊光)
2024-08-08 3:45 ` CK Hu (胡俊光)
2024-09-10 8:08 ` AngeloGioacchino Del Regno
2024-06-18 10:17 ` [PATCH v8 2/3] dt-bindings: arm: mediatek: mmsys: " AngeloGioacchino Del Regno
2024-06-18 10:17 ` [PATCH v8 3/3] drm/mediatek: Implement OF graphs support for display paths AngeloGioacchino Del Regno
2024-06-18 12:08 ` Sui Jingfeng
2024-08-08 3:48 ` CK Hu (胡俊光)
2024-09-10 8:38 ` AngeloGioacchino Del Regno
2024-06-18 11:05 ` [PATCH v8 0/3] drm/mediatek: Add support for OF graphs Michael Walle
2024-06-19 10:56 ` AngeloGioacchino Del Regno
2024-07-04 8:29 ` AngeloGioacchino Del Regno [this message]
2024-07-11 9:24 ` Michael Walle
2024-08-19 7:43 ` Michael Walle
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=eef10e9f-dac5-4a05-a79c-f8026f27f051@collabora.com \
--to=angelogioacchino.delregno@collabora.com \
--cc=airlied@gmail.com \
--cc=chunkuang.hu@kernel.org \
--cc=ck.hu@mediatek.com \
--cc=conor+dt@kernel.org \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jitao.shi@mediatek.com \
--cc=kernel@collabora.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=matthias.bgg@gmail.com \
--cc=michael@walle.cc \
--cc=mripard@kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=robh@kernel.org \
--cc=shawn.sung@mediatek.com \
--cc=sui.jingfeng@linux.dev \
--cc=tzimmermann@suse.de \
--cc=wenst@chromium.org \
--cc=yu-chang.lee@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®