From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: "Borah, Chaitanya Kumar" <chaitanya.kumar.borah@intel.com>
Cc: "Nautiyal, Ankit K" <ankit.k.nautiyal@intel.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>,
"jani.nikula@linux.intel.com" <jani.nikula@linux.intel.com>,
"Kandpal, Suraj" <suraj.kandpal@intel.com>,
"david.laight.linux@gmail.com" <david.laight.linux@gmail.com>,
"naresh.kamboju@linaro.org" <naresh.kamboju@linaro.org>
Subject: Re: [PATCH] drm/i915/dp: Return min bpc supported by source instead of 0
Date: Fri, 31 Jan 2025 10:20:15 -0500 [thread overview]
Message-ID: <Z5zqL0li1BWUdIgw@intel.com> (raw)
In-Reply-To: <SJ1PR11MB6129AAFC239494D560599632B9E82@SJ1PR11MB6129.namprd11.prod.outlook.com>
On Fri, Jan 31, 2025 at 01:10:25AM -0500, Borah, Chaitanya Kumar wrote:
>
>
> > -----Original Message-----
> > From: Intel-xe <intel-xe-bounces@lists.freedesktop.org> On Behalf Of Ankit
> > Nautiyal
> > Sent: Friday, January 31, 2025 9:44 AM
> > To: intel-gfx@lists.freedesktop.org; intel-xe@lists.freedesktop.org
> > Cc: jani.nikula@linux.intel.com; Kandpal, Suraj <suraj.kandpal@intel.com>;
> > Vivi, Rodrigo <rodrigo.vivi@intel.com>; david.laight.linux@gmail.com;
> > naresh.kamboju@linaro.org
> > Subject: [PATCH] drm/i915/dp: Return min bpc supported by source instead
> > of 0
> >
> > Currently, intel_dp_dsc_max_src_input_bpc can return 0 for platforms not
> > supporting DSC, which could theoretically cause issues in clamp() due to a
> > low limit being greater than the high limit.
> >
> > Instead, return the minimum bpc supported by the source to prevent such
> > issues.
> >
> > Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
> > Closes:
> > https://lore.kernel.org/all/CA+G9fYtNfM399_=_ff81zeRJv=0+z7oFJfPGmJgTp6y
> > rJmU+1w@mail.gmail.com/
> > Fixes: 160672b86b0d ("drm/i915/dp: Use clamp for pipe_bpp limits with
> > DSC")
> > Cc: Suraj Kandpal <suraj.kandpal@intel.com>
> > Cc: Jani Nikula <jani.nikula@linux.intel.com>
> > Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
> > Signed-off-by: Ankit Nautiyal <ankit.k.nautiyal@intel.com>
>
> Solves the build issue for linux-next.
>
> Tested-by: Chaitanya Kumar Borah <chaitanya.kumar.borah@intel.com>
pushed to drm-intel-next. Thank you all
>
>
>
> > ---
> > drivers/gpu/drm/i915/display/intel_dp.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/drivers/gpu/drm/i915/display/intel_dp.c
> > b/drivers/gpu/drm/i915/display/intel_dp.c
> > index 80214a559013..d28abf081844 100644
> > --- a/drivers/gpu/drm/i915/display/intel_dp.c
> > +++ b/drivers/gpu/drm/i915/display/intel_dp.c
> > @@ -1791,7 +1791,7 @@ int intel_dp_dsc_max_src_input_bpc(struct
> > intel_display *display)
> > if (DISPLAY_VER(display) == 11)
> > return 10;
> >
> > - return 0;
> > + return intel_dp_dsc_min_src_input_bpc();
> > }
> >
> > int intel_dp_dsc_compute_max_bpp(const struct intel_connector *connector,
> > --
> > 2.45.2
>
next prev parent reply other threads:[~2025-01-31 15:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-31 4:13 [PATCH] drm/i915/dp: Return min bpc supported by source instead of 0 Ankit Nautiyal
2025-01-31 4:43 ` ✓ CI.Patch_applied: success for " Patchwork
2025-01-31 4:43 ` ✓ CI.checkpatch: " Patchwork
2025-01-31 4:45 ` ✓ CI.KUnit: " Patchwork
2025-01-31 4:55 ` [PATCH] " Kandpal, Suraj
2025-01-31 5:08 ` ✓ CI.Build: success for " Patchwork
2025-01-31 5:11 ` ✓ CI.Hooks: " Patchwork
2025-01-31 5:12 ` ✓ CI.checksparse: " Patchwork
2025-01-31 5:34 ` ✓ i915.CI.BAT: " Patchwork
2025-01-31 5:38 ` ✓ Xe.CI.BAT: " Patchwork
2025-01-31 6:10 ` [PATCH] " Borah, Chaitanya Kumar
2025-01-31 15:20 ` Rodrigo Vivi [this message]
2025-01-31 7:14 ` ✗ i915.CI.Full: failure for " Patchwork
2025-01-31 7:22 ` ✗ Xe.CI.Full: " Patchwork
2025-01-31 12:27 ` ✓ i915.CI.Full: 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=Z5zqL0li1BWUdIgw@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=ankit.k.nautiyal@intel.com \
--cc=chaitanya.kumar.borah@intel.com \
--cc=david.laight.linux@gmail.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=naresh.kamboju@linaro.org \
--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.