From: "Nautiyal, Ankit K" <ankit.k.nautiyal@intel.com>
To: Suraj Kandpal <suraj.kandpal@intel.com>,
<intel-xe@lists.freedesktop.org>,
<intel-gfx@lists.freedesktop.org>
Cc: <uma.shankar@intel.com>, <william.tseng@intel.com>,
<jani.nikula@intel.com>
Subject: Re: [PATCH] drm/i915/vdsc: Use the DSC config tables for DSI panels
Date: Fri, 28 Feb 2025 10:07:22 +0530 [thread overview]
Message-ID: <a940d336-31e3-467d-bcc9-4c9301f7a740@intel.com> (raw)
In-Reply-To: <20250227112654.279160-1-suraj.kandpal@intel.com>
On 2/27/2025 4:56 PM, Suraj Kandpal wrote:
> Some DSI panel vendors end up hardcoding PPS params because of which
> it does not listen to the params sent from the source. We use the
> default config tables for DSI panels when using DSC 1.1 rather than
> calculate our own rc parameters.
>
> --v2
> -Use intel_crtc_has_type [Jani]
>
> --v3
> -Add Signed-off-by from William too [Ankit]
>
> Closes: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/13719
> Signed-off-by: Suraj Kandpal <suraj.kandpal@intel.com>
> Signed-off-by: William Tseng <william.tseng@intel.com>
> ---
> drivers/gpu/drm/i915/display/intel_vdsc.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_vdsc.c b/drivers/gpu/drm/i915/display/intel_vdsc.c
> index 6e7151346382..affe9913f1ee 100644
> --- a/drivers/gpu/drm/i915/display/intel_vdsc.c
> +++ b/drivers/gpu/drm/i915/display/intel_vdsc.c
> @@ -320,7 +320,9 @@ int intel_dsc_compute_params(struct intel_crtc_state *pipe_config)
> * upto uncompressed bpp-1, hence add calculations for all the rc
> * parameters
> */
> - if (DISPLAY_VER(dev_priv) >= 13) {
> + if (DISPLAY_VER(dev_priv) >= 13 &&
> + (vdsc_cfg->dsc_version_minor != 1 ||
> + intel_crtc_has_type(pipe_config, INTEL_OUTPUT_DSI))) {
This should be !intel_crtc_has_type(pipe_config, INTEL_OUTPUT_DSI)
I think it would be better to use a function for special handling for
DSI panel with DSC1.1.
(I am not very sure what should be an appropriate name for this but just
to give an example)
bool is_mipi_dsi_dsc_1_1()
{
return vdsc_cfg->dsc_version_minor == 1 &&
intel_crtc_has_type(pipe_config, INTEL_OUTPUT_DSI);
}
The condition will then become:
if (DISPLAY_VER(dev_priv) >= 13 && !is_mipi_dsi_dsc_1_1())
calculate_rc_params(vdsc_cfg);
With this we also need to document about why we are not using calculate_rc_params for MIPI DSI with DSC1.1 in comment above the function.
Regards,
Ankit
> calculate_rc_params(vdsc_cfg);
> } else {
> if ((compressed_bpp == 8 ||
next prev parent reply other threads:[~2025-02-28 4:37 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-27 11:26 [PATCH] drm/i915/vdsc: Use the DSC config tables for DSI panels Suraj Kandpal
2025-02-27 13:28 ` ✓ CI.Patch_applied: success for drm/i915/vdsc: Use the DSC config tables for DSI panels (rev3) Patchwork
2025-02-27 13:28 ` ✓ CI.checkpatch: " Patchwork
2025-02-27 13:29 ` ✓ CI.KUnit: " Patchwork
2025-02-27 13:46 ` ✓ CI.Build: " Patchwork
2025-02-27 13:48 ` ✓ CI.Hooks: " Patchwork
2025-02-27 13:49 ` ✓ CI.checksparse: " Patchwork
2025-02-27 14:07 ` ✓ Xe.CI.BAT: " Patchwork
2025-02-27 16:40 ` ✗ Xe.CI.Full: failure " Patchwork
2025-02-28 4:37 ` Nautiyal, Ankit K [this message]
2025-02-28 4:47 ` [PATCH] drm/i915/vdsc: Use the DSC config tables for DSI panels Kandpal, Suraj
-- strict thread matches above, loose matches on Subject: below --
2025-02-28 15:25 Suraj Kandpal
2025-03-11 5:33 ` Nautiyal, Ankit K
2025-02-28 5:10 Suraj Kandpal
2025-02-28 9:15 ` Jani Nikula
2025-02-28 1:15 Yu, Gareth
2025-02-27 10:49 Suraj Kandpal
2025-02-27 9:53 Suraj Kandpal
2025-02-27 10:42 ` Jani Nikula
2025-02-27 10:45 ` Kandpal, Suraj
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=a940d336-31e3-467d-bcc9-4c9301f7a740@intel.com \
--to=ankit.k.nautiyal@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=suraj.kandpal@intel.com \
--cc=uma.shankar@intel.com \
--cc=william.tseng@intel.com \
/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