Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Imre Deak <imre.deak@intel.com>
To: "Nautiyal, Ankit K" <ankit.k.nautiyal@intel.com>
Cc: <intel-gfx@lists.freedesktop.org>,
	<intel-xe@lists.freedesktop.org>,
	"Jani Nikula" <jani.nikula@intel.com>
Subject: Re: [PATCH v2 02/12] drm/i915/dp_mst: Simplify handling the single-bpp case during state computation
Date: Tue, 6 May 2025 13:00:06 +0300	[thread overview]
Message-ID: <aBndpioCdsEEcmRq@ideak-desk.fi.intel.com> (raw)
In-Reply-To: <b15cc451-812a-49e9-812d-7bab2807f776@intel.com>

On Tue, May 06, 2025 at 03:21:13PM +0530, Nautiyal, Ankit K wrote:
> 
> On 4/28/2025 7:01 PM, Imre Deak wrote:
> > A follow-up change wants to skip invalid bpps in the bpp select loop of
> > a stream state computation. To allow for that, using the usual
> > 'continue' statement in the loop, change the way the sinlge-bpp range is
> 
> 
> s/sinlge/single
> 
> 
> > handled.
> > 
> > Cc: Jani Nikula <jani.nikula@intel.com>
> > Signed-off-by: Imre Deak <imre.deak@intel.com>
> > ---
> >   drivers/gpu/drm/i915/display/intel_dp_mst.c | 10 ++++++----
> >   1 file changed, 6 insertions(+), 4 deletions(-)
> > 
> > diff --git a/drivers/gpu/drm/i915/display/intel_dp_mst.c b/drivers/gpu/drm/i915/display/intel_dp_mst.c
> > index 49b836cd8816c..d8033e55dc093 100644
> > --- a/drivers/gpu/drm/i915/display/intel_dp_mst.c
> > +++ b/drivers/gpu/drm/i915/display/intel_dp_mst.c
> > @@ -283,6 +283,12 @@ int intel_dp_mtp_tu_compute_config(struct intel_dp *intel_dp,
> >   					   fxp_q4_to_frac(max_bpp_x16) ||
> >   					   fxp_q4_to_frac(bpp_step_x16)));
> > +	if (!bpp_step_x16) {
> > +		/* Allow using zero step only to indicate single try for a given bpp. */
> > +		drm_WARN_ON(display->drm, min_bpp_x16 != max_bpp_x16);
> > +		bpp_step_x16 = 1;
> > +	}
> 
> I can see this function is called for non-dsc uhbr case with bpp_step_x16 =0
> and dsc false.
> 
> So we just want to get the loop run once and get the slots with min_bpp_x16
> == max_bpp_x16 == fxp_q4_from_int(pipe_bpp) right?
> 
> Similarly for dsc uhbr case check with a given compressed bpp dsc_bpp_x16 if
> its valid.
> 
> bpp_step_x16 = 1 will mean 1/16th fraction. The value itself won't have any
> effect for the case where min_bpp_x16 == max_bpp_x16.
> 
> Is my understanding correct here?

Yes, correct. On SST UHBR for each bpp a minimal link config is
selected, so this function - checking if the link config is valid - is
called for a single bpp only, hence min_bpp_x16 == max_bpp_x16.

> Regards,
> 
> Ankit
> 
> 
> 
> 
> 
> > +
> >   	if (is_mst) {
> >   		mst_state = drm_atomic_get_mst_topology_state(state, &intel_dp->mst.mgr);
> >   		if (IS_ERR(mst_state))
> > @@ -408,10 +414,6 @@ int intel_dp_mtp_tu_compute_config(struct intel_dp *intel_dp,
> >   			break;
> >   		}
> > -
> > -		/* Allow using zero step to indicate one try */
> > -		if (!bpp_step_x16)
> > -			break;
> >   	}
> >   	if (slots < 0) {

  reply	other threads:[~2025-05-06 10:00 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-28 13:31 [PATCH v2 00/12] drm/i915/dp_mst: Add support for fractional link bpps Imre Deak
2025-04-28 13:31 ` [PATCH v2 01/12] drm/i915/dp_mst: Use the correct connector while computing the link BPP limit on MST Imre Deak
2025-05-06  8:45   ` Nautiyal, Ankit K
2025-05-06  9:39   ` Luca Coelho
2025-04-28 13:31 ` [PATCH v2 02/12] drm/i915/dp_mst: Simplify handling the single-bpp case during state computation Imre Deak
2025-05-06  9:51   ` Nautiyal, Ankit K
2025-05-06 10:00     ` Imre Deak [this message]
2025-05-06 12:32       ` Nautiyal, Ankit K
2025-05-06  9:53   ` Luca Coelho
2025-04-28 13:31 ` [PATCH v2 03/12] drm/i915/dp_mst: Validate compressed bpp vs. platform restrictions Imre Deak
2025-05-06  9:54   ` Nautiyal, Ankit K
2025-05-06 10:03   ` Luca Coelho
2025-04-28 13:31 ` [PATCH v2 04/12] drm/i915/dp_mst: Update the total link slot count early Imre Deak
2025-05-06  9:55   ` Nautiyal, Ankit K
2025-05-06 10:07   ` Luca Coelho
2025-04-28 13:31 ` [PATCH v2 05/12] drm/i915/dp_mst: Check BW limit on the local MST link early Imre Deak
2025-05-06 10:06   ` Nautiyal, Ankit K
2025-04-28 13:31 ` [PATCH v2 06/12] drm/i915/dp_mst: Simplify computing the min/max compressed bpp limits Imre Deak
2025-05-06 10:11   ` Luca Coelho
2025-05-06 10:16   ` Nautiyal, Ankit K
2025-04-28 13:31 ` [PATCH v2 07/12] drm/i915/dp: Limit max link bpp properly to a fractional value on SST Imre Deak
2025-05-06 10:27   ` Luca Coelho
2025-05-06 12:34   ` Nautiyal, Ankit K
2025-04-28 13:31 ` [PATCH v2 08/12] drm/i915/dp_mst: Add support for fractional compressed link bpps on MST Imre Deak
2025-05-06 13:02   ` Nautiyal, Ankit K
2025-04-28 13:31 ` [PATCH v2 09/12] drm/i915/display: Factor out intel_display_{min, max}_pipe_bpp() Imre Deak
2025-05-06 13:07   ` Nautiyal, Ankit K
2025-05-06 15:16     ` Imre Deak
2025-05-07  3:59       ` Nautiyal, Ankit K
2025-05-07 10:58         ` Imre Deak
2025-05-07 12:44           ` Nautiyal, Ankit K
2025-04-28 13:31 ` [PATCH v2 10/12] drm/i915/dp: Export intel_dp_dsc_min_src_compressed_bpp() Imre Deak
2025-05-06 13:16   ` Nautiyal, Ankit K
2025-04-28 13:31 ` [PATCH v2 11/12] drm/i915: Add support for forcing the link bpp on a connector Imre Deak
2025-05-07  5:37   ` Nautiyal, Ankit K
2025-05-07 12:03     ` Imre Deak
2025-05-07 12:41       ` Nautiyal, Ankit K
2025-04-28 13:31 ` [PATCH v2 12/12] drm/i915/dp_mst: Enable fractional link bpps on MST if the bpp is forced Imre Deak
2025-05-06 13:15   ` Nautiyal, Ankit K
2025-04-28 13:59 ` ✓ CI.Patch_applied: success for drm/i915/dp_mst: Add support for fractional link bpps (rev2) Patchwork
2025-04-28 13:59 ` ✗ CI.checkpatch: warning " Patchwork
2025-04-28 14:00 ` ✓ CI.KUnit: success " Patchwork
2025-04-28 14:09 ` ✓ CI.Build: " Patchwork
2025-04-28 14:11 ` ✓ CI.Hooks: " Patchwork
2025-04-28 14:12 ` ✗ CI.checksparse: warning " Patchwork
2025-04-28 17:03 ` ✗ Xe.CI.Full: failure " Patchwork
2025-05-06  8:37 ` ✓ Xe.CI.BAT: 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=aBndpioCdsEEcmRq@ideak-desk.fi.intel.com \
    --to=imre.deak@intel.com \
    --cc=ankit.k.nautiyal@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=jani.nikula@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