From: Imre Deak <imre.deak@intel.com>
To: Jani Nikula <jani.nikula@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org,
dri-devel@lists.freedesktop.org,
Ankit Nautiyal <ankit.k.nautiyal@intel.com>
Subject: Re: [PATCH] drm: Fix DSC BPP increment decoding
Date: Thu, 13 Feb 2025 10:33:11 +0200 [thread overview]
Message-ID: <Z62uR0dPIphkgb8z@ideak-desk.fi.intel.com> (raw)
In-Reply-To: <87h64zyutr.fsf@intel.com>
On Wed, Feb 12, 2025 at 06:46:40PM +0200, Jani Nikula wrote:
> On Wed, 12 Feb 2025, Imre Deak <imre.deak@intel.com> wrote:
> > Starting with DPCD version 2.0 bits 6:3 of the DP_DSC_BITS_PER_PIXEL_INC
> > DPCD register contains the NativeYCbCr422_MAX_bpp_DELTA field, which can
> > be non-zero as opposed to earlier DPCD versions, hence decoding the
> > bit_per_pixel increment value at bits 2:0 in the same register requires
> > applying a mask, do so.
> >
> > Cc: Ankit Nautiyal <ankit.k.nautiyal@intel.com>
> > Fixes: 0c2287c96521 ("drm/display/dp: Add helper function to get DSC bpp precision")
> > Signed-off-by: Imre Deak <imre.deak@intel.com>
>
> Reviewed-by: Jani Nikula <jani.nikula@intel.com>
Thanks, patch is pushed to drm-misc-fixes.
> But we should really clean up the macros:
>
> #define DP_DSC_BITS_PER_PIXEL_INC 0x06F
> # define DP_DSC_RGB_YCbCr444_MAX_BPP_DELTA_MASK 0x1f
> # define DP_DSC_RGB_YCbCr420_MAX_BPP_DELTA_MASK 0xe0
>
> These are both for DPCD 0x6e, not 0x6f. They're misleading here. And
> they should contain the /* DP 2.0 */ comment.
>
> And a similar macro for 0x6f bits 6:3 could be added.
Ok, noted. Decoding and using these caps is still missing, the above
could be fixed when adding that.
>
> BR,
> Jani.
>
>
> > ---
> > drivers/gpu/drm/display/drm_dp_helper.c | 2 +-
> > include/drm/display/drm_dp.h | 1 +
> > 2 files changed, 2 insertions(+), 1 deletion(-)
> >
> > diff --git a/drivers/gpu/drm/display/drm_dp_helper.c b/drivers/gpu/drm/display/drm_dp_helper.c
> > index c488d160a3c1f..f5c596234729d 100644
> > --- a/drivers/gpu/drm/display/drm_dp_helper.c
> > +++ b/drivers/gpu/drm/display/drm_dp_helper.c
> > @@ -2602,7 +2602,7 @@ u8 drm_dp_dsc_sink_bpp_incr(const u8 dsc_dpcd[DP_DSC_RECEIVER_CAP_SIZE])
> > {
> > u8 bpp_increment_dpcd = dsc_dpcd[DP_DSC_BITS_PER_PIXEL_INC - DP_DSC_SUPPORT];
> >
> > - switch (bpp_increment_dpcd) {
> > + switch (bpp_increment_dpcd & DP_DSC_BITS_PER_PIXEL_MASK) {
> > case DP_DSC_BITS_PER_PIXEL_1_16:
> > return 16;
> > case DP_DSC_BITS_PER_PIXEL_1_8:
> > diff --git a/include/drm/display/drm_dp.h b/include/drm/display/drm_dp.h
> > index 784a32bfbad8f..c413ef68f9a30 100644
> > --- a/include/drm/display/drm_dp.h
> > +++ b/include/drm/display/drm_dp.h
> > @@ -359,6 +359,7 @@
> > # define DP_DSC_BITS_PER_PIXEL_1_4 0x2
> > # define DP_DSC_BITS_PER_PIXEL_1_2 0x3
> > # define DP_DSC_BITS_PER_PIXEL_1_1 0x4
> > +# define DP_DSC_BITS_PER_PIXEL_MASK 0x7
> >
> > #define DP_PSR_SUPPORT 0x070 /* XXX 1.2? */
> > # define DP_PSR_IS_SUPPORTED 1
>
> --
> Jani Nikula, Intel
next prev parent reply other threads:[~2025-02-13 8:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-12 16:18 [PATCH] drm: Fix DSC BPP increment decoding Imre Deak
2025-02-12 16:46 ` Jani Nikula
2025-02-13 8:33 ` Imre Deak [this message]
2025-02-12 18:03 ` ✓ CI.Patch_applied: success for " Patchwork
2025-02-12 18:03 ` ✓ CI.checkpatch: " Patchwork
2025-02-12 18:04 ` ✓ CI.KUnit: " Patchwork
2025-02-12 18:21 ` ✓ CI.Build: " Patchwork
2025-02-12 18:23 ` ✓ CI.Hooks: " Patchwork
2025-02-12 18:25 ` ✓ CI.checksparse: " Patchwork
2025-02-12 18:46 ` ✓ Xe.CI.BAT: " Patchwork
2025-02-12 19:49 ` ✗ Fi.CI.SPARSE: warning " Patchwork
2025-02-12 20:04 ` ✓ i915.CI.BAT: success " Patchwork
2025-02-13 2:07 ` ✗ Xe.CI.Full: failure " Patchwork
2025-02-13 4:29 ` ✗ i915.CI.Full: " 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=Z62uR0dPIphkgb8z@ideak-desk.fi.intel.com \
--to=imre.deak@intel.com \
--cc=ankit.k.nautiyal@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.nikula@linux.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.