From: Jani Nikula <jani.nikula@linux.intel.com>
To: Swati Sharma <swati2.sharma@intel.com>, intel-xe@lists.freedesktop.org
Cc: Swati Sharma <swati2.sharma@intel.com>
Subject: Re: [PATCH 1/1] drm/i915/dsc: Expose dsc sink max slice count via debugfs
Date: Wed, 11 Dec 2024 11:31:09 +0200 [thread overview]
Message-ID: <87y10my3aa.fsf@intel.com> (raw)
In-Reply-To: <20241210164252.2118155-2-swati2.sharma@intel.com>
On Tue, 10 Dec 2024, Swati Sharma <swati2.sharma@intel.com> wrote:
> Expose dsc sink max slice count via i915_dsc_fec_support debugfs.
> This debugfs entry is required in cases, where sink doesn't support
> minimum of 8 slices in case of ultrajoiner and minimum of 4 slices
> in case of big joiner.
>
> 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 | 6 ++++++
> 1 file changed, 6 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..4823d27cafb5 100644
> --- a/drivers/gpu/drm/i915/display/intel_display_debugfs.c
> +++ b/drivers/gpu/drm/i915/display/intel_display_debugfs.c
> @@ -1013,6 +1013,12 @@ 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));
> + if (intel_dp_is_edp(intel_dp))
> + seq_printf(m, "DSC_Sink_Max_Slice_Count: %d\n",
> + drm_dp_dsc_sink_max_slice_count((connector->dp.dsc_dpcd), true));
> + else
> + seq_printf(m, "DSC_Sink_Max_Slice_Count: %d\n",
> + drm_dp_dsc_sink_max_slice_count((connector->dp.dsc_dpcd), false));
Maybe just use intel_dp_is_edp() as the parameter to
drm_dp_dsc_sink_max_slice_count() instead of duplicating the whole
statement?
BR,
Jani.
> seq_printf(m, "Force_DSC_Enable: %s\n",
> str_yes_no(intel_dp->force_dsc_en));
> if (!intel_dp_is_edp(intel_dp))
--
Jani Nikula, Intel
next prev parent reply other threads:[~2024-12-11 9:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-10 16:42 [PATCH 0/1] Expose dsc sink max slice count via debugfs Swati Sharma
2024-12-10 16:42 ` [PATCH 1/1] drm/i915/dsc: " Swati Sharma
2024-12-11 9:31 ` Jani Nikula [this message]
2024-12-13 12:54 ` Sharma, Swati2
2024-12-10 20:00 ` ✓ CI.Patch_applied: success for " Patchwork
2024-12-10 20:00 ` ✗ CI.checkpatch: warning " Patchwork
2024-12-10 20:02 ` ✓ CI.KUnit: success " Patchwork
2024-12-10 20:21 ` ✓ CI.Build: " Patchwork
2024-12-10 20:25 ` ✓ CI.Hooks: " Patchwork
2024-12-10 20:27 ` ✓ CI.checksparse: " Patchwork
2024-12-10 20:53 ` ✓ Xe.CI.BAT: " Patchwork
2024-12-10 23:06 ` ✗ Xe.CI.Full: 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=87y10my3aa.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=intel-xe@lists.freedesktop.org \
--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;
as well as URLs for NNTP newsgroup(s).