All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Suraj Kandpal <suraj.kandpal@intel.com>, intel-gfx@lists.freedesktop.org
Cc: juha-pekka.heikkila@intel.com, william.tseng@intel.com
Subject: Re: [Intel-gfx] [PATCH] drm/i915/dsi: Explicit first_line_bpg_offset assignment for DSI
Date: Tue, 15 Aug 2023 22:33:08 +0300	[thread overview]
Message-ID: <877cpwayob.fsf@intel.com> (raw)
In-Reply-To: <20230807142754.3891787-1-suraj.kandpal@intel.com>

On Mon, 07 Aug 2023, Suraj Kandpal <suraj.kandpal@intel.com> wrote:
> Assign explicit value of 12 at 8bpp as per Table E2 of DSC 1.1 for DSI
> panels even though we already use calculations from CModel for
> first_line_bpg_offset.
> The reason being some DSI monitors may have not have added the
> change in errata for the calculation of first_line_bpg_offset.
>
> Signed-off-by: Suraj Kandpal <suraj.kandpal@intel.com>
> ---
>  drivers/gpu/drm/i915/display/icl_dsi.c | 5 +++++
>  1 file changed, 5 insertions(+)
>
> diff --git a/drivers/gpu/drm/i915/display/icl_dsi.c b/drivers/gpu/drm/i915/display/icl_dsi.c
> index f7ebc146f96d..2376d5000d78 100644
> --- a/drivers/gpu/drm/i915/display/icl_dsi.c
> +++ b/drivers/gpu/drm/i915/display/icl_dsi.c
> @@ -1585,6 +1585,11 @@ static int gen11_dsi_dsc_compute_config(struct intel_encoder *encoder,
>  	if (ret)
>  		return ret;
>  
> +	/* From Table E-2 in DSC 1.1*/
> +	if (vdsc_cfg->dsc_version_minor == 1 &&
> +	    vdsc_cfg->bits_per_pixel == 128)

So, vdsc_cfg->bits_per_pixel has 4 fractional bits, and that's 8 bpp
compressed?

Better describe it that way, instead of as 128.

But... looking around, in intel_vdsc.c we set:

	pps_val |= DSC_BPP(vdsc_cfg->bits_per_pixel);

and we have:

	#define DSC_BPP(bpp)	((bpp) << 4)

however, when reading it back in intel_dsc_get_config(), it's just
directly:

	vdsc_cfg->bits_per_pixel = pps1;

Are we always sending x16 bpp in PPS?


BR,
Jani.



> +		vdsc_cfg->first_line_bpg_offset = 12;
> +
>  	/* DSI specific sanity checks on the common code */
>  	drm_WARN_ON(&dev_priv->drm, vdsc_cfg->vbr_enable);
>  	drm_WARN_ON(&dev_priv->drm, vdsc_cfg->simple_422);

-- 
Jani Nikula, Intel Open Source Graphics Center

  parent reply	other threads:[~2023-08-15 19:33 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-07 14:27 [Intel-gfx] [PATCH] drm/i915/dsi: Explicit first_line_bpg_offset assignment for DSI Suraj Kandpal
2023-08-07 15:48 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2023-08-07 15:48 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2023-08-07 15:56 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-08-07 21:06 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2023-08-08  8:06 ` [Intel-gfx] [PATCH] " Tseng, William
2023-08-08  8:40 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/dsi: Explicit first_line_bpg_offset assignment for DSI (rev2) Patchwork
2023-08-08  8:40 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2023-08-08  8:55 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-08-08 15:40 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2023-08-14 12:52 ` [Intel-gfx] [PATCH] drm/i915/dsi: Explicit first_line_bpg_offset assignment for DSI Suraj Kandpal
2023-08-14 15:06 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/dsi: Explicit first_line_bpg_offset assignment for DSI (rev3) Patchwork
2023-08-14 15:06 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2023-08-14 15:26 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-08-14 18:28 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2023-08-15 19:33 ` Jani Nikula [this message]
2023-08-16  6:14   ` [Intel-gfx] [PATCH] drm/i915/dsi: Explicit first_line_bpg_offset assignment for DSI Kandpal, Suraj
2023-08-16  9:55     ` Jani Nikula
2023-08-16 10:31       ` Jani Nikula
2023-08-16 10:40         ` Kandpal, Suraj
2023-08-16 10:45           ` Kandpal, Suraj
2023-08-16 12:15             ` Jani Nikula
2023-08-16 11:58           ` Jani Nikula
2023-08-16 15:50             ` Kandpal, Suraj

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=877cpwayob.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=juha-pekka.heikkila@intel.com \
    --cc=suraj.kandpal@intel.com \
    --cc=william.tseng@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.