From: "Kulkarni, Vandita" <vandita.kulkarni@intel.com>
To: "Nikula, Jani" <jani.nikula@intel.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>
Cc: "Nikula, Jani" <jani.nikula@intel.com>,
"Navare, Manasi D" <manasi.d.navare@intel.com>
Subject: RE: [PATCH RESEND 6/7] drm/i915/bios: fill in DSC rc_model_size from VBT
Date: Wed, 8 Apr 2020 10:04:19 +0000 [thread overview]
Message-ID: <57510F3E2013164E925CD03ED7512A3B80A88437@BGSMSX108.gar.corp.intel.com> (raw)
In-Reply-To: <20200327124229.26461-6-jani.nikula@intel.com>
> -----Original Message-----
> From: Jani Nikula <jani.nikula@intel.com>
> Sent: Friday, March 27, 2020 6:12 PM
> To: intel-gfx@lists.freedesktop.org; dri-devel@lists.freedesktop.org
> Cc: Nikula, Jani <jani.nikula@intel.com>; Navare, Manasi D
> <manasi.d.navare@intel.com>; Kulkarni, Vandita <vandita.kulkarni@intel.com>
> Subject: [PATCH RESEND 6/7] drm/i915/bios: fill in DSC rc_model_size from
> VBT
>
> The VBT fields match the DPCD data, so use the same helper.
>
> Cc: Manasi Navare <manasi.d.navare@intel.com>
> Cc: Vandita Kulkarni <vandita.kulkarni@intel.com>
> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
> ---
> drivers/gpu/drm/i915/display/intel_bios.c | 11 +++--------
> 1 file changed, 3 insertions(+), 8 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_bios.c
> b/drivers/gpu/drm/i915/display/intel_bios.c
> index 839124647202..a4ea0e6c3286 100644
> --- a/drivers/gpu/drm/i915/display/intel_bios.c
> +++ b/drivers/gpu/drm/i915/display/intel_bios.c
> @@ -2494,16 +2494,11 @@ static void fill_dsc(struct intel_crtc_state
> *crtc_state,
> crtc_state->dsc.slice_count);
>
> /*
> - * FIXME: Use VBT rc_buffer_block_size and rc_buffer_size for the
> - * implementation specific physical rate buffer size. Currently we use
> - * the required rate buffer model size calculated in
> - * drm_dsc_compute_rc_parameters() according to VESA DSC Annex E.
> - *
> * The VBT rc_buffer_block_size and rc_buffer_size definitions
> - * correspond to DP 1.4 DPCD offsets 0x62 and 0x63. The DP DSC
> - * implementation should also use the DPCD (or perhaps VBT for eDP)
> - * provided value for the buffer size.
> + * correspond to DP 1.4 DPCD offsets 0x62 and 0x63.
> */
> + vdsc_cfg->rc_model_size = drm_dsc_dp_rc_buffer_size(dsc-
> >rc_buffer_block_size,
> + dsc-
> >rc_buffer_size);
Do we need to handle the invalid case here?
Regards
Vandita
>
> /* FIXME: DSI spec says bpc + 1 for this one */
> vdsc_cfg->line_buf_depth = VBT_DSC_LINE_BUFFER_DEPTH(dsc-
> >line_buffer_depth);
> --
> 2.20.1
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2020-04-08 10:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-27 12:42 [PATCH RESEND 1/7] drm/dsc: use rc_model_size from DSC config for PPS Jani Nikula
2020-03-27 12:42 ` [PATCH RESEND 2/7] drm/dsc: add helper for calculating rc buffer size from DPCD Jani Nikula
2020-04-08 9:50 ` Kulkarni, Vandita
2020-03-27 12:42 ` [PATCH RESEND 3/7] drm/amd/display: use drm_dsc_dp_rc_buffer_size() to get rc buffer size Jani Nikula
2020-03-27 12:42 ` [PATCH RESEND 4/7] drm/i915/dsc: configure hardware using specified rc_model_size Jani Nikula
2020-04-08 10:00 ` Kulkarni, Vandita
2020-03-27 12:42 ` [PATCH RESEND 5/7] drm/i915/dsc: make rc_model_size an encoder defined value Jani Nikula
2020-03-27 12:42 ` [PATCH RESEND 6/7] drm/i915/bios: fill in DSC rc_model_size from VBT Jani Nikula
2020-04-08 10:04 ` Kulkarni, Vandita [this message]
2020-03-27 12:42 ` [PATCH RESEND 7/7] drm/i915/dsi: use VBT data for rc_model_size Jani Nikula
2020-04-08 9:46 ` [PATCH RESEND 1/7] drm/dsc: use rc_model_size from DSC config for PPS Kulkarni, Vandita
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=57510F3E2013164E925CD03ED7512A3B80A88437@BGSMSX108.gar.corp.intel.com \
--to=vandita.kulkarni@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=manasi.d.navare@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;
as well as URLs for NNTP newsgroup(s).