Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: imre.deak@intel.com, intel-gfx@lists.freedesktop.org,
	intel-xe@lists.freedesktop.org
Subject: Re: [PATCH 6/6] drm/i915/mst: use min_array() and max_array() instead of hand-rolling
Date: Fri, 31 Jan 2025 11:20:22 +0200	[thread overview]
Message-ID: <87zfj7731l.fsf@intel.com> (raw)
In-Reply-To: <Z5uPGjP3hcIRhRPL@ideak-desk.fi.intel.com>

On Thu, 30 Jan 2025, Imre Deak <imre.deak@intel.com> wrote:
> On Thu, Jan 30, 2025 at 04:35:06PM +0200, Imre Deak wrote:
>> On Wed, Jan 29, 2025 at 04:46:38PM +0200, Jani Nikula wrote:
>> > Improve code clarity by using existing min_array() and max_array()
>> > helpers to find the lowest and highest values in an array.
>> > 
>> > Signed-off-by: Jani Nikula <jani.nikula@intel.com>
>> 
>> Reviewed-by: Imre Deak <imre.deak@intel.com>
>> 
>> > ---
>> >  drivers/gpu/drm/i915/display/intel_dp_mst.c | 13 +++----------
>> >  1 file changed, 3 insertions(+), 10 deletions(-)
>> > 
>> > diff --git a/drivers/gpu/drm/i915/display/intel_dp_mst.c b/drivers/gpu/drm/i915/display/intel_dp_mst.c
>> > index a4ed4f379d1e..60b003bcd1ee 100644
>> > --- a/drivers/gpu/drm/i915/display/intel_dp_mst.c
>> > +++ b/drivers/gpu/drm/i915/display/intel_dp_mst.c
>> > @@ -391,7 +391,7 @@ static int mst_stream_dsc_compute_link_config(struct intel_dp *intel_dp,
>> >  {
>> >  	struct intel_display *display = to_intel_display(intel_dp);
>> >  	struct intel_connector *connector = to_intel_connector(conn_state->connector);
>> > -	int i, num_bpc;
>> > +	int num_bpc;
>> >  	u8 dsc_bpc[3] = {};
>> >  	int min_bpp, max_bpp, sink_min_bpp, sink_max_bpp;
>> >  	int min_compressed_bpp, max_compressed_bpp;
>> > @@ -405,15 +405,8 @@ static int mst_stream_dsc_compute_link_config(struct intel_dp *intel_dp,
>> >  	drm_dbg_kms(display->drm, "DSC Source supported min bpp %d max bpp %d\n",
>> >  		    min_bpp, max_bpp);
>> >  
>> > -	sink_max_bpp = dsc_bpc[0] * 3;
>> > -	sink_min_bpp = sink_max_bpp;
>> > -
>> > -	for (i = 1; i < num_bpc; i++) {
>> > -		if (sink_min_bpp > dsc_bpc[i] * 3)
>> > -			sink_min_bpp = dsc_bpc[i] * 3;
>> > -		if (sink_max_bpp < dsc_bpc[i] * 3)
>> > -			sink_max_bpp = dsc_bpc[i] * 3;
>> > -	}
>> > +	sink_min_bpp = min_array(dsc_bpc, num_bpc) * 3;
>> > +	sink_max_bpp = max_array(dsc_bpc, num_bpc) * 3;
>
> Does linux/minmax.h need to be included explicitly for this?

It's included from kernel.h, so I figured not.

Series pushed to din, thanks for the reviews.

BR,
Jani.

>
>> >  
>> >  	drm_dbg_kms(display->drm, "DSC Sink supported min bpp %d max bpp %d\n",
>> >  		    sink_min_bpp, sink_max_bpp);
>> > -- 
>> > 2.39.5
>> > 

-- 
Jani Nikula, Intel

  reply	other threads:[~2025-01-31  9:20 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-29 14:46 [PATCH 0/6] drm/i915: DP and DP MST cleanups Jani Nikula
2025-01-29 14:46 ` [PATCH 1/6] drm/i915/dp: constify struct link_config_limits pointers Jani Nikula
2025-01-30 13:47   ` Imre Deak
2025-01-29 14:46 ` [PATCH 2/6] drm/i915/dp: change the order of intel_dp_mtp_tu_compute_config() params Jani Nikula
2025-01-30 14:03   ` Imre Deak
2025-01-29 14:46 ` [PATCH 3/6] drm/i915/mst: change where lane_count and port_clock are set Jani Nikula
2025-01-30 14:16   ` Imre Deak
2025-01-29 14:46 ` [PATCH 4/6] drm/i915/mst: handle mst pbn_div in intel_dp_mtp_tu_compute_config() Jani Nikula
2025-01-30 14:23   ` Imre Deak
2025-01-30 21:14     ` Jani Nikula
2025-01-30 21:34       ` Imre Deak
2025-01-29 14:46 ` [PATCH 5/6] drm/i915/mst: remove unnecessary mst_stream_find_vcpi_slots_for_bpp() Jani Nikula
2025-01-30 14:25   ` Imre Deak
2025-01-29 14:46 ` [PATCH 6/6] drm/i915/mst: use min_array() and max_array() instead of hand-rolling Jani Nikula
2025-01-30 14:35   ` Imre Deak
2025-01-30 14:39     ` Imre Deak
2025-01-31  9:20       ` Jani Nikula [this message]
2025-01-31  9:38         ` Raag Jadav
2025-01-29 16:31 ` ✓ CI.Patch_applied: success for series starting with [1/6] drm/i915/dp: constify struct link_config_limits pointers Patchwork
2025-01-29 16:32 ` ✓ CI.checkpatch: " Patchwork
2025-01-29 16:33 ` ✓ CI.KUnit: " Patchwork
2025-01-29 16:49 ` ✓ CI.Build: success for drm/i915: DP and DP MST cleanups Patchwork
2025-01-29 16:51 ` ✗ CI.Hooks: failure " Patchwork
2025-01-29 16:53 ` ✗ CI.checksparse: warning " Patchwork
2025-01-29 17:13 ` ✓ Xe.CI.BAT: success " Patchwork
2025-01-30  0:24 ` ✗ Xe.CI.Full: failure " 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=87zfj7731l.fsf@intel.com \
    --to=jani.nikula@intel.com \
    --cc=imre.deak@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox