From: Jani Nikula <jani.nikula@linux.intel.com>
To: "Borah, Chaitanya Kumar" <chaitanya.kumar.borah@intel.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>
Cc: "Deak, Imre" <imre.deak@intel.com>
Subject: RE: [PATCH] drm/i915: Preserve value of fec_enable calculated before DSC compute config
Date: Wed, 14 Aug 2024 11:45:23 +0300 [thread overview]
Message-ID: <877ccjze58.fsf@intel.com> (raw)
In-Reply-To: <SJ1PR11MB6129241F0F93400ACB2592FAB9852@SJ1PR11MB6129.namprd11.prod.outlook.com>
On Mon, 12 Aug 2024, "Borah, Chaitanya Kumar" <chaitanya.kumar.borah@intel.com> wrote:
>> -----Original Message-----
>> From: Jani Nikula <jani.nikula@linux.intel.com>
>> Sent: Monday, August 12, 2024 5:24 PM
>> To: Borah, Chaitanya Kumar <chaitanya.kumar.borah@intel.com>; intel-
>> gfx@lists.freedesktop.org; intel-xe@lists.freedesktop.org
>> Cc: Deak, Imre <imre.deak@intel.com>; Borah, Chaitanya Kumar
>> <chaitanya.kumar.borah@intel.com>
>> Subject: Re: [PATCH] drm/i915: Preserve value of fec_enable calculated before
>> DSC compute config
>>
>> On Mon, 12 Aug 2024, Chaitanya Kumar Borah
>> <chaitanya.kumar.borah@intel.com> wrote:
>> > Before DSC compute config, fec_enable value is set in other functions
>> > (e.g. intel_dp_mst_find_vcpi_slots_for_bpp). We are ignoring the value
>> > by OR'ing its value in DSC compute config. One unintended effect of
>> > this is setting fec_enable in UHBR use-cases which is not needed for
>> > Intel hardware. Therefore, change operator to AND.
>> >
>> > While at it, add a comment explaining why we don't enable FEC in eDP v1.5.
>> >
>> > Signed-off-by: Chaitanya Kumar Borah <chaitanya.kumar.borah@intel.com>
>> > ---
>> > drivers/gpu/drm/i915/display/intel_dp.c | 7 ++++++-
>> > 1 file changed, 6 insertions(+), 1 deletion(-)
>> >
>> > diff --git a/drivers/gpu/drm/i915/display/intel_dp.c
>> > b/drivers/gpu/drm/i915/display/intel_dp.c
>> > index 49a37b996530..3fbf9f33c3e4 100644
>> > --- a/drivers/gpu/drm/i915/display/intel_dp.c
>> > +++ b/drivers/gpu/drm/i915/display/intel_dp.c
>> > @@ -2298,7 +2298,12 @@ int intel_dp_dsc_compute_config(struct
>> intel_dp *intel_dp,
>> > &pipe_config->hw.adjusted_mode;
>> > int ret;
>> >
>> > - pipe_config->fec_enable = pipe_config->fec_enable ||
>> > + /*
>> > + * 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));
>>
>> With this change, FEC will only be enabled for non-UHBR MST DP and nothing
>> else. This is the place where SST DP DSC gets FEC enabled.
>
> Thank you Jani for pointing it out.
>
> Something like this should work?
>
> 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));
Technically yes, although I dislike the fact that we now have fec_enable
and its rules split to multiple locations.
BR,
Jani.
>
> Regards
>
> Chaitanya
>
>>
>> BR,
>> Jani.
>>
>>
>> --
>> Jani Nikula, Intel
--
Jani Nikula, Intel
next prev parent reply other threads:[~2024-08-14 8:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-12 8:24 [PATCH] drm/i915: Preserve value of fec_enable calculated before DSC compute config Chaitanya Kumar Borah
2024-08-12 8:34 ` ✓ CI.Patch_applied: success for " Patchwork
2024-08-12 8:34 ` ✓ CI.checkpatch: " Patchwork
2024-08-12 8:36 ` ✓ CI.KUnit: " Patchwork
2024-08-12 8:55 ` ✓ CI.Build: " Patchwork
2024-08-12 8:57 ` ✓ CI.Hooks: " Patchwork
2024-08-12 8:59 ` ✗ CI.checksparse: warning " Patchwork
2024-08-12 9:33 ` ✓ CI.BAT: success " Patchwork
2024-08-12 11:28 ` ✗ Fi.CI.BAT: failure " Patchwork
2024-08-12 11:40 ` ✗ CI.FULL: " Patchwork
2024-08-12 11:53 ` [PATCH] " Jani Nikula
2024-08-12 13:03 ` Borah, Chaitanya Kumar
2024-08-14 8:45 ` Jani Nikula [this message]
2024-08-22 6:20 ` Borah, Chaitanya Kumar
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=877ccjze58.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=chaitanya.kumar.borah@intel.com \
--cc=imre.deak@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.