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 60D58C79FA1 for ; Tue, 8 Sep 2026 09:59:11 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender:List-Subscribe:List-Help :List-Post:List-Archive:List-Unsubscribe:List-Id:Content-Transfer-Encoding:Cc :References:In-Reply-To:Subject:To:From:Date:Message-ID:Reply-To:MIME-Version :Content-Type:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=qJfUSJRCevtsAlee5fpqTfsNMuEH2eYAYjOny6uC7L0=; b=IdSvntKYqmnOdh1ihyuUFe9v29 gFGQoZ1nCIcbgj2yKNrtXqO29bgjea8igDY56djcGz7DnrM7bVYH1+Hq2X4iX9A8v/UrydA9sAK08 +ChHETCoQ1/vjIS0JN8rJv9BH8PXBwMeZBoA0tPjWTDSYK2cpL2jnLpkdKVZ6IyXFmKEWHO0MKjcr zWpIGXhIXQHTJ8P3aD1VqGU3k0mp+b6i083f80hApWLst/WF8al7D1UuLaHjOW2xyG0THlcVYaIWt +uMUZlQGWKK+//rGxKwK8ToAdgyUiHbpdyIfxvKNDOb3jrMtIUr0w088cI0aOTvJ7AKW7msSxFlpl xheod1Fw==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.99.1 #2 (Red Hat Linux)) id 1x3sbY-00000008hSX-2iio; Tue, 08 Sep 2026 09:59:04 +0000 Received: from tor.source.kernel.org ([2600:3c04:e001:324:0:1991:8:25]) by bombadil.infradead.org with esmtps (Exim 4.99.1 #2 (Red Hat Linux)) id 1x3sbW-00000008hRm-3vSY; Tue, 08 Sep 2026 09:59:02 +0000 Received: from smtp.kernel.org (quasi.space.kernel.org [100.103.45.18]) by tor.source.kernel.org (Postfix) with ESMTP id 1ADCE60A93; Tue, 8 Sep 2026 09:59:02 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 1B05F1F00A3D; Tue, 8 Sep 2026 09:59:01 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1788861541; bh=qJfUSJRCevtsAlee5fpqTfsNMuEH2eYAYjOny6uC7L0=; h=Date:From:To:Subject:In-Reply-To:References:Cc; b=g0Dxy9so8FfejqBtHuaG1lGFytbhTY/SYmnz7lxKGGPNFXJY6tksNCGAhMyyuz15c A1HNknCOxFfkHm6oOjSbAspjVqXSKeptEF9ZCyFxezvuTAYWoKFqlUZ1Ic7jvWXwT5 7GZ/dYJqH8NTJlT6M3WcwIsCVLPKvLaPgU6wB3+eFiK5GMpwwkr651FofVo75WXkmL tJEnmWfvy8w5HZ1GjjHqkEiL/+zDadoFTrSWGanx07uUhYjBr2I7rx8Wa+kWpePwYQ O2qdzxGEg8NNjpa5m0fLxr6dMhZNw/OEgJuPqJxDqgSwis8L1EJF3ZExrowhezZVxL QxBfCrjhil0eg== Message-ID: <5053a2775eb9b2101ae7725b497912bc@kernel.org> Date: Tue, 08 Sep 2026 09:58:58 +0000 From: "Maxime Ripard" To: "Cristian Ciocaltea" Subject: Re: [PATCH v11 51/74] drm/bridge: inno-hdmi: Advertise HDMI 1.2 capabilities In-Reply-To: <20260901-dw-hdmi-qp-scramb-v11-51-bc12954a0688@collabora.com> References: <20260901-dw-hdmi-qp-scramb-v11-51-bc12954a0688@collabora.com> Cc: dri-devel@lists.freedesktop.org, kernel@collabora.com, linux-arm-kernel@lists.infradead.org, linux-fbdev@vger.kernel.org, linux-kernel@vger.kernel.org, linux-rockchip@lists.infradead.org, linux-sunxi@lists.linux.dev, "Algea Cao" , "Andrzej Hajda" , "Andy Yan" , "Chen-Yu Tsai" , "Daniel Stone" , "Dave Stevenson" , "David Airlie" , "Dmitry Baryshkov" , =?utf-8?b?SGVpa28gU3TDvGJuZXI=?= , "Helge Deller" , "Jernej Skrabec" , "Jonas Karlman" , "Laurent Pinchart" , "Liu Ying" , "Luca Ceresoli" , "Maarten Lankhorst" , "Maxime Ripard" , =?utf-8?b?TWHDrXJhIENhbmFs?= , "Neil Armstrong" , "Phong LE" , "Raphael Gallais-Pou" , "Raspberry Pi Kernel Maintenance" , "Robert Foss" , "Samuel Holland" , "Sandy Huang" , "Simona Vetter" , "Thomas Zimmermann" Content-Transfer-Encoding: 7bit X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Tue, 1 Sep 2026 21:51:15 +0300, Cristian Ciocaltea wrote: > Bridges using DRM_BRIDGE_OP_HDMI are now expected to also provide a > supported HDMI version. This is not yet enforced, but will become > mandatory once the migration to the new caps-based HDMI connector > initialization API is completed. > > > [ ... ] Reviewed-by: Maxime Ripard Thanks! Maxime