From: Imre Deak <imre.deak@intel.com>
To: Arun R Murthy <arun.r.murthy@intel.com>
Cc: <intel-gfx@lists.freedesktop.org>, <intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH v5] drm/i915/display: Use the recomended min_hblank values
Date: Mon, 28 Jul 2025 11:37:30 +0300 [thread overview]
Message-ID: <aIc2ytX67SuMQvmK@ideak-desk> (raw)
In-Reply-To: <20250728-min_hblank-v5-1-54cb7ea5cd74@intel.com>
On Mon, Jul 28, 2025 at 01:32:14PM +0530, Arun R Murthy wrote:
> Use recommended values as per wa_14021694213 to compare with the
> calculated value and choose minimum of them.
>
> v2: corrected checkpatch warning and retain the restriction for
> min_hblank (Jani)
> v3: use calculated value to compare with recomended value and choose
> minimum of them (Imre)
> v4: As driver supported min bpc is 8, omit the condition check for
> bpc6 with ycbcr420. Added a note for the same (Imre)
> v5: Add a warn for the unexpected case of 6bpc + uhbr + ycbcr420
>
> Bspec: 74379
> Signed-off-by: Arun R Murthy <arun.r.murthy@intel.com>
> ---
> Changes in v5:
> - EDITME: describe what is new in this series revision.
> - EDITME: use bulletpoints and terse descriptions.
> - Link to v4: https://lore.kernel.org/r/20250728-min_hblank-v4-1-b9d83bf03025@intel.com
> ---
> drivers/gpu/drm/i915/display/intel_dp.c | 21 ++++++++++++++++++++-
> 1 file changed, 20 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_dp.c b/drivers/gpu/drm/i915/display/intel_dp.c
> index 54d88f24b6893e1f8009f00dda87d8dae5dfc137..1cc19f3e7729c25d2066f42601a18bdfa03b2721 100644
> --- a/drivers/gpu/drm/i915/display/intel_dp.c
> +++ b/drivers/gpu/drm/i915/display/intel_dp.c
> @@ -3182,7 +3182,26 @@ int intel_dp_compute_min_hblank(struct intel_crtc_state *crtc_state,
> */
> min_hblank = min_hblank - 2;
>
> - min_hblank = min(10, min_hblank);
> + /*
> + * min_hblank formula is undergoing a change, to avoid underrun use the
> + * recomended value in spec to compare with the calculated one and use the
> + * minimum value
> + */
> + if (intel_dp_is_uhbr(crtc_state)) {
> + /*
> + * Note: Driver doesn't support compressed bpp 6.
> + * Its unusual to have 6bpc with YCBCR420, for which the spec suggests
^bpp
> + * a minimum hblank value of 2(Hence this condition is omitted).
It's not clear why a compressed bpp of 6 would be unusual. The driver
would use this compressed bpp, just as it would use any other compressed
bpp, if the source (HW) would support it and the available link bandwidth
would require it. It's just that the minimum compressed bpp supported by
the HW or driver is 8. So I'd just say stg like:
/*
* Note: Bspec requires a min_hblank of 2 for YCBCR420
* with compressed bpp 6, but the minimum compressed bpp
* supported by the driver is 8.
*/
> + */
> + drm_WARN(display->drm, (crtc_state->dsc.compression_enable &&
> + crtc_state->output_format == INTEL_OUTPUT_FORMAT_YCBCR420 &&
> + crtc_state->dsc.compressed_bpp_x16 == 6),
The above needs a conversion from int to fixed point and it's better to
also assert that the bpp is at least 8, so
crtc_state->dsc.compressed_bpp_x16 < fxp_q4_from_int(8)
> + "Unusual to have compressed bpp 6 with ycbcr420\n");
The condition is self-explanatory, so I'd just use drm_WARN_ON() w/o the
above text part.
> + min_hblank = min(3, min_hblank);
> + } else {
> + min_hblank = min(10, min_hblank);
> + }
> +
> crtc_state->min_hblank = min_hblank;
>
> return 0;
>
> ---
> base-commit: eb0c2b25072b5c56e8c41d7099050bf53bebaa14
> change-id: 20250728-min_hblank-263ceb40508c
>
> Best regards,
> --
> Arun R Murthy <arun.r.murthy@intel.com>
>
prev parent reply other threads:[~2025-07-28 8:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-28 8:02 [PATCH v5] drm/i915/display: Use the recomended min_hblank values Arun R Murthy
2025-07-28 8:37 ` Imre Deak [this message]
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=aIc2ytX67SuMQvmK@ideak-desk \
--to=imre.deak@intel.com \
--cc=arun.r.murthy@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.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 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.