From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id EED48C4451C for ; Sat, 18 Jul 2026 11:18:06 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:MIME-Version:References:In-Reply-To: Message-ID:Date:Subject:Cc:To:From:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=25m79zY0amcHoy4L3akcyWE+hKTNBmRZA84asNN5Hx8=; b=sTKm8tR2qmBES4 egZ+QLgkSKif3ZSlPeyeSXvekpRu4MxtAnhp02jLIEOuM5YRRnJUt1Mc/VKvZjo3OufX9VULD51tF a/pJuKwcV7FOfAKbNF0z/smJn9lrvmVcg2aRiwCVazEvaa1jH9KgTsPRaDTtMyuXsE+gE/BJVFyF6 cS7BfEM5jFVmBuiUdayhj2bF0TMVDQBk0/YI/xm1g1SxXz3/rBkyHLG7cTWBqjr44vVK+NHrd5VKY waEMs4QojMFqyVZiF+fSxteiDOUE4ezKZNV8QkM7a6DnEIi2ypxqRWFK0XuMIapFkcdhLlaA+skTZ JblnQYm+BGhSS9/wilOQ==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.99.1 #2 (Red Hat Linux)) id 1wl33V-000000042lK-0hTM; Sat, 18 Jul 2026 11:18:05 +0000 Received: from out-174.mta1.migadu.com ([95.215.58.174]) by bombadil.infradead.org with esmtps (Exim 4.99.1 #2 (Red Hat Linux)) id 1wl33O-000000042iX-2aLn for linux-amlogic@lists.infradead.org; Sat, 18 Jul 2026 11:18:00 +0000 X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mieulab.com; s=key1; t=1784373476; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=s0L/CvyUhmFHnr8ZdmxcBtUe6vtszqB/KJYG8quybbM=; b=dDvWpZ9C5oZyJar+uUTs4hmEtNIhJMTY6rjb6zyg3K7IDsgqkeaqozlMLWsBBPFAD41QJ8 FTzb3xhfF7CNK2ktGMMIzOCaP03q/LiLBoAFueIozDdt+l9FYq7s7rJ2xzk4Onhe++PZR1 5og3NPL+dwVeB3t0HoLgIxrxeDW/a5xsnQnO5OCKu5Z1NKG+2G1A8kbdwKMnpes6k3nFBx xENiHUDdkjdSQ9drg6slecE+L+/J13/2hsyhZqoE7pX6WXlq2jhGme9MLlNGlXKHU9qQKF 6NwkJw/L794RhfQ4NydNsGCtJRNJxc8LQQMUyxI0uuPf7FwteZYApm6kLnbJIQ== From: Zinan Zhou To: Neil Armstrong Cc: Zinan Zhou , Rob Herring , Krzysztof Kozlowski , Conor Dooley , Maarten Lankhorst , Maxime Ripard , Thomas Zimmermann , David Airlie , Simona Vetter , Kevin Hilman , Jerome Brunet , Martin Blumenstingl , dri-devel@lists.freedesktop.org, linux-amlogic@lists.infradead.org, devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org Subject: [RFC PATCH 1/2] dt-bindings: display: meson-dw-hdmi: add GXLX2 compatible Date: Sat, 18 Jul 2026 20:15:26 +0900 Message-ID: <20260718111527.119231-2-zinan@mieulab.com> In-Reply-To: <20260718111527.119231-1-zinan@mieulab.com> References: <20260718111527.119231-1-zinan@mieulab.com> MIME-Version: 1.0 X-Migadu-Flow: FLOW_OUT X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.9.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20260718_041758_797783_1D1BF99D X-CRM114-Status: UNSURE ( 9.37 ) X-CRM114-Notice: Please train this message. X-BeenThere: linux-amlogic@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-amlogic" Errors-To: linux-amlogic-bounces+linux-amlogic=archiver.kernel.org@lists.infradead.org The GXLX2 HDMI transmitter uses the byte-addressed DesignWare controller registers and directly mapped TOP window also present on G12A. Its display pipeline and HDMI PHY programming remain GXL-like, however. Add a dedicated compatible with no fallback. The generic meson-gx-dw-hdmi interface uses indirect address/data registers and cannot operate this hardware, while meson-g12a-dw-hdmi would select incompatible PHY initialization values. The one-resource representation is proposed for RFC review; DWC and TOP occupy one contiguous MMIO range on the tested HG680-LC. Assisted-by: Codex:gpt-5.6-sol Signed-off-by: Zinan Zhou --- .../devicetree/bindings/display/amlogic,meson-dw-hdmi.yaml | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/Documentation/devicetree/bindings/display/amlogic,meson-dw-hdmi.yaml b/Documentation/devicetree/bindings/display/amlogic,meson-dw-hdmi.yaml index 416fe263ac92..4a17eccabea9 100644 --- a/Documentation/devicetree/bindings/display/amlogic,meson-dw-hdmi.yaml +++ b/Documentation/devicetree/bindings/display/amlogic,meson-dw-hdmi.yaml @@ -29,8 +29,10 @@ description: | The HDMI TOP block only supports HPD sensing. The Synopsys HDMI Controller interrupt is routed through the TOP Block interrupt. - Communication to the TOP Block and the Synopsys HDMI Controller is done - via a pair of dedicated addr+read/write registers. + Communication with the TOP Block and the Synopsys HDMI Controller uses a pair + of dedicated address/data registers on GXBB, GXL and GXM. GXLX2 and G12A + instead expose byte-addressed controller registers and a directly mapped TOP + window. The HDMI PHY is configured by registers in the HHI register block. Pixel data arrives in "4:4:4" format from the VENC block and the VPU HDMI mux @@ -54,6 +56,7 @@ properties: - amlogic,meson-gxm-dw-hdmi # GXM (S912) - const: amlogic,meson-gx-dw-hdmi - enum: + - amlogic,meson-gxlx2-dw-hdmi # GXLX2 (S905L3) - amlogic,meson-g12a-dw-hdmi # G12A (S905X2, S905Y2, S905D2) reg: -- 2.43.0 _______________________________________________ linux-amlogic mailing list linux-amlogic@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-amlogic