From mboxrd@z Thu Jan 1 00:00:00 1970 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 A7C9A12B141; Tue, 9 Apr 2024 12:02:20 +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=1712664142; cv=none; b=We2KSmzGwIEjOPS67vy5QoMlZwdaT4v8RhYivnCkonS8uNWXobUt/7A7hCbHPJlvdf7T6N9ewviPe6sflq9p+jY37IuXtkahupwrvF4M5luPgsxs6VBcewqj+7B9/vqhFGxv2L73FhG2yRh7hAQRWbJouKiyyGLgxwweMGE/NXw= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1712664142; c=relaxed/simple; bh=RnG3B99ztVcbahOk3drEuVbXdWqVnpm0upNaJDwbdkk=; h=From:To:Cc:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version; b=evKWeNYRT59RtendK5tPMEBe4t4pmklLnC+ILwNsQsvWom03qMeit8FbBg2xyDsxmaiZvPJbiNmdxBsfXlVNg+qjAz2JZ02UWKBu4gUbX/dpytrpXMn8HSy0meTmRgREDEeToFRH0Eacys125GCJ+7T9vE1n8LAIigj+l5AFNA4= 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=02LJsze6; 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="02LJsze6" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=collabora.com; s=mail; t=1712664138; bh=RnG3B99ztVcbahOk3drEuVbXdWqVnpm0upNaJDwbdkk=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=02LJsze6QLQiLv2EXVYreZKP76WUn0F+q/qMJJdJfXvMRPVGtoAM84t5KMtursmj3 FNPz60BB07Y6ukGV8s05Rtp8BQiIfbOaqbb0R+3/p00detYIKfhKaIRLumLwxy+e1W 8mOwENn1sLLOQaA5WABdCLB6S58wpyePPWaUJ+T/MBJN0ErQkqFIhyyYXIzHqMmk9b /DzgtYIK923+pmJ1wyqa1r3AF1/G/2GmtN1tcJvpywCc7BjShsy823jw/9GsjaVbc8 doF/6wQ7mXUKX8GhC18Ybk9+gE2eNZnsRDZRhBGGa902isXX/KwFqd0ivW0MWlJBbI WEHC0s/KK4R0Q== 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 7B52837820F8; Tue, 9 Apr 2024 12:02:17 +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 Subject: [PATCH v2 2/3] dt-bindings: arm: mediatek: mmsys: Add OF graph support for board path Date: Tue, 9 Apr 2024 14:02:10 +0200 Message-ID: <20240409120211.321153-3-angelogioacchino.delregno@collabora.com> X-Mailer: git-send-email 2.44.0 In-Reply-To: <20240409120211.321153-1-angelogioacchino.delregno@collabora.com> References: <20240409120211.321153-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: 8bit 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. Signed-off-by: AngeloGioacchino Del Regno --- .../bindings/arm/mediatek/mediatek,mmsys.yaml | 23 +++++++++++++++++++ 1 file changed, 23 insertions(+) diff --git a/Documentation/devicetree/bindings/arm/mediatek/mediatek,mmsys.yaml b/Documentation/devicetree/bindings/arm/mediatek/mediatek,mmsys.yaml index b3c6888c1457..4e9acd966aa5 100644 --- a/Documentation/devicetree/bindings/arm/mediatek/mediatek,mmsys.yaml +++ b/Documentation/devicetree/bindings/arm/mediatek/mediatek,mmsys.yaml @@ -93,6 +93,29 @@ properties: '#reset-cells': const: 1 + 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 up to three 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 + + required: + - endpoint@0 + required: - compatible - reg -- 2.44.0