From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Jani Nikula <jani.nikula@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH] drm/i915: add a note about fec_enable with 128b/132b
Date: Wed, 20 Sep 2023 15:06:24 +0300 [thread overview]
Message-ID: <ZQrgQMdyqFdRUZPs@intel.com> (raw)
In-Reply-To: <20230920112901.3315876-1-jani.nikula@intel.com>
On Wed, Sep 20, 2023 at 02:29:01PM +0300, Jani Nikula wrote:
> Add a note that fec_enable actually means FEC is to be enabled
> explicitly. 128b/132b always has FEC enabled, the driver doesn't need to
> enable it separately, and fec_enable will be false.
>
> Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> ---
> drivers/gpu/drm/i915/display/intel_display_types.h | 7 ++++++-
> 1 file changed, 6 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_display_types.h b/drivers/gpu/drm/i915/display/intel_display_types.h
> index 3c54fe2bfddd..f781a9755a52 100644
> --- a/drivers/gpu/drm/i915/display/intel_display_types.h
> +++ b/drivers/gpu/drm/i915/display/intel_display_types.h
> @@ -1364,7 +1364,12 @@ struct intel_crtc_state {
>
> bool enhanced_framing;
>
> - /* Forward Error correction State */
> + /*
> + * Forward Error Correction.
> + *
> + * Note: This will be false for 128b/132b, which will always have FEC
> + * enabled automatically.
> + */
> bool fec_enable;
>
> bool sdp_split_enable;
> --
> 2.39.2
--
Ville Syrjälä
Intel
next prev parent reply other threads:[~2023-09-20 12:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-20 11:29 [Intel-gfx] [PATCH] drm/i915: add a note about fec_enable with 128b/132b Jani Nikula
2023-09-20 12:06 ` Ville Syrjälä [this message]
2023-09-21 9:48 ` Jani Nikula
2023-09-20 15:07 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2023-09-20 21:03 ` [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=ZQrgQMdyqFdRUZPs@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@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