From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from bali.collaboradmins.com (bali.collaboradmins.com [148.251.105.195]) (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 7D0323976A4 for ; Wed, 8 Jul 2026 10:19:26 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=148.251.105.195 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1783505967; cv=none; b=ApzPjO8+hG6gRqRDVaiakUDL6/5/lpXIHQsWh3fChCLq4xRkdfnGqeQCbAHL6RRVFblpeQ0LMabS9E1ZyYlcD1hF4kYMRZbptt11s9yXM3NZo/clyWf7tlegsH/BsZt7qEv5TbvTz7wR8Ip3cpbYSsdmfmxAJbo4v1Dq9jIbWAM= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1783505967; c=relaxed/simple; bh=t4DOSQvYZTk4aogo+c4G+/9IKm4UAqiMw36o1jDkqKc=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From: In-Reply-To:Content-Type; b=QEYiTsVTPR3tmOW1gI7o6pWfAUHh5Q1+XwlNcfPUrDcUN+ADtoAZL07e4LMrOFsZks67rQxc7Xyf4TwgSzUCWWe0Jn/agwrZObdkjGnmk+btWB0e88xIiQedntZ2ZF5LSaxqJKHtHZOJR1vorda7O9gg6Nky+ueASa5TlZ+OCMk= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none 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=a08YaQTj; arc=none smtp.client-ip=148.251.105.195 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none 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="a08YaQTj" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=collabora.com; s=mail; t=1783505964; bh=t4DOSQvYZTk4aogo+c4G+/9IKm4UAqiMw36o1jDkqKc=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=a08YaQTjh/lmoGKJCUBgd5xcipF4vvRTVqpmEgm5tN2tQ8FCVo2rbhVH4cbGrENXd LuEKARrfWMtakQXhdbthmdrUoVfhqwvNRHqT0gmMT8JnL5O0HjKGr8DnVIv/gkCiqV YJU3OjZzhSUaBGvPBZc5LrPo40m5AwLHbY5VS5FwYvNUfsAQ0nfJd1+xpuRlmKSc8I 1TlRt8c/FHHZ30ynN+OLRZ4doGvL3DkdAQw/b5H3fKEoDnMz+wnWkjSrOyZaYrcItO qkMtQmrZvQdLbMI8HhoiMi25hvaTQg94FcU1EKJbgexlwCzLwQQsbw/VdPAkV1RClf dQ4gOYNZTG90g== Received: from [100.64.0.241] (unknown [100.64.0.241]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange x25519) (No client certificate requested) (Authenticated sender: cristicc) by bali.collaboradmins.com (Postfix) with ESMTPSA id D83EC17E00F6; Wed, 08 Jul 2026 12:19:23 +0200 (CEST) Message-ID: Date: Wed, 8 Jul 2026 13:19:23 +0300 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PATCH v8 03/39] drm/display: bridge_connector: Pass HDMI capabilities through caps struct To: Maxime Ripard Cc: Dmitry Baryshkov , Maarten Lankhorst , Thomas Zimmermann , David Airlie , Simona Vetter , Andrzej Hajda , Neil Armstrong , Robert Foss , Laurent Pinchart , Jonas Karlman , Jernej Skrabec , Luca Ceresoli , Sandy Huang , =?UTF-8?Q?Heiko_St=C3=BCbner?= , Andy Yan , Daniel Stone , Dave Stevenson , =?UTF-8?Q?Ma=C3=ADra_Canal?= , Raspberry Pi Kernel Maintenance , kernel@collabora.com, dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-rockchip@lists.infradead.org References: <20260702-dw-hdmi-qp-scramb-v8-0-d79890d00b6a@collabora.com> <20260702-dw-hdmi-qp-scramb-v8-3-d79890d00b6a@collabora.com> <20260708-bold-ruby-potoo-c6c949@houat> Content-Language: en-US From: Cristian Ciocaltea In-Reply-To: <20260708-bold-ruby-potoo-c6c949@houat> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit On 7/8/26 9:46 AM, Maxime Ripard wrote: > On Fri, Jul 03, 2026 at 10:55:09PM +0300, Cristian Ciocaltea wrote: >> On 7/3/26 5:19 PM, Dmitry Baryshkov wrote: >>> On Thu, Jul 02, 2026 at 05:46:16PM +0300, Cristian Ciocaltea wrote: >>>> Switch drm_bridge_connector_init() to >>>> drmm_connector_hdmi_init_with_caps(), collecting the bridge's HDMI >>>> properties into a stack drm_connector_hdmi_caps so future HDMI 2.x >>>> capabilities can be plumbed without growing the argument list. >>>> >>>> Introduce struct drm_bridge::supported_hdmi_ver to let bridges declare >>>> the HDMI specification version they are conformant with, and forward it >>>> to the connector layer through the new caps struct so HDMI 2.x features >>>> can be gated on real source capability rather than guesswork. >>> >>> And it's left uninitialized by the bridges, which doesn't mean anything. >>> If you don't want to touch all bridge drivers in one commit, please >>> provide some migration path and hopefully get rid of it by the end of >>> the series. >> >> Sure, one question though: at the end of the migration, would it be fine to >> stick with drmm_connector_hdmi_init_with_caps() and just drop >> drmm_connector_hdmi_init()? Otherwise I'll rename it back. > > Absolutely, it doesn't make any sense to keep both variants. I was referring to whether option 3 might be the preferred choice in the context of the earlier patch discussion. Cristian