From: Maxime Ripard <mripard@kernel.org>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Cc: "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>,
"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>,
"Liu Ying" <victor.liu@nxp.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>,
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 v3 01/11] drm/connector: let drivers declare infoframes as unsupported
Date: Mon, 1 Sep 2025 09:03:30 +0200 [thread overview]
Message-ID: <20250901-precious-observant-kiwi-cc5283@houat> (raw)
In-Reply-To: <20250830-drm-limit-infoframes-v3-1-32fcbec4634e@oss.qualcomm.com>
[-- Attachment #1: Type: text/plain, Size: 877 bytes --]
On Sat, Aug 30, 2025 at 03:22:57AM +0300, 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.
>
> Acked-by: Liu Ying <victor.liu@nxp.com>
> Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
I still don't think it's a good idea on principle, see my answer to your v2.
Maxime
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 273 bytes --]
next prev parent reply other threads:[~2025-09-01 7:48 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-30 0:22 [PATCH v3 00/11] drm/connector: hdmi: limit infoframes per driver capabilities Dmitry Baryshkov
2025-08-30 0:22 ` [PATCH v3 01/11] drm/connector: let drivers declare infoframes as unsupported Dmitry Baryshkov
2025-09-01 7:03 ` Maxime Ripard [this message]
2025-08-30 0:22 ` [PATCH v3 02/11] drm/bridge: adv7511: declare supported infoframes Dmitry Baryshkov
2025-09-01 7:12 ` Maxime Ripard
2025-09-02 3:13 ` Dmitry Baryshkov
2025-08-30 0:22 ` [PATCH v3 03/11] drm/bridge: ite-it6263: " Dmitry Baryshkov
2025-08-30 0:23 ` [PATCH v3 04/11] drm/bridge: lontium-lt9611: " Dmitry Baryshkov
2025-08-30 0:23 ` [PATCH v3 05/11] drm/bridge: synopsys/dw-hdmi-qp: " Dmitry Baryshkov
2025-08-30 7:30 ` Daniel Stone
2025-08-30 0:23 ` [PATCH v3 06/11] drm/msm: hdmi: " Dmitry Baryshkov
2025-08-30 0:23 ` [PATCH v3 07/11] drm/rockchip: rk3066: " Dmitry Baryshkov
2025-08-30 12:08 ` kernel test robot
2025-08-30 0:23 ` [PATCH v3 08/11] drm/display: bridge_connector: drop default list for HDMI Infoframes Dmitry Baryshkov
2025-08-30 0:23 ` [PATCH v3 09/11] drm/connector: verify that HDMI connectors support necessary InfoFrames Dmitry Baryshkov
2025-08-30 7:34 ` Daniel Stone
2025-08-30 0:23 ` [PATCH v3 10/11] drm/display: hdmi-audio: warn if HDMI connector doesn't support Audio IF Dmitry Baryshkov
2025-08-30 0:23 ` [PATCH v3 11/11] drm/bridge: lontium-lt9611uxc: switch to HDMI audio helpers Dmitry Baryshkov
2025-08-30 7:30 ` [PATCH v3 00/11] drm/connector: hdmi: limit infoframes per driver capabilities Daniel Stone
2025-08-30 7:38 ` Daniel Stone
2025-08-30 22:29 ` Dmitry Baryshkov
2025-08-31 13:46 ` Daniel Stone
2025-09-01 7:07 ` Maxime Ripard
2025-09-02 3:45 ` Dmitry Baryshkov
2025-09-02 18:06 ` Maxime Ripard
2025-09-03 0:03 ` Dmitry Baryshkov
2025-09-10 7:30 ` Maxime Ripard
2025-09-10 15:26 ` Dmitry Baryshkov
2025-09-25 13:13 ` Maxime Ripard
2025-09-25 14:16 ` Dmitry Baryshkov
2025-09-29 13:00 ` Maxime Ripard
2025-09-30 7:02 ` Dmitry Baryshkov
2025-10-03 13:22 ` Maxime Ripard
2025-10-03 15:54 ` Dmitry Baryshkov
2025-10-14 12:59 ` Maxime Ripard
2025-10-14 15:48 ` Dmitry Baryshkov
2025-11-21 15:36 ` Maxime Ripard
2025-11-21 17:09 ` Dmitry Baryshkov
2025-12-01 17:01 ` Maxime Ripard
2025-12-06 11:28 ` Dmitry Baryshkov
2025-12-19 9:54 ` Maxime Ripard
2025-12-19 9:56 ` Dmitry Baryshkov
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=20250901-precious-observant-kiwi-cc5283@houat \
--to=mripard@kernel.org \
--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=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=victor.liu@nxp.com \
--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