From: "Hogander, Jouni" <jouni.hogander@intel.com>
To: "intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>,
"Sharma, Swati2" <swati2.sharma@intel.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>
Cc: "Garg, Nemesa" <nemesa.garg@intel.com>
Subject: Re: [PATCH] drm/i915/dsc: Expose dsc sink max slice count via debugfs
Date: Tue, 17 Dec 2024 09:23:17 +0000 [thread overview]
Message-ID: <5fc156c887052cb35d13b0fc17fef3afed4d89f2.camel@intel.com> (raw)
In-Reply-To: <20241213093008.2149452-1-swati2.sharma@intel.com>
On Fri, 2024-12-13 at 15:00 +0530, Swati Sharma wrote:
> Number of DSC slices can be shown in the DSC debugfs so that
> test can take a call whether the configuration can support forcing
> bigjoiner/ultrajoiner.
>
This is now pushed to drm-intel-next.
BR,
Jouni Högander
> v2: used intel_dp_is_edp() as the parameter to
> drm_dp_dsc_sink_max_slice_count() (Jani N)
>
> Reviewed-by: Nemesa Garg <nemesa.garg@intel.com> (v1)
> Closes: https://gitlab.freedesktop.org/drm/xe/kernel/-/issues/3387
> Signed-off-by: Swati Sharma <swati2.sharma@intel.com>
> ---
> drivers/gpu/drm/i915/display/intel_display_debugfs.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_display_debugfs.c
> b/drivers/gpu/drm/i915/display/intel_display_debugfs.c
> index 3eb7565cd83c..a7c744654274 100644
> --- a/drivers/gpu/drm/i915/display/intel_display_debugfs.c
> +++ b/drivers/gpu/drm/i915/display/intel_display_debugfs.c
> @@ -1013,6 +1013,8 @@ static int i915_dsc_fec_support_show(struct
> seq_file *m, void *data)
>
> DP_DSC_YCbCr444)));
> seq_printf(m, "DSC_Sink_BPP_Precision: %d\n",
> drm_dp_dsc_sink_bpp_incr(connector-
> >dp.dsc_dpcd));
> + seq_printf(m, "DSC_Sink_Max_Slice_Count: %d\n",
> +
> drm_dp_dsc_sink_max_slice_count((connector->dp.dsc_dpcd),
> intel_dp_is_edp(intel_dp)));
> seq_printf(m, "Force_DSC_Enable: %s\n",
> str_yes_no(intel_dp->force_dsc_en));
> if (!intel_dp_is_edp(intel_dp))
prev parent reply other threads:[~2024-12-17 9:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-13 9:30 [PATCH] drm/i915/dsc: Expose dsc sink max slice count via debugfs Swati Sharma
2024-12-13 11:04 ` ✓ CI.Patch_applied: success for " Patchwork
2024-12-13 11:04 ` ✗ CI.checkpatch: warning " Patchwork
2024-12-13 11:05 ` ✓ CI.KUnit: success " Patchwork
2024-12-13 11:23 ` ✓ CI.Build: " Patchwork
2024-12-13 11:26 ` ✓ CI.Hooks: " Patchwork
2024-12-13 11:27 ` ✓ CI.checksparse: " Patchwork
2024-12-13 11:58 ` ✓ Xe.CI.BAT: " Patchwork
2024-12-13 20:14 ` ✗ Xe.CI.Full: failure " Patchwork
2024-12-17 9:23 ` Hogander, Jouni [this message]
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=5fc156c887052cb35d13b0fc17fef3afed4d89f2.camel@intel.com \
--to=jouni.hogander@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=nemesa.garg@intel.com \
--cc=swati2.sharma@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