From nobody Thu Sep 19 23:06:45 2024 Received: from madrid.collaboradmins.com (madrid.collaboradmins.com [46.235.227.194]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id C8AB6524D6; Tue, 21 May 2024 07:57:30 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=46.235.227.194 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1716278252; cv=none; b=GL/K1sOthMQx1m2wrpXvkZnaNtA+uteDuhdNJZkoRBqMrtZJgY2JS+2WtvyTiu4lfasPUxjfVVJ7XhjdY5O6QrQsuY9shm2cOA178wN9zibo6ykwM5Ieq/7396YnigJvNtrd/jmmx9wdmNKOWP8QPw6EzC4Go5+7UvjEZcaU4i8= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1716278252; c=relaxed/simple; bh=gktLdBFpusJha20xG16h24yHbRR5VtJbfp03wVbROgY=; h=From:To:Cc:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version; b=hNIQ7i3LlV4c6GTqrTcszxL6ZMjn/aF7dmC2LMm3oA/gHc1JH1kKxn6YZQ34vsso9bOsuTHcYmVRU4qX9LCAtOEynDN6HF8JhpN8sxVZHDhzpv8D+9ZgA2XyUzbZWxXznYSIcjkOBD5uDQHuN9fAdGQmXVkioxN1Jjea8QfMBw8= ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=collabora.com; spf=pass smtp.mailfrom=collabora.com; dkim=pass (2048-bit key) header.d=collabora.com header.i=@collabora.com header.b=E9/YM9Y8; arc=none smtp.client-ip=46.235.227.194 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=collabora.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=collabora.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=collabora.com header.i=@collabora.com header.b="E9/YM9Y8" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=collabora.com; s=mail; t=1716278249; bh=gktLdBFpusJha20xG16h24yHbRR5VtJbfp03wVbROgY=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=E9/YM9Y8xNIXBYtjP6D2n5VKr6EklMb2Hh/Wh8UYXcsMdnbVoTSfcWMbzpkp04YWz WUg+5oBDSGJAeudowU9qpQblwBr3SfiQqJMk79lplIhuqxHzC8uTRmFsyQOi0gHZ9Y Fbj6iCZJEo7e1clPFeZ7dCbesxuJ6PdCeEr7aH/+58EgpUpJF679xD+8L1TDQ0297Y AjwEqwRE9GGob5zCjI+o0h5V7oDbPfmfb3a+teuhlRWrtevKCgQqbAxgtkUXAedhOv PV6aNi4j9DLrWSn3PvedFccayPUBEKOxXS+WWR4neURGelUA7IjJYbhNFUREUdMBU9 K2lW3uXxQEAzA== Received: from IcarusMOD.eternityproject.eu (cola.collaboradmins.com [195.201.22.229]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) (Authenticated sender: kholk11) by madrid.collaboradmins.com (Postfix) with ESMTPSA id D8AED378219B; Tue, 21 May 2024 07:57:27 +0000 (UTC) From: AngeloGioacchino Del Regno To: chunkuang.hu@kernel.org 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, angelogioacchino.delregno@collabora.com, shawn.sung@mediatek.com, yu-chang.lee@mediatek.com, ck.hu@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, Alexandre Mergnat Subject: [PATCH v5 2/3] dt-bindings: arm: mediatek: mmsys: Add OF graph support for board path Date: Tue, 21 May 2024 09:57:16 +0200 Message-ID: <20240521075717.50330-3-angelogioacchino.delregno@collabora.com> X-Mailer: git-send-email 2.45.1 In-Reply-To: <20240521075717.50330-1-angelogioacchino.delregno@collabora.com> References: <20240521075717.50330-1-angelogioacchino.delregno@collabora.com> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" Document OF graph on MMSYS/VDOSYS: this supports up to three DDP paths per HW instance (so potentially up to six displays for multi-vdo SoCs). The MMSYS or VDOSYS is always the first component in the DDP pipeline, so it only supports an output port with multiple endpoints - where each endpoint defines the starting point for one of the (currently three) possible hardware paths. Reviewed-by: Rob Herring (Arm) Reviewed-by: Alexandre Mergnat Tested-by: Alexandre Mergnat Signed-off-by: AngeloGioacchino Del Regno Reviewed-by: CK Hu --- .../bindings/arm/mediatek/mediatek,mmsys.yaml | 28 +++++++++++++++++++ 1 file changed, 28 insertions(+) diff --git a/Documentation/devicetree/bindings/arm/mediatek/mediatek,mmsys.= yaml b/Documentation/devicetree/bindings/arm/mediatek/mediatek,mmsys.yaml index b3c6888c1457..0ef67ca4122b 100644 --- a/Documentation/devicetree/bindings/arm/mediatek/mediatek,mmsys.yaml +++ b/Documentation/devicetree/bindings/arm/mediatek/mediatek,mmsys.yaml @@ -93,6 +93,34 @@ properties: '#reset-cells': const: 1 =20 + port: + $ref: /schemas/graph.yaml#/properties/port + description: + Output port node. This port connects the MMSYS/VDOSYS output to + the first component of one display pipeline, for example one of + the available OVL or RDMA blocks. + Some MediaTek SoCs support multiple display outputs per MMSYS. + properties: + endpoint@0: + $ref: /schemas/graph.yaml#/properties/endpoint + description: Output to the primary display pipeline + + endpoint@1: + $ref: /schemas/graph.yaml#/properties/endpoint + description: Output to the secondary display pipeline + + endpoint@2: + $ref: /schemas/graph.yaml#/properties/endpoint + description: Output to the tertiary display pipeline + + anyOf: + - required: + - endpoint@0 + - required: + - endpoint@1 + - required: + - endpoint@2 + required: - compatible - reg --=20 2.45.1