Re: [PATCH v3 0/9] Add platform supports to MediaTek MT8188 SoC (part 2)

[AngeloGioacchino Del Regno]

Il 04/10/24 10:11, Fei Shao ha scritto:
> Hi all,
>
> This series is based on top of my previous "Add platform supports to
> MediaTek MT8188 SoC" v3 series[*].
>
> There's nothing to change or address in that series at the point of
> writing, so I decided not to resend it and start this new "part 2"
> series instead.
> (if I need to update both series next time I might consider merging them
> into one)
>
> Specifically, this continues to introduce the following platform supports
> in MediaTek MT8188 SoC to lay the groundwork for the board device trees:
> - PCIe
> - MIPI DSI
> - video decoder and encoder
> - JPEG decoder and encoder
> - vdosys0 and vdosys1 display pipelines
> - DP-INTF
> - eDP and DP TX
> - aliases
>
> Please have a look and feedback are welcome, thanks.
>
> [*]: https://lore.kernel.org/all/20240911143429.850071-1-fshao@xxxxxxxxxxxx/
> [v1]: https://lore.kernel.org/all/20241002114614.847553-1-fshao@xxxxxxxxxxxx/
> [v2]: https://lore.kernel.org/all/20241003070139.1461472-1-fshao@xxxxxxxxxxxx/
>
> Regards,
> Fei
>
> Changes in v3:
> - add the secondary MIPI DSI
>
> Changes in v2:
> - add linux,pci-domain to PCIe node
> - add power domain to PCIe PHY node
>
> Fei Shao (9):
>    arm64: dts: mediatek: mt8188: Assign GCE aliases
>    arm64: dts: mediatek: mt8188: Add PCIe nodes
>    arm64: dts: mediatek: mt8188: Add MIPI DSI nodes
>    arm64: dts: mediatek: mt8188: Add video decoder and encoder nodes
>    arm64: dts: mediatek: mt8188: Add JPEG decoder and encoder nodes
>    arm64: dts: mediatek: mt8188: Add display nodes for vdosys0
>    arm64: dts: mediatek: mt8188: Add display nodes for vdosys1
>    arm64: dts: mediatek: mt8188: Add DP-INTF nodes
>    arm64: dts: mediatek: mt8188: Add eDP and DP TX nodes
>
>   arch/arm64/boot/dts/mediatek/mt8188.dtsi | 668 +++++++++++++++++++++++
>   1 file changed, 668 insertions(+)

Whole series is

Reviewed-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@xxxxxxxxxxxxx>