From: Liu Ying <victor.liu@nxp.com>
To: "Dmitry Baryshkov" <dmitry.baryshkov@oss.qualcomm.com>,
"Andrzej Hajda" <andrzej.hajda@intel.com>,
"Neil Armstrong" <neil.armstrong@linaro.org>,
"Robert Foss" <rfoss@kernel.org>,
"Laurent Pinchart" <Laurent.pinchart@ideasonboard.com>,
"Jonas Karlman" <jonas@kwiboo.se>,
"Jernej Skrabec" <jernej.skrabec@gmail.com>,
"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
"Maxime Ripard" <mripard@kernel.org>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
"David Airlie" <airlied@gmail.com>,
"Simona Vetter" <simona@ffwll.ch>,
"Sandy Huang" <hjc@rock-chips.com>,
"Heiko Stübner" <heiko@sntech.de>,
"Andy Yan" <andy.yan@rock-chips.com>,
"Chen-Yu Tsai" <wens@csie.org>,
"Samuel Holland" <samuel@sholland.org>,
"Dave Stevenson" <dave.stevenson@raspberrypi.com>,
"Maíra Canal" <mcanal@igalia.com>,
"Raspberry Pi Kernel Maintenance" <kernel-list@raspberrypi.com>,
"Rob Clark" <robin.clark@oss.qualcomm.com>,
"Dmitry Baryshkov" <lumag@kernel.org>,
"Abhinav Kumar" <abhinav.kumar@linux.dev>,
"Jessica Zhang" <jessica.zhang@oss.qualcomm.com>,
"Sean Paul" <sean@poorly.run>,
"Marijn Suijten" <marijn.suijten@somainline.org>
Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-sunxi@lists.linux.dev,
linux-arm-msm@vger.kernel.org, freedreno@lists.freedesktop.org
Subject: Re: [PATCH v2 1/8] drm/connector: let drivers declare infoframes as unsupported
Date: Wed, 20 Aug 2025 11:31:03 +0800 [thread overview]
Message-ID: <214e8bad-8ca7-405e-bdf6-90ab3a1a5d84@nxp.com> (raw)
In-Reply-To: <20250819-drm-limit-infoframes-v2-1-7595dda24fbd@oss.qualcomm.com>
On 08/19/2025, Dmitry Baryshkov wrote:
> Currently DRM framework expects that the HDMI connector driver supports
> all infoframe types: it generates the data as required and calls into
> the driver to program all of them, letting the driver to soft-fail if
> the infoframe is unsupported. This has a major drawback on userspace
> API: the framework also registers debugfs files for all Infoframe types,
> possibly surprising the users when infoframe is visible in the debugfs
> file, but it is not visible on the wire.
>
> Let drivers declare that they support only a subset of infoframes,
> creating a more consistent interface.
>
> Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
> ---
> drivers/gpu/drm/display/drm_bridge_connector.c | 6 ++++
> drivers/gpu/drm/display/drm_hdmi_state_helper.c | 37 ++++++++++++++++++++--
> drivers/gpu/drm/drm_connector.c | 4 +++
> drivers/gpu/drm/drm_debugfs.c | 16 +++++++---
> drivers/gpu/drm/rockchip/inno_hdmi.c | 1 +
> drivers/gpu/drm/sun4i/sun4i_hdmi_enc.c | 1 +
> drivers/gpu/drm/tests/drm_connector_test.c | 28 ++++++++++++++++
> drivers/gpu/drm/tests/drm_hdmi_state_helper_test.c | 8 +++++
> drivers/gpu/drm/vc4/vc4_hdmi.c | 5 +++
> include/drm/drm_bridge.h | 7 ++++
> include/drm/drm_connector.h | 22 +++++++++++++
> 11 files changed, 128 insertions(+), 7 deletions(-)
Acked-by: Liu Ying <victor.liu@nxp.com>
next prev parent reply other threads:[~2025-08-20 3:29 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-19 18:57 [PATCH v2 0/8] drm/connector: hdmi: limit infoframes per driver capabilities Dmitry Baryshkov
2025-08-19 18:57 ` [PATCH v2 1/8] drm/connector: let drivers declare infoframes as unsupported Dmitry Baryshkov
2025-08-20 3:31 ` Liu Ying [this message]
2025-08-20 4:52 ` Liu Ying
2025-08-20 7:15 ` Maxime Ripard
2025-08-20 9:52 ` Dmitry Baryshkov
2025-08-27 7:30 ` Maxime Ripard
2025-08-27 14:04 ` Dmitry Baryshkov
2025-09-01 6:54 ` Maxime Ripard
2025-09-02 3:12 ` Dmitry Baryshkov
2025-09-02 17:38 ` Maxime Ripard
2025-08-19 18:57 ` [PATCH v2 2/8] drm/bridge: adv7511: declare supported infoframes Dmitry Baryshkov
2025-08-20 3:41 ` Liu Ying
2025-08-19 18:57 ` [PATCH v2 3/8] drm/bridge: ite-it6263: " Dmitry Baryshkov
2025-08-19 18:57 ` [PATCH v2 4/8] drm/bridge: lontium-lt9611: " Dmitry Baryshkov
2025-08-20 3:49 ` Liu Ying
2025-08-19 18:57 ` [PATCH v2 5/8] drm/bridge: synopsys/dw-hdmi-qp: " Dmitry Baryshkov
2025-08-20 3:54 ` Liu Ying
2025-08-19 18:57 ` [PATCH v2 6/8] drm/msm: hdmi: " Dmitry Baryshkov
2025-08-20 3:56 ` Liu Ying
2025-08-19 18:57 ` [PATCH v2 7/8] drm/rockchip: rk3066: " Dmitry Baryshkov
2025-08-20 3:59 ` Liu Ying
2025-08-19 18:57 ` [PATCH v2 8/8] drm/display: bridge_connector: drop default list for HDMI Infoframes Dmitry Baryshkov
2025-08-20 4:02 ` Liu Ying
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=214e8bad-8ca7-405e-bdf6-90ab3a1a5d84@nxp.com \
--to=victor.liu@nxp.com \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=abhinav.kumar@linux.dev \
--cc=airlied@gmail.com \
--cc=andrzej.hajda@intel.com \
--cc=andy.yan@rock-chips.com \
--cc=dave.stevenson@raspberrypi.com \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=heiko@sntech.de \
--cc=hjc@rock-chips.com \
--cc=jernej.skrabec@gmail.com \
--cc=jessica.zhang@oss.qualcomm.com \
--cc=jonas@kwiboo.se \
--cc=kernel-list@raspberrypi.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux-sunxi@lists.linux.dev \
--cc=lumag@kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=marijn.suijten@somainline.org \
--cc=mcanal@igalia.com \
--cc=mripard@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=rfoss@kernel.org \
--cc=robin.clark@oss.qualcomm.com \
--cc=samuel@sholland.org \
--cc=sean@poorly.run \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.de \
--cc=wens@csie.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®