From: Jani Nikula <jani.nikula@intel.com>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org,
stable@vger.kernel.org
Subject: Re: [PATCH v2 1/2] drm/i915/mso: using joiner is not possible with eDP MSO
Date: Fri, 14 Jun 2024 17:01:15 +0300 [thread overview]
Message-ID: <871q4zipxw.fsf@intel.com> (raw)
In-Reply-To: <ZmwsZCkP6mobS7ki@intel.com>
On Fri, 14 Jun 2024, Ville Syrjälä <ville.syrjala@linux.intel.com> wrote:
> On Fri, Jun 14, 2024 at 01:16:03PM +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.
>>
>> While just reporting false for intel_dp_has_joiner() should be
>> sufficient, also skip creation of the joiner force enable debugfs to
>> better handle this in testing.
>>
>> 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>
>> ---
>> drivers/gpu/drm/i915/display/intel_display_debugfs.c | 8 ++++++--
>> drivers/gpu/drm/i915/display/intel_dp.c | 4 ++++
>> 2 files changed, 10 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/i915/display/intel_display_debugfs.c b/drivers/gpu/drm/i915/display/intel_display_debugfs.c
>> index 91757fed9c6d..5eb31404436c 100644
>> --- a/drivers/gpu/drm/i915/display/intel_display_debugfs.c
>> +++ b/drivers/gpu/drm/i915/display/intel_display_debugfs.c
>> @@ -1546,8 +1546,12 @@ void intel_connector_debugfs_add(struct intel_connector *connector)
>> if (DISPLAY_VER(i915) >= 11 &&
>> (connector_type == DRM_MODE_CONNECTOR_DisplayPort ||
>> connector_type == DRM_MODE_CONNECTOR_eDP)) {
>> - debugfs_create_bool("i915_bigjoiner_force_enable", 0644, root,
>> - &connector->force_bigjoiner_enable);
>> + struct intel_dp *intel_dp = intel_attached_dp(connector);
>
> That won't give you anything on MST.
Gah!
> Dunno if there's any point in
> trying to do anything here anyway. We don't account for the other
> intel_dp_has_joiner() restrictions here either.
The only point would be skipping a bunch of IGT tests. With the debugfs
in place, kms_big_joiner thinks it enables joiner, and runs extra joiner
tests for nothing.
Thoughts? I guess the simplest fix for stable could be just the last
hunk here.
BR,
Jani.
>
>> +
>> + /* eDP MSO is not compatible with joiner */
>> + if (!intel_dp->mso_link_count)
>> + debugfs_create_bool("i915_bigjoiner_force_enable", 0644, root,
>> + &connector->force_bigjoiner_enable);
>> }
>>
>> if (connector_type == DRM_MODE_CONNECTOR_DSI ||
>> 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;
>> +
>
> This part looks fine.
>
>> return DISPLAY_VER(dev_priv) >= 12 ||
>> (DISPLAY_VER(dev_priv) == 11 &&
>> encoder->port != PORT_A);
>> --
>> 2.39.2
--
Jani Nikula, Intel
next prev parent reply other threads:[~2024-06-14 14:02 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-14 10:16 [PATCH v2 0/2] drm/i915: fix MSO vs. joiner issue Jani Nikula
2024-06-14 10:16 ` [PATCH v2 1/2] drm/i915/mso: using joiner is not possible with eDP MSO Jani Nikula
2024-06-14 11:41 ` Ville Syrjälä
2024-06-14 14:01 ` Jani Nikula [this message]
2024-06-14 10:16 ` [PATCH v2 2/2] drm/i915/dsc: don't mess up splitter state in joiner or dsc config Jani Nikula
2024-06-14 11:47 ` Ville Syrjälä
2024-06-14 14:17 ` Jani Nikula
2024-06-14 14:29 ` Ville Syrjälä
2024-06-14 10:50 ` ✗ Fi.CI.SPARSE: warning for drm/i915: fix MSO vs. joiner issue Patchwork
2024-06-14 11:00 ` ✓ Fi.CI.BAT: success " Patchwork
2024-06-14 11:16 ` ✓ CI.Patch_applied: " Patchwork
2024-06-14 11:16 ` ✗ CI.checkpatch: warning " Patchwork
2024-06-14 11:17 ` ✓ CI.KUnit: success " Patchwork
2024-06-14 11:29 ` ✓ CI.Build: " Patchwork
2024-06-14 11:31 ` ✗ CI.Hooks: failure " Patchwork
2024-06-14 11:33 ` ✗ CI.checksparse: warning " Patchwork
2024-06-14 11:55 ` ✓ CI.BAT: success " Patchwork
2024-06-14 20:11 ` ✓ CI.FULL: " Patchwork
2024-06-16 7:38 ` ✗ 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=871q4zipxw.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=stable@vger.kernel.org \
--cc=ville.syrjala@linux.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 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.