From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Jani Nikula <jani.nikula@intel.com>
Cc: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org,
stable@vger.kernel.org
Subject: Re: [PATCH] drm/i915/mso: using joiner is not possible with eDP MSO
Date: Fri, 14 Jun 2024 17:39:39 +0300 [thread overview]
Message-ID: <ZmxWKyz8RcqjQ0Mg@intel.com> (raw)
In-Reply-To: <20240614142311.589089-1-jani.nikula@intel.com>
On Fri, Jun 14, 2024 at 05:23:11PM +0300, Jani Nikula wrote:
> It's not possible to use the joiner at the same time with eDP MSO. When
> a panel needs MSO, it's not optional, so MSO trumps joiner.
>
> v3: Only change intel_dp_has_joiner(), leave debugfs alone (Ville)
>
> Cc: stable@vger.kernel.org
> Cc: Ville Syrjala <ville.syrjala@linux.intel.com>
> Closes: https://gitlab.freedesktop.org/drm/xe/kernel/-/issues/1668
> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
>
> ---
>
> Just the minimal fix for starters to move things along.
> ---
> drivers/gpu/drm/i915/display/intel_dp.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_dp.c b/drivers/gpu/drm/i915/display/intel_dp.c
> index 9a9bb0f5b7fe..ab33c9de393a 100644
> --- a/drivers/gpu/drm/i915/display/intel_dp.c
> +++ b/drivers/gpu/drm/i915/display/intel_dp.c
> @@ -465,6 +465,10 @@ bool intel_dp_has_joiner(struct intel_dp *intel_dp)
> struct intel_encoder *encoder = &intel_dig_port->base;
> struct drm_i915_private *dev_priv = to_i915(encoder->base.dev);
>
> + /* eDP MSO is not compatible with joiner */
> + if (intel_dp->mso_link_count)
> + return false;
> +
> return DISPLAY_VER(dev_priv) >= 12 ||
> (DISPLAY_VER(dev_priv) == 11 &&
> encoder->port != PORT_A);
> --
> 2.39.2
--
Ville Syrjälä
Intel
next prev parent reply other threads:[~2024-06-14 14:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-14 14:23 [PATCH] drm/i915/mso: using joiner is not possible with eDP MSO Jani Nikula
2024-06-14 14:32 ` ✓ CI.Patch_applied: success for " Patchwork
2024-06-14 14:33 ` ✓ CI.checkpatch: " Patchwork
2024-06-14 14:34 ` ✓ CI.KUnit: " Patchwork
2024-06-14 14:39 ` Ville Syrjälä [this message]
2024-06-17 8:50 ` [PATCH] " Jani Nikula
2024-06-14 14:46 ` ✓ CI.Build: success for " Patchwork
2024-06-14 14:48 ` ✗ CI.Hooks: failure " Patchwork
2024-06-14 14:49 ` ✗ CI.checksparse: warning " Patchwork
2024-06-14 15:11 ` ✓ CI.BAT: success " Patchwork
2024-06-15 1:44 ` ✗ 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=ZmxWKyz8RcqjQ0Mg@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=stable@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox