From: Jani Nikula <jani.nikula@linux.intel.com>
To: Yaroslav Bolyukin <iam@lach.pw>,
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>
Cc: "Harry Wentland" <harry.wentland@amd.com>,
"Leo Li" <sunpeng.li@amd.com>,
"Rodrigo Siqueira" <siqueira@igalia.com>,
"Alex Deucher" <alexander.deucher@amd.com>,
"Christian König" <christian.koenig@amd.com>,
"Wayne Lin" <Wayne.Lin@amd.com>,
amd-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org,
"Yaroslav Bolyukin" <iam@lach.pw>
Subject: Re: [PATCH v4 2/2] drm/amd: use fixed dsc bits-per-pixel from edid
Date: Thu, 16 Oct 2025 19:39:57 +0300 [thread overview]
Message-ID: <34407e8d423f0d00e949ba8c6b209cb88e8f5414@intel.com> (raw)
In-Reply-To: <20251016001038.13611-6-iam@lach.pw>
On Thu, 16 Oct 2025, Yaroslav Bolyukin <iam@lach.pw> wrote:
> VESA vendor header from DisplayID spec may contain fixed bit per pixel
> rate, it should be respected by drm driver
>
> Signed-off-by: Yaroslav Bolyukin <iam@lach.pw>
> ---
> drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c | 14 +++++++++++++-
> 1 file changed, 13 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c b/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c
> index 0d03e324d5b9..ebe5bb4eecf8 100644
> --- a/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c
> +++ b/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c
> @@ -6521,6 +6521,11 @@ static void fill_stream_properties_from_drm_display_mode(
>
> stream->output_color_space = get_output_color_space(timing_out, connector_state);
> stream->content_type = get_output_content_type(connector_state);
> +
> + /* DisplayID Type VII pass-through timings. */
> + if (mode_in->dsc_passthrough_timings_support && info->dp_dsc_bpp != 0) {
> + stream->timing.dsc_fixed_bits_per_pixel_x16 = info->dp_dsc_bpp;
> + }
If we had mode->dp_dsc_bpp_x16 directly, or something better named, this
would be simpler. This will eventually be replicated in a bunch of
drivers.
BR,
Jani.
> }
>
> static void fill_audio_info(struct audio_info *audio_info,
> @@ -7067,6 +7072,13 @@ create_stream_for_sink(struct drm_connector *connector,
> &mode, preferred_mode, scale);
>
> preferred_refresh = drm_mode_vrefresh(preferred_mode);
> +
> + /*
> + * HACK: In case of multiple supported modes, we should look at the matching mode to decide this flag.
> + * But what is matching mode, how should it be decided?
> + * Assuming that only preferred mode would have this flag.
> + */
> + mode.dsc_passthrough_timings_support = preferred_mode->dsc_passthrough_timings_support;
> }
> }
>
> @@ -7756,7 +7768,7 @@ create_validate_stream_for_sink(struct drm_connector *connector,
> drm_dbg_kms(connector->dev, "%s:%d Validation failed with %d, retrying w/ YUV420\n",
> __func__, __LINE__, dc_result);
> aconnector->force_yuv420_output = true;
> - }
> +}
> stream = create_validate_stream_for_sink(connector, drm_mode,
> dm_state, old_stream);
> aconnector->force_yuv422_output = false;
--
Jani Nikula, Intel
next prev parent reply other threads:[~2025-10-16 16:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-16 0:10 [PATCH v4 0/2] DisplayID DSC passthrough timing support Yaroslav Bolyukin
2025-10-16 0:10 ` [PATCH v4 1/2] drm/edid: parse DRM VESA dsc bpp target Yaroslav Bolyukin
2025-10-16 16:36 ` Jani Nikula
2025-10-16 17:11 ` Yaroslav
2025-10-16 20:45 ` Ville Syrjälä
2025-10-16 22:24 ` Yaroslav
2025-10-16 22:55 ` Ville Syrjälä
2025-10-17 0:11 ` Yaroslav
2025-10-16 0:10 ` [PATCH v4 2/2] drm/amd: use fixed dsc bits-per-pixel from edid Yaroslav Bolyukin
2025-10-16 16:39 ` Jani Nikula [this message]
2025-10-16 17:22 ` Yaroslav
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=34407e8d423f0d00e949ba8c6b209cb88e8f5414@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=Wayne.Lin@amd.com \
--cc=airlied@gmail.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=harry.wentland@amd.com \
--cc=iam@lach.pw \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=simona@ffwll.ch \
--cc=siqueira@igalia.com \
--cc=sunpeng.li@amd.com \
--cc=tzimmermann@suse.de \
/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