[PATCH 01/38] dt-bindings: display: mediatek: dpi: Allow specifying resets
Chen-Yu Tsai
wenst at chromium.org
Thu Jul 24 09:16:21 UTC 2025
On Thu, Jul 24, 2025 at 4:39 PM AngeloGioacchino Del Regno
<angelogioacchino.delregno at collabora.com> wrote:
>
> Even though the DPI IP has a reset bit on all MediaTek SoCs, it
> is optional, and has always been unused until MT8195; specifically:
> on older SoCs, like MT8173, the reset bit is located in MMSYS, and
> on newer SoCs, like MT8195, it is located in VDOSYS.
>
> For this reason, allow specifying the resets and reset-names on
> all MediaTek SoCs.
>
> Those properties are optional because there are multiple ways to
> reset this IP and the reset lines in MM/VDO are used only if the
> IP cannot perform warm-reset.
>
> Signed-off-by: AngeloGioacchino Del Regno <angelogioacchino.delregno at collabora.com>
> ---
> .../devicetree/bindings/display/mediatek/mediatek,dpi.yaml | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/display/mediatek/mediatek,dpi.yaml b/Documentation/devicetree/bindings/display/mediatek/mediatek,dpi.yaml
> index b659d79393a8..eb4f276e8dc4 100644
> --- a/Documentation/devicetree/bindings/display/mediatek/mediatek,dpi.yaml
> +++ b/Documentation/devicetree/bindings/display/mediatek/mediatek,dpi.yaml
> @@ -102,6 +102,13 @@ properties:
> - port at 0
> - port at 1
>
> + resets:
> + maxItems: 1
> +
> + reset-names:
> + items:
> + - const: dpi
> +
Do we really need the name if there is only one though?
> required:
> - compatible
> - reg
> --
> 2.50.1
>
More information about the dri-devel
mailing list