From: Jani Nikula <jani.nikula@linux.intel.com>
To: Ankit Nautiyal <ankit.k.nautiyal@intel.com>,
intel-gfx@lists.freedesktop.org
Cc: intel-xe@lists.freedesktop.org, suraj.kandpal@intel.com,
imre.deak@intel.com
Subject: Re: [PATCH 03/12] drm/i915/dp: Separate out helper for compute fec_enable
Date: Wed, 20 Nov 2024 13:52:24 +0200 [thread overview]
Message-ID: <871pz62kcn.fsf@intel.com> (raw)
In-Reply-To: <20241120103802.134295-4-ankit.k.nautiyal@intel.com>
On Wed, 20 Nov 2024, Ankit Nautiyal <ankit.k.nautiyal@intel.com> wrote:
> Make a separate function for setting fec_enable in crtc_state.
> Drop the check for FEC support as its already checked while checking for
> DSC support.
That's two changes that generally shouldn't be bundled together.
Aim for separating non-functional refactoring and functional
changes. (Well, arguably dropping the FEC check should also be
non-functional, but you know what I mean.)
> Signed-off-by: Ankit Nautiyal <ankit.k.nautiyal@intel.com>
> ---
> drivers/gpu/drm/i915/display/intel_dp.c | 30 +++++++++++++++++--------
> 1 file changed, 21 insertions(+), 9 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_dp.c b/drivers/gpu/drm/i915/display/intel_dp.c
> index dee15a05e7fd..d82e25d0dc5a 100644
> --- a/drivers/gpu/drm/i915/display/intel_dp.c
> +++ b/drivers/gpu/drm/i915/display/intel_dp.c
> @@ -2352,6 +2352,26 @@ static int intel_edp_dsc_compute_pipe_bpp(struct intel_dp *intel_dp,
> return 0;
> }
>
> +static void intel_dp_compute_fec_config(struct intel_dp *intel_dp,
> + struct intel_crtc_state *pipe_config)
I think all encoder->callback_name hooks should be named
something_something_callback_name(), and the same goes for helpers
specifically aimed at this.
This would make the function intel_dp_fec_compute_config().
Yes, in many ways "compute fec config" reads better, but there's value
in being able to search for "_compute_config", and to know this is only
for he ->compute_config path.
BR,
Jani.
> +{
> + if (pipe_config->fec_enable)
> + return;
> +
> + /*
> + * Though eDP v1.5 supports FEC with DSC, unlike DP, it is optional.
> + * Since, FEC is a bandwidth overhead, continue to not enable it for
> + * eDP. Until, there is a good reason to do so.
> + */
> + if (intel_dp_is_edp(intel_dp))
> + return;
> +
> + if (intel_dp_is_uhbr(pipe_config))
> + return;
> +
> + pipe_config->fec_enable = true;
> +}
> +
> int intel_dp_dsc_compute_config(struct intel_dp *intel_dp,
> struct intel_crtc_state *pipe_config,
> struct drm_connector_state *conn_state,
> @@ -2368,15 +2388,7 @@ int intel_dp_dsc_compute_config(struct intel_dp *intel_dp,
> int num_joined_pipes = intel_crtc_num_joined_pipes(pipe_config);
> int ret;
>
> - /*
> - * Though eDP v1.5 supports FEC with DSC, unlike DP, it is optional.
> - * Since, FEC is a bandwidth overhead, continue to not enable it for
> - * eDP. Until, there is a good reason to do so.
> - */
> - pipe_config->fec_enable = pipe_config->fec_enable ||
> - (!intel_dp_is_edp(intel_dp) &&
> - intel_dp_supports_fec(intel_dp, connector, pipe_config) &&
> - !intel_dp_is_uhbr(pipe_config));
> + intel_dp_compute_fec_config(intel_dp, pipe_config);
>
> if (!intel_dp_dsc_supports_format(connector, pipe_config->output_format))
> return -EINVAL;
--
Jani Nikula, Intel
next prev parent reply other threads:[~2024-11-20 11:52 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-20 10:37 [PATCH 00/12] DP DSC min/max src bpc fixes Ankit Nautiyal
2024-11-20 10:37 ` [PATCH 01/12] drm/i915/dp: Refactor FEC support check in intel_dp_supports_dsc Ankit Nautiyal
2024-11-28 12:46 ` Jani Nikula
2024-11-20 10:37 ` [PATCH 02/12] drm/i915/dp: Return early if DSC not supported Ankit Nautiyal
2024-11-27 5:43 ` Kandpal, Suraj
2024-12-03 8:32 ` Nautiyal, Ankit K
2024-12-03 8:35 ` Kandpal, Suraj
2024-11-20 10:37 ` [PATCH 03/12] drm/i915/dp: Separate out helper for compute fec_enable Ankit Nautiyal
2024-11-20 11:52 ` Jani Nikula [this message]
2024-11-20 12:37 ` Nautiyal, Ankit K
2024-11-20 12:51 ` Jani Nikula
2024-11-20 10:37 ` [PATCH 04/12] drm/i915/dp: Remove HAS_DSC macro for intel_dp_dsc_max_src_input_bpc Ankit Nautiyal
2024-11-27 5:45 ` Kandpal, Suraj
2024-11-28 10:35 ` Nautiyal, Ankit K
2024-11-20 10:37 ` [PATCH 05/12] drm/i915/dp: Return int from dsc_max/min_src_input_bpc helpers Ankit Nautiyal
2024-11-20 10:37 ` [PATCH 06/12] drm/i915/dp_mst: Use helpers to get dsc min/max input bpc Ankit Nautiyal
2024-11-20 10:37 ` [PATCH 07/12] drm/i915/dp: Drop max_requested_bpc for dsc pipe_min/max bpp Ankit Nautiyal
2024-11-20 10:37 ` [PATCH 08/12] drm/i915/dp: Refactor pipe_bpp limits with dsc Ankit Nautiyal
2024-11-20 10:37 ` [PATCH 09/12] drm/i915/dp_mst: Refactor pipe_bpp limits with dsc for mst Ankit Nautiyal
2024-11-27 5:51 ` Kandpal, Suraj
2024-11-20 10:38 ` [PATCH 10/12] drm/i915/dp: Use clamp for pipe_bpp limits with DSC Ankit Nautiyal
2024-11-20 10:38 ` [PATCH 11/12] drm/i915/dp: Make dsc helpers accept const crtc_state pointers Ankit Nautiyal
2024-11-27 5:56 ` Kandpal, Suraj
2024-11-20 10:38 ` [PATCH 12/12] drm/i915/dp: Set the DSC link limits intel_dp_compute_config_link_bpp_limits Ankit Nautiyal
2024-11-20 10:41 ` ✓ CI.Patch_applied: success for DP DSC min/max src bpc fixes (rev2) Patchwork
2024-11-20 10:42 ` ✓ CI.checkpatch: " Patchwork
2024-11-20 10:43 ` ✓ CI.KUnit: " Patchwork
2024-11-20 11:01 ` ✓ CI.Build: " Patchwork
2024-11-20 11:03 ` ✓ CI.Hooks: " Patchwork
2024-11-20 11:05 ` ✗ CI.checksparse: warning " Patchwork
2024-11-20 11:23 ` ✓ CI.BAT: success " Patchwork
2024-11-20 18:45 ` ✗ 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=871pz62kcn.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=ankit.k.nautiyal@intel.com \
--cc=imre.deak@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@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;
as well as URLs for NNTP newsgroup(s).