From: "Nautiyal, Ankit K" <ankit.k.nautiyal@intel.com>
To: Suraj Kandpal <suraj.kandpal@intel.com>,
<intel-gfx@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [PATCH v2 1/2] drm/i915/dsc: Move rc param calculation for native_420
Date: Fri, 23 Jun 2023 16:29:41 +0530 [thread overview]
Message-ID: <c2d00c25-d53e-db07-6644-a83bf5a9ea38@intel.com> (raw)
In-Reply-To: <20230524025550.1345712-1-suraj.kandpal@intel.com>
On 5/24/2023 8:25 AM, Suraj Kandpal wrote:
> Move rc_param calculation for native_420 into calculate_rc_parameter.
> second_line_bpg_offset and second_line_offset_adj are both rc params
> and it would be better to have these calculated where all the other
> rc parameters are calculated.
>
> --v2
> -Add the reason for commit in commit message [Jani]
>
> Cc: Jani Nikula <jani.nikula@linux.intel.com>
> Cc: Ankit Nautiyal <ankit.k.nautiyal@intel.com>
> Signed-off-by: Suraj Kandpal <suraj.kandpal@intel.com>
> ---
> drivers/gpu/drm/i915/display/intel_vdsc.c | 28 +++++++++++++----------
> 1 file changed, 16 insertions(+), 12 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_vdsc.c b/drivers/gpu/drm/i915/display/intel_vdsc.c
> index bd9116d2cd76..c64a38363e02 100644
> --- a/drivers/gpu/drm/i915/display/intel_vdsc.c
> +++ b/drivers/gpu/drm/i915/display/intel_vdsc.c
> @@ -78,6 +78,22 @@ calculate_rc_params(struct drm_dsc_config *vdsc_cfg)
> else
> vdsc_cfg->first_line_bpg_offset = 2 * (vdsc_cfg->slice_height - 1);
>
> + /* According to DSC 1.2 specs in Section 4.1 if native_420 is set:
> + * -second_line_bpg_offset is 12 in general and equal to 2*(slice_height-1) if slice
> + * height < 8.
> + * -second_line_offset_adj is 512 as shown by emperical values to yeild best chroma
> + * preservation in second line.
> + */
> + if (vdsc_cfg->native_420) {
> + if (vdsc_cfg->slice_height >= 8)
> + vdsc_cfg->second_line_bpg_offset = 12;
> + else
> + vdsc_cfg->second_line_bpg_offset =
> + 2 * (vdsc_cfg->slice_height - 1);
> +
> + vdsc_cfg->second_line_offset_adj = 512;
> + }
> +
> /* Our hw supports only 444 modes as of today */
> if (bpp >= 12)
> vdsc_cfg->initial_offset = 2048;
> @@ -192,24 +208,12 @@ int intel_dsc_compute_params(struct intel_crtc_state *pipe_config)
> /*
> * According to DSC 1.2 specs in Section 4.1 if native_420 is set:
> * -We need to double the current bpp.
> - * -second_line_bpg_offset is 12 in general and equal to 2*(slice_height-1) if slice
> - * height < 8.
> - * -second_line_offset_adj is 512 as shown by emperical values to yeild best chroma
> - * preservation in second line.
> * -nsl_bpg_offset is calculated as second_line_offset/slice_height -1 then rounded
> * up to 16 fractional bits, we left shift second line offset by 11 to preserve 11
> * fractional bits.
> */
> if (vdsc_cfg->native_420) {
> vdsc_cfg->bits_per_pixel <<= 1;
> -
> - if (vdsc_cfg->slice_height >= 8)
> - vdsc_cfg->second_line_bpg_offset = 12;
> - else
> - vdsc_cfg->second_line_bpg_offset =
> - 2 * (vdsc_cfg->slice_height - 1);
> -
> - vdsc_cfg->second_line_offset_adj = 512;
> vdsc_cfg->nsl_bpg_offset = DIV_ROUND_UP(vdsc_cfg->second_line_bpg_offset << 11,
This seems wrong. We have removed code to set second_line_bpg_offset
from here to the function calculate_rc_params, which is called later,
but nsl_bpg_offset is using the second_line_bpg_offset.
So if we want to move the two params in calculate_rc_params, then lets
call it earlier, before these values get used.
Regards,
Ankit
> vdsc_cfg->slice_height - 1);
> }
next prev parent reply other threads:[~2023-06-23 10:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-23 10:16 [Intel-gfx] [PATCH 0/2] Add rc_range_params for YUV420 Suraj Kandpal
2023-05-23 10:16 ` [Intel-gfx] [PATCH 1/2] drm/i915/dsc: Move rc param calculation for native_420 Suraj Kandpal
2023-05-23 11:44 ` Jani Nikula
2023-05-24 2:55 ` [Intel-gfx] [PATCH v2 " Suraj Kandpal
2023-06-23 10:59 ` Nautiyal, Ankit K [this message]
2023-05-23 10:16 ` [Intel-gfx] [PATCH 2/2] drm/i915/dsc: Add rc_range_parameter calculation for YCBCR420 Suraj Kandpal
2023-05-25 11:41 ` [Intel-gfx] [PATCH v2 " Suraj Kandpal
2023-05-23 21:20 ` [Intel-gfx] ✓ Fi.CI.BAT: success for Add rc_range_params for YUV420 Patchwork
2023-05-23 23:28 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2023-05-24 3:51 ` [Intel-gfx] ✓ Fi.CI.BAT: success for Add rc_range_params for YUV420 (rev2) Patchwork
2023-05-24 14:38 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2023-05-25 19:16 ` [Intel-gfx] ✓ Fi.CI.BAT: success for Add rc_range_params for YUV420 (rev3) Patchwork
2023-05-26 5:27 ` [Intel-gfx] ✗ Fi.CI.IGT: 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=c2d00c25-d53e-db07-6644-a83bf5a9ea38@intel.com \
--to=ankit.k.nautiyal@intel.com \
--cc=intel-gfx@lists.freedesktop.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox