From: Jani Nikula <jani.nikula@linux.intel.com>
To: Suraj Kandpal <suraj.kandpal@intel.com>, intel-gfx@lists.freedesktop.org
Cc: mitulkumar.ajitkumar.golani@intel.com,
chaitanya.kumar.borah@intel.com,
Suraj Kandpal <suraj.kandpal@intel.com>
Subject: Re: [PATCH] drm/i915/vdsc: Add bpc check in intel_dsc_compute_params
Date: Thu, 26 Sep 2024 10:59:18 +0300 [thread overview]
Message-ID: <87v7yi26cp.fsf@intel.com> (raw)
In-Reply-To: <20240926053346.1391776-2-suraj.kandpal@intel.com>
On Thu, 26 Sep 2024, Suraj Kandpal <suraj.kandpal@intel.com> wrote:
> DSC does not support bpc under 8 according to DSC 1.2a Section 2
> Requirements. Return an error if that happens to be the case.
>
> --v2
> -should be bits_per_component [Mitul/Chaitanya/Srikanth]
> -Add reference to this restriction [Chaitanya]
>
> Signed-off-by: Suraj Kandpal <suraj.kandpal@intel.com>
> ---
> drivers/gpu/drm/i915/display/intel_vdsc.c | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_vdsc.c b/drivers/gpu/drm/i915/display/intel_vdsc.c
> index 8158e3702ed5..7a30fdea16da 100644
> --- a/drivers/gpu/drm/i915/display/intel_vdsc.c
> +++ b/drivers/gpu/drm/i915/display/intel_vdsc.c
> @@ -306,6 +306,11 @@ int intel_dsc_compute_params(struct intel_crtc_state *pipe_config)
>
> vdsc_cfg->bits_per_component = pipe_config->pipe_bpp / 3;
>
> + if (vdsc_cfg->bits_per_component < 8) {
> + drm_dbg_kms(&dev_priv->drm, "DSC bpc requirements not met\n");
If you hit this warning, what's the absolutely first thing you want to
know...? Maybe log that bits_per_component value here?
BR,
Jani.
> + return -EINVAL;
> + }
> +
> drm_dsc_set_rc_buf_thresh(vdsc_cfg);
>
> /*
--
Jani Nikula, Intel
next prev parent reply other threads:[~2024-09-26 7:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-26 4:33 [PATCH] drm/i915/vdsc: Add bpc check in intel_dsc_compute_params Suraj Kandpal
2024-09-26 5:00 ` Borah, Chaitanya Kumar
2024-09-26 5:13 ` Kandpal, Suraj
2024-09-26 5:14 ` Suraj Kandpal
2024-09-26 5:26 ` Srikanth V, NagaVenkata
2024-09-26 5:33 ` Suraj Kandpal
2024-09-26 5:52 ` Borah, Chaitanya Kumar
2024-09-26 7:59 ` Jani Nikula [this message]
2024-09-26 8:13 ` Suraj Kandpal
2024-09-27 19:12 ` ✓ Fi.CI.BAT: success for drm/i915/vdsc: Add bpc check in intel_dsc_compute_params (rev4) Patchwork
2024-09-28 20:04 ` ✗ Fi.CI.IGT: failure " Patchwork
2024-09-30 13:42 ` ✓ Fi.CI.IGT: success " Patchwork
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=87v7yi26cp.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=chaitanya.kumar.borah@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=mitulkumar.ajitkumar.golani@intel.com \
--cc=suraj.kandpal@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.