Message ID | 20231222174220.55249-1-knaerzche@gmail.com |
---|---|
Headers |
Return-Path: <linux-kernel+bounces-9948-ouuuleilei=gmail.com@vger.kernel.org> Delivered-To: ouuuleilei@gmail.com Received: by 2002:a05:7300:2483:b0:fb:cd0c:d3e with SMTP id q3csp1222378dyi; Fri, 22 Dec 2023 09:42:57 -0800 (PST) X-Google-Smtp-Source: AGHT+IGWj7CB8P97mMPgci627lvmIWG7Wn/wXZ5i63yg2hc+ez4Z705fxdJlJvdP3+FCXA1pmRlU X-Received: by 2002:a05:6a00:6ca0:b0:6d9:844a:b69f with SMTP id jc32-20020a056a006ca000b006d9844ab69fmr1338834pfb.28.1703266977308; Fri, 22 Dec 2023 09:42:57 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1703266977; cv=none; d=google.com; s=arc-20160816; b=F5qANmoNcB5D85tjtiREUlyDX/nJA+7RWoTgTJ7499ywsCzoTrhRO+nptljGQwHMhb MAJ1B86/2a9rJleUKkvXMdG8pPU9ya7ew90KUVJk0L3sOoD37ENuApSNq/hV4xxDlQxB bvcBxDCXoQZGaDr1/GT8KJgKTEXSJVkfS6TxwAY3i500W1QogPHgwUzndewYjjb01GRW 08gmWBFyzPorDNxlarS3UbUpuutX3FZHHz9gnLtrWmTAY78lTpbyF/HsxZ3QANBYqIA6 v3y2O8PcpsS1FH3LsepNJ2CFR9SKAi4LooLbVRt9x4xiCVoFP4z4b2lmNdIn+iRq2sXK xF7g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=content-transfer-encoding:mime-version:list-unsubscribe :list-subscribe:list-id:precedence:message-id:date:subject:cc:to :from:dkim-signature; bh=hHFkedPmax7f2jMznqg0TqRbSWkPKtd98J+qp1ddTP0=; fh=k7ZhfSDxugAUNAX9PFQjqQnTRGZ+rgCl5CN8/TdzbyU=; b=QJV/k3TlJmo7hb71f4IQjVlXeBPfAHZzGUsg/N3UHayIE3i15Go4QFMTCD9rO7Ec0J yhQWo6lDZImOnE2zMVu5pqfTM6z8pBvqv7Xt3LtlOaa8CbAWtCU6ITE6g7x7fhCUr7tq HgdXdl5zaM9htgFVwXOavBuiZ2uajMIiJGQj6KmvMZ9QJQmmZtwJkLQtdWYbXErAlIN2 OktxwAled87XWGb5hfd2czAFfro6iK6a1HPmKLqTy8adVpd1x8MRSdtNlneF2kMVuJge oUjPP5EItM3B7tJEXsmQNNvHoy/9+Jmb7miW05VzNt28OwgJ6iVJiq2WuD6J1yilr+0P v1nQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20230601 header.b=eJlcUFZU; spf=pass (google.com: domain of linux-kernel+bounces-9948-ouuuleilei=gmail.com@vger.kernel.org designates 139.178.88.99 as permitted sender) smtp.mailfrom="linux-kernel+bounces-9948-ouuuleilei=gmail.com@vger.kernel.org"; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: from sv.mirrors.kernel.org (sv.mirrors.kernel.org. [139.178.88.99]) by mx.google.com with ESMTPS id b7-20020a056a000cc700b006d968d81513si3533725pfv.164.2023.12.22.09.42.57 for <ouuuleilei@gmail.com> (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 22 Dec 2023 09:42:57 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel+bounces-9948-ouuuleilei=gmail.com@vger.kernel.org designates 139.178.88.99 as permitted sender) client-ip=139.178.88.99; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20230601 header.b=eJlcUFZU; spf=pass (google.com: domain of linux-kernel+bounces-9948-ouuuleilei=gmail.com@vger.kernel.org designates 139.178.88.99 as permitted sender) smtp.mailfrom="linux-kernel+bounces-9948-ouuuleilei=gmail.com@vger.kernel.org"; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: from smtp.subspace.kernel.org (wormhole.subspace.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by sv.mirrors.kernel.org (Postfix) with ESMTPS id 10933286168 for <ouuuleilei@gmail.com>; Fri, 22 Dec 2023 17:42:57 +0000 (UTC) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by smtp.subspace.kernel.org (Postfix) with ESMTP id 944A12C1A6; Fri, 22 Dec 2023 17:42:27 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="eJlcUFZU" X-Original-To: linux-kernel@vger.kernel.org Received: from mail-wr1-f42.google.com (mail-wr1-f42.google.com [209.85.221.42]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 66B8C2C183; Fri, 22 Dec 2023 17:42:23 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=gmail.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=gmail.com Received: by mail-wr1-f42.google.com with SMTP id ffacd0b85a97d-336746a545fso1256567f8f.0; Fri, 22 Dec 2023 09:42:23 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1703266941; x=1703871741; darn=vger.kernel.org; h=content-transfer-encoding:mime-version:message-id:date:subject:cc :to:from:from:to:cc:subject:date:message-id:reply-to; bh=hHFkedPmax7f2jMznqg0TqRbSWkPKtd98J+qp1ddTP0=; b=eJlcUFZU6JBEX87MKg0HtKBkTmNXERGRsGuvW+FC/dFsC0rV/a9/5nqhcGvMObNcMt khNdirsnc4SJOFeQvvvtnRwH6P6Z33l8foHaWKanrvFi3v5UoiCKIrDYbJ/FLzOAzVXx arbX+irwcH9q2EFooTvqBeas+bVAXTdiTdVTUY0fHynDy34D27NdYOK/XpRtfbJPdbia gtSfqzN9oJScdilWgGksvGGDKHcOfEMHr29kraFKromrVSaIgPYV8FI41YK5PP0K1C5x uD+Oxyxv28WqEQVVnIQ3gYWGllaHAzvUpOYyq+6Mwc4SXxnDj9lVmshr5rlZHn25F/Sf jRjg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1703266941; x=1703871741; h=content-transfer-encoding:mime-version:message-id:date:subject:cc :to:from:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=hHFkedPmax7f2jMznqg0TqRbSWkPKtd98J+qp1ddTP0=; b=PkU05mCbkl/RyUB5icMaPma1nHkV8ledBIYepyIp4u3q3rg5ytFSySgHzn+mQCKpkf w0bphemlYHEI6hsvUeV4wFJwJ5kwNjCxiY/kCeFcSVuWtTugVDycYjeoanwJjvaX2Bz8 tKq3y0L5bu+eXowlIJWg3ywbQTx79G9A1vL5YAXztWgYw0BCmTCFmDEkoDxVpQ5Bieek pwCTMj1vaDNzfhfxdHbv3CvXPPKsS4/QIXocc+5C4EJ1v7hlmVwrPi74r1nLOUBX0xlB 6MpSxfX62ASSgEWvjzgMjfRZmtH0eHEXa5HOndpfdxf0KYvCt76W8PhY5F7HJ/ui6x4n k8Pg== X-Gm-Message-State: AOJu0YyFASZVqQ73k5l1mN+gySnGoqk4Pix2tiilaGLMW1JaHPObFmZq c9Iqd2JOiuOp0y88wpiLYg== X-Received: by 2002:a5d:6102:0:b0:336:5bc1:f53 with SMTP id v2-20020a5d6102000000b003365bc10f53mr1693282wrt.10.1703266941511; Fri, 22 Dec 2023 09:42:21 -0800 (PST) Received: from U4.lan ([2a02:810b:f40:4300:f3ae:2788:7e03:f44]) by smtp.gmail.com with ESMTPSA id w10-20020adfec4a000000b00336670abdcasm4777116wrn.40.2023.12.22.09.42.20 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 22 Dec 2023 09:42:21 -0800 (PST) From: Alex Bee <knaerzche@gmail.com> To: Sandy Huang <hjc@rock-chips.com>, =?utf-8?q?Heiko_St=C3=BCbner?= <heiko@sntech.de>, Maarten Lankhorst <maarten.lankhorst@linux.intel.com>, Maxime Ripard <mripard@kernel.org>, Thomas Zimmermann <tzimmermann@suse.de>, Rob Herring <robh+dt@kernel.org>, Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>, Conor Dooley <conor+dt@kernel.org> Cc: David Airlie <airlied@gmail.com>, Daniel Vetter <daniel@ffwll.ch>, dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org, Alex Bee <knaerzche@gmail.com> Subject: [PATCH v4 00/29] Add HDMI support for RK3128 Date: Fri, 22 Dec 2023 18:41:51 +0100 Message-ID: <20231222174220.55249-1-knaerzche@gmail.com> X-Mailer: git-send-email 2.43.0 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: <linux-kernel.vger.kernel.org> List-Subscribe: <mailto:linux-kernel+subscribe@vger.kernel.org> List-Unsubscribe: <mailto:linux-kernel+unsubscribe@vger.kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-getmail-retrieved-from-mailbox: INBOX X-GMAIL-THRID: 1786004874064796277 X-GMAIL-MSGID: 1786004874064796277 |
Series |
Add HDMI support for RK3128
|
|
Message
Alex Bee
Dec. 22, 2023, 5:41 p.m. UTC
This is version 4 of my series that aims to add support for the display controller (VOP) and the HDMI controller block of RK3128 (which is very similar to the one found in RK3036). The original intention of this series was to add support for this slightly different integration but is by now, driven by maintainer's feedback, exploded to be a rework of inno-hdmi driver in large parts. It is, however, a change for the better. The VOP part is very simple - everything we need for HDMI support is already there. I only needed to split the output selection registers from RK3036. The VOP has an IOMMU attached, but it has a serious silicon bug: Registers can only be written, but not be read. As it's not possible to use it with the IOMMU driver in it's current state I'm not adding it here and we have to live with CMA for now - which works fine also. I got response from the vendor, that there is no possibility to read the registers and an workaround must be implemented in software in order to use it. The inno-hdmi driver currently gets a lot of attention [0-2] and I'm hooking in now also. As requested I incorporated some of Maxime's series [0] (and tested them). I have intentionally not removed any code dealing with output format conversion in this series. In contrast to the input format, which is always RGB on this platform and certainly can be dropped, that can be implemented later. And secondly I need the conversion for RGB full range to RGB limited range for this series. I did also some smaller driver cleanups from my side and implemented a custom connector state which now holds the data that belongs there and it is not longer in the device structure and, of course, addressed the feedback from v1 [3] and v2 [4]. There hasn't been any feedback to v3[5] so far, but I fixed an issue with the new custom connector reset hook: If there is a connector state already it needs to be destroyed in there as well. Please see individual patches for detailed changelog. Note: Patches are based and tested on next-20231213. [0] https://lore.kernel.org/all/20231207-kms-hdmi-connector-state-v5-0-6538e19d634d@kernel.org [1] https://lore.kernel.org/all/20231204123315.28456-1-keith.zhao@starfivetech.com [2] https://lore.kernel.org/all/2601b669-c570-f39d-8cf9-bff56c939912@gmail.com [3] https://lore.kernel.org/all/20231213195125.212923-1-knaerzche@gmail.com/ [4] https://lore.kernel.org/all/20231216162639.125215-1-knaerzche@gmail.com/ [5] https://lore.kernel.org/all/20231219170100.188800-1-knaerzche@gmail.com/ Alex Bee (17): dt-bindings: display: rockchip,inno-hdmi: Document RK3128 compatible drm/rockchip: vop: Add output selection registers for RK312x drm/rockchip: inno_hdmi: Fix video timing drm/rockchip: inno_hdmi: Remove YUV-based csc coefficents drm/rockchip: inno_hdmi: Drop irq struct member drm/rockchip: inno_hdmi: Remove useless include drm/rockchip: inno_hdmi: Subclass connector state drm/rockchip: inno_hdmi: Correctly setup HDMI quantization range drm/rockchip: inno_hdmi: Don't power up the phy after resetting drm/rockchip: inno_hdmi: Split power mode setting drm/rockchip: inno_hdmi: Add variant support drm/rockchip: inno_hdmi: Add RK3128 support drm/rockchip: inno_hdmi: Add basic mode validation drm/rockchip: inno_hdmi: Drop custom fill_modes hook ARM: dts: rockchip: Add display subsystem for RK3128 ARM: dts: rockchip: Add HDMI node for RK3128 ARM: dts: rockchip: Enable HDMI output for XPI-3128 Maxime Ripard (12): drm/rockchip: inno_hdmi: Remove useless mode_fixup drm/rockchip: inno_hdmi: Remove useless copy of drm_display_mode drm/rockchip: inno_hdmi: Switch encoder hooks to atomic drm/rockchip: inno_hdmi: Get rid of mode_set drm/rockchip: inno_hdmi: no need to store vic drm/rockchip: inno_hdmi: Remove unneeded has audio flag drm/rockchip: inno_hdmi: Remove useless input format drm/rockchip: inno_hdmi: Remove tmds rate from structure drm/rockchip: inno_hdmi: Drop HDMI Vendor Infoframe support drm/rockchip: inno_hdmi: Move infoframe disable to separate function drm/rockchip: inno_hdmi: Switch to infoframe type drm/rockchip: inno_hdmi: Remove unused drm device pointer .../display/rockchip/rockchip,inno-hdmi.yaml | 40 +- .../arm/boot/dts/rockchip/rk3128-xpi-3128.dts | 29 + arch/arm/boot/dts/rockchip/rk3128.dtsi | 60 ++ drivers/gpu/drm/rockchip/inno_hdmi.c | 549 +++++++++++------- drivers/gpu/drm/rockchip/inno_hdmi.h | 5 - drivers/gpu/drm/rockchip/rockchip_vop_reg.c | 13 +- drivers/gpu/drm/rockchip/rockchip_vop_reg.h | 3 + 7 files changed, 484 insertions(+), 215 deletions(-) base-commit: 48e8992e33abf054bcc0bb2e77b2d43bb899212e
Comments
On Fri, 22 Dec 2023 18:41:51 +0100, Alex Bee wrote: > This is version 4 of my series that aims to add support for the display > controller (VOP) and the HDMI controller block of RK3128 (which is very > similar to the one found in RK3036). The original intention of this series > was to add support for this slightly different integration but is by now, > driven by maintainer's feedback, exploded to be a rework of inno-hdmi > driver in large parts. It is, however, a change for the better. > > [...] Applied, thanks! [02/29] drm/rockchip: vop: Add output selection registers for RK312x commit: 407eaa4aa64a8429094fa75fac00fff5e471138d [03/29] drm/rockchip: inno_hdmi: Fix video timing commit: 47a145c03484d33e65d773169d5ca1b9fe2a492e [04/29] drm/rockchip: inno_hdmi: Remove useless mode_fixup commit: 099be7b6718685ebafb417e74bb637abf992474a [05/29] drm/rockchip: inno_hdmi: Remove useless copy of drm_display_mode commit: 8f0df2012b8a94aed0cc450016f7592c24e92cfb [06/29] drm/rockchip: inno_hdmi: Switch encoder hooks to atomic commit: ff4d4fa76fcc19f7d5d261f717121f0a88ec4e30 [07/29] drm/rockchip: inno_hdmi: Get rid of mode_set commit: d3e040f450ec8e46ff42fa495a433b976ab47686 [08/29] drm/rockchip: inno_hdmi: no need to store vic commit: d7ba3d711cf537ef0ece14cd85d2113ca338a00b [09/29] drm/rockchip: inno_hdmi: Remove unneeded has audio flag commit: f8723484e045ff2d176124484907ec0199c55a0c [10/29] drm/rockchip: inno_hdmi: Remove useless input format commit: c1ceee3248742149d1a602fd913bd88857da1d52 [11/29] drm/rockchip: inno_hdmi: Remove YUV-based csc coefficents commit: 139771b8239c43ad1bd6c2976aa12788096a5483 [12/29] drm/rockchip: inno_hdmi: Remove tmds rate from structure commit: 5f92474844a4fcb7997da20dd1de2031aed1d794 Best regards,
On Fri, 22 Dec 2023 18:41:51 +0100, Alex Bee wrote: > This is version 4 of my series that aims to add support for the display > controller (VOP) and the HDMI controller block of RK3128 (which is very > similar to the one found in RK3036). The original intention of this series > was to add support for this slightly different integration but is by now, > driven by maintainer's feedback, exploded to be a rework of inno-hdmi > driver in large parts. It is, however, a change for the better. > > [...] Applied, thanks! [13/29] drm/rockchip: inno_hdmi: Drop HDMI Vendor Infoframe support commit: aa4f96e2de82f5e0dfc0102d08f66918c5e3637f [14/29] drm/rockchip: inno_hdmi: Move infoframe disable to separate function commit: cc9ec38cb2cd32518fe02615d004e96ce2fd0348 [15/29] drm/rockchip: inno_hdmi: Switch to infoframe type commit: 4278ff62b73936a9138b60cc0610381003132b77 [16/29] drm/rockchip: inno_hdmi: Remove unused drm device pointer commit: 153fe8dbd866869846af3a359ecf82d5ad9fe247 [17/29] drm/rockchip: inno_hdmi: Drop irq struct member commit: 073aa696f8cbc170a2c3502c2165aeb835be0156 [18/29] drm/rockchip: inno_hdmi: Remove useless include commit: f68a68fe9d9197ea6aa9cb461270685f370b165e [19/29] drm/rockchip: inno_hdmi: Subclass connector state commit: ceeb0f0104a62c867656c2730a51df47e7350b8f [20/29] drm/rockchip: inno_hdmi: Correctly setup HDMI quantization range commit: 164abbd2b7ef62aae6fc80450a2d085acdc3da3e [21/29] drm/rockchip: inno_hdmi: Don't power up the phy after resetting commit: 71892cee6ceb3e1b88e0bb44b05c8397d8261a85 [22/29] drm/rockchip: inno_hdmi: Split power mode setting commit: f01e33cb586b5fd354cba73052f82c3b4246109d Best regards,
On Fri, 22 Dec 2023 18:41:51 +0100, Alex Bee wrote: > This is version 4 of my series that aims to add support for the display > controller (VOP) and the HDMI controller block of RK3128 (which is very > similar to the one found in RK3036). The original intention of this series > was to add support for this slightly different integration but is by now, > driven by maintainer's feedback, exploded to be a rework of inno-hdmi > driver in large parts. It is, however, a change for the better. > > [...] Applied, thanks! [23/29] drm/rockchip: inno_hdmi: Add variant support commit: 5f2e93e6719701a91307090f8f7696fd6b3bffdf [24/29] drm/rockchip: inno_hdmi: Add RK3128 support commit: aa54f334c291effe321aa4b9ac0e67a895fd7b58 [25/29] drm/rockchip: inno_hdmi: Add basic mode validation commit: 701029621d4141d0c9f8b81a88a37b95ec84ce65 [26/29] drm/rockchip: inno_hdmi: Drop custom fill_modes hook commit: 50a3c772bd927dd409c484832ddd9f6bf00b7389 For reference, Rob has applied the rk3128 compatible in https://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git/commit/?id=21960bda59852ca961fcd27fba9f92750caccd06 Best regards,
Hi Heiko, Am 04.01.24 um 09:14 schrieb Heiko Stuebner: > On Fri, 22 Dec 2023 18:41:51 +0100, Alex Bee wrote: >> This is version 4 of my series that aims to add support for the display >> controller (VOP) and the HDMI controller block of RK3128 (which is very >> similar to the one found in RK3036). The original intention of this series >> was to add support for this slightly different integration but is by now, >> driven by maintainer's feedback, exploded to be a rework of inno-hdmi >> driver in large parts. It is, however, a change for the better. >> >> [...] > Applied, thanks! > > [23/29] drm/rockchip: inno_hdmi: Add variant support > commit: 5f2e93e6719701a91307090f8f7696fd6b3bffdf > [24/29] drm/rockchip: inno_hdmi: Add RK3128 support > commit: aa54f334c291effe321aa4b9ac0e67a895fd7b58 > [25/29] drm/rockchip: inno_hdmi: Add basic mode validation > commit: 701029621d4141d0c9f8b81a88a37b95ec84ce65 > [26/29] drm/rockchip: inno_hdmi: Drop custom fill_modes hook > commit: 50a3c772bd927dd409c484832ddd9f6bf00b7389 > > > For reference, Rob has applied the rk3128 compatible in > https://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git/commit/?id=21960bda59852ca961fcd27fba9f92750caccd06 thanks for keeping track on this. Is there any reason the DT paches aren't merged yet? From what I can see they should be fine to be merged in your v6.8-armsoc/dts32 branch which is 6.7-rc1 based. There was only a txt-binding at this point and it's very likely that both the rockchip,inno-hdmi.yaml-conversion and the rk3128 additon will both land in 6.8 (they are both in linux-next). Linus' 6.8 merge-window will open earliest next week. I'm really not pressuring here and I'm fine if they land in 6.9 - it's just for my understanding for further submissions. Alex > > Best regards,
Am Freitag, 5. Januar 2024, 17:47:21 CET schrieb Alex Bee: > Hi Heiko, > > > Am 04.01.24 um 09:14 schrieb Heiko Stuebner: > > On Fri, 22 Dec 2023 18:41:51 +0100, Alex Bee wrote: > >> This is version 4 of my series that aims to add support for the display > >> controller (VOP) and the HDMI controller block of RK3128 (which is very > >> similar to the one found in RK3036). The original intention of this series > >> was to add support for this slightly different integration but is by now, > >> driven by maintainer's feedback, exploded to be a rework of inno-hdmi > >> driver in large parts. It is, however, a change for the better. > >> > >> [...] > > Applied, thanks! > > > > [23/29] drm/rockchip: inno_hdmi: Add variant support > > commit: 5f2e93e6719701a91307090f8f7696fd6b3bffdf > > [24/29] drm/rockchip: inno_hdmi: Add RK3128 support > > commit: aa54f334c291effe321aa4b9ac0e67a895fd7b58 > > [25/29] drm/rockchip: inno_hdmi: Add basic mode validation > > commit: 701029621d4141d0c9f8b81a88a37b95ec84ce65 > > [26/29] drm/rockchip: inno_hdmi: Drop custom fill_modes hook > > commit: 50a3c772bd927dd409c484832ddd9f6bf00b7389 > > > > > > For reference, Rob has applied the rk3128 compatible in > > https://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git/commit/?id=21960bda59852ca961fcd27fba9f92750caccd06 > thanks for keeping track on this. > > Is there any reason the DT paches aren't merged yet? From what I can see > they should be fine to be merged in your v6.8-armsoc/dts32 branch which is > 6.7-rc1 based. There was only a txt-binding at this point and it's very > likely that both the rockchip,inno-hdmi.yaml-conversion and the rk3128 > additon will both land in 6.8 (they are both in linux-next). Linus' 6.8 > merge-window will open earliest next week. Exactly ... and the arm subarchitectures (Rockchip, etc) feed into the more generic soc-tree[0] and from there in a set of pull requests. Normally everything needs to go to the soc tree before -rc7 . With the whole xmas stuff, I sent some stragglers in a second pull request on monday, but that was already before Rob applied the binding on tuesday. So 6.8 devicetree stuff is essentially done and the dts patches from this series will go in to 6.9 . Hope that explains things a bit :-) Heiko [0] https://git.kernel.org/pub/scm/linux/kernel/git/soc/soc.git/ > I'm really not pressuring here and I'm fine if they land in 6.9 - it's just > for my understanding for further submissions. > > Alex > > > > > Best regards, >
Am 05.01.24 um 18:02 schrieb Heiko Stübner: > Am Freitag, 5. Januar 2024, 17:47:21 CET schrieb Alex Bee: >> Hi Heiko, >> >> >> Am 04.01.24 um 09:14 schrieb Heiko Stuebner: >>> On Fri, 22 Dec 2023 18:41:51 +0100, Alex Bee wrote: >>>> This is version 4 of my series that aims to add support for the display >>>> controller (VOP) and the HDMI controller block of RK3128 (which is very >>>> similar to the one found in RK3036). The original intention of this series >>>> was to add support for this slightly different integration but is by now, >>>> driven by maintainer's feedback, exploded to be a rework of inno-hdmi >>>> driver in large parts. It is, however, a change for the better. >>>> >>>> [...] >>> Applied, thanks! >>> >>> [23/29] drm/rockchip: inno_hdmi: Add variant support >>> commit: 5f2e93e6719701a91307090f8f7696fd6b3bffdf >>> [24/29] drm/rockchip: inno_hdmi: Add RK3128 support >>> commit: aa54f334c291effe321aa4b9ac0e67a895fd7b58 >>> [25/29] drm/rockchip: inno_hdmi: Add basic mode validation >>> commit: 701029621d4141d0c9f8b81a88a37b95ec84ce65 >>> [26/29] drm/rockchip: inno_hdmi: Drop custom fill_modes hook >>> commit: 50a3c772bd927dd409c484832ddd9f6bf00b7389 >>> >>> >>> For reference, Rob has applied the rk3128 compatible in >>> https://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git/commit/?id=21960bda59852ca961fcd27fba9f92750caccd06 >> thanks for keeping track on this. >> >> Is there any reason the DT paches aren't merged yet? From what I can see >> they should be fine to be merged in your v6.8-armsoc/dts32 branch which is >> 6.7-rc1 based. There was only a txt-binding at this point and it's very >> likely that both the rockchip,inno-hdmi.yaml-conversion and the rk3128 >> additon will both land in 6.8 (they are both in linux-next). Linus' 6.8 >> merge-window will open earliest next week. > Exactly ... and the arm subarchitectures (Rockchip, etc) feed into the > more generic soc-tree[0] and from there in a set of pull requests. > > Normally everything needs to go to the soc tree before -rc7 . > With the whole xmas stuff, I sent some stragglers in a second pull > request on monday, but that was already before Rob applied the > binding on tuesday. > > So 6.8 devicetree stuff is essentially done and the dts patches > from this series will go in to 6.9 . > > > Hope that explains things a bit :-) I assumed (for some reason) that sub-architecture maintainers are allowed to send PRs to the respective upper tree until the merge window opens and "all the rest" is done within this ~2 weeks. Thanks for explaining. Alex > Heiko > > [0] https://git.kernel.org/pub/scm/linux/kernel/git/soc/soc.git/ > >> I'm really not pressuring here and I'm fine if they land in 6.9 - it's just >> for my understanding for further submissions. >> >> Alex >> >>> Best regards, > > >
Am Freitag, 5. Januar 2024, 18:33:34 CET schrieb Alex Bee: > > Am 05.01.24 um 18:02 schrieb Heiko Stübner: > > Am Freitag, 5. Januar 2024, 17:47:21 CET schrieb Alex Bee: > >> Hi Heiko, > >> > >> > >> Am 04.01.24 um 09:14 schrieb Heiko Stuebner: > >>> On Fri, 22 Dec 2023 18:41:51 +0100, Alex Bee wrote: > >>>> This is version 4 of my series that aims to add support for the display > >>>> controller (VOP) and the HDMI controller block of RK3128 (which is very > >>>> similar to the one found in RK3036). The original intention of this series > >>>> was to add support for this slightly different integration but is by now, > >>>> driven by maintainer's feedback, exploded to be a rework of inno-hdmi > >>>> driver in large parts. It is, however, a change for the better. > >>>> > >>>> [...] > >>> Applied, thanks! > >>> > >>> [23/29] drm/rockchip: inno_hdmi: Add variant support > >>> commit: 5f2e93e6719701a91307090f8f7696fd6b3bffdf > >>> [24/29] drm/rockchip: inno_hdmi: Add RK3128 support > >>> commit: aa54f334c291effe321aa4b9ac0e67a895fd7b58 > >>> [25/29] drm/rockchip: inno_hdmi: Add basic mode validation > >>> commit: 701029621d4141d0c9f8b81a88a37b95ec84ce65 > >>> [26/29] drm/rockchip: inno_hdmi: Drop custom fill_modes hook > >>> commit: 50a3c772bd927dd409c484832ddd9f6bf00b7389 > >>> > >>> > >>> For reference, Rob has applied the rk3128 compatible in > >>> https://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git/commit/?id=21960bda59852ca961fcd27fba9f92750caccd06 > >> thanks for keeping track on this. > >> > >> Is there any reason the DT paches aren't merged yet? From what I can see > >> they should be fine to be merged in your v6.8-armsoc/dts32 branch which is > >> 6.7-rc1 based. There was only a txt-binding at this point and it's very > >> likely that both the rockchip,inno-hdmi.yaml-conversion and the rk3128 > >> additon will both land in 6.8 (they are both in linux-next). Linus' 6.8 > >> merge-window will open earliest next week. > > Exactly ... and the arm subarchitectures (Rockchip, etc) feed into the > > more generic soc-tree[0] and from there in a set of pull requests. > > > > Normally everything needs to go to the soc tree before -rc7 . > > With the whole xmas stuff, I sent some stragglers in a second pull > > request on monday, but that was already before Rob applied the > > binding on tuesday. > > > > So 6.8 devicetree stuff is essentially done and the dts patches > > from this series will go in to 6.9 . > > > > > > Hope that explains things a bit :-) > I assumed (for some reason) that sub-architecture maintainers are allowed > to send PRs to the respective upper tree until the merge window opens and > "all the rest" is done within this ~2 weeks. > Thanks for explaining. No worries :-) . The general rule of thumb is that everything should be done and ready before the merge-window opens. Linus often writes very positively about people sending him pull-requests even before the merge window opens ;-) [meaning their tree is settled early and all test-robots have run] And there are different rules in every tree. For the soc tree the general rule of thumb of =< -rc7 - earlier with larger changesets. On the other side drm-misc stays open all the time, but makes a cut at -rc6. So everything targetted at v6.8 needs to be in before v6.7-rc6. Heiko
On Fri, 22 Dec 2023 18:41:51 +0100, Alex Bee wrote: > This is version 4 of my series that aims to add support for the display > controller (VOP) and the HDMI controller block of RK3128 (which is very > similar to the one found in RK3036). The original intention of this series > was to add support for this slightly different integration but is by now, > driven by maintainer's feedback, exploded to be a rework of inno-hdmi > driver in large parts. It is, however, a change for the better. > > [...] Applied, thanks! [27/29] ARM: dts: rockchip: Add display subsystem for RK3128 commit: 695b9b57443d88a1c8e0567c88a79d1a4532c75e [28/29] ARM: dts: rockchip: Add HDMI node for RK3128 commit: 3fd6e33f8fde16869d4cd9cef71ca964b2b0789b [29/29] ARM: dts: rockchip: Enable HDMI output for XPI-3128 commit: 5aab66e319df2a6fc4ab06bcb4bd974c1ac4927e Best regards,