From: Imre Deak <imre.deak@intel.com>
To: "Souza, Jose" <jose.souza@intel.com>,
Jani Nikula <jani.nikula@intel.com>
Cc: "intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"Zanoni, Paulo R" <paulo.r.zanoni@intel.com>
Subject: Re: [PATCH v2 12/23] drm/i915: Sanitize the TypeC connect/detect sequences
Date: Thu, 27 Jun 2019 12:48:37 +0300 [thread overview]
Message-ID: <20190627094837.GA23002@ideak-desk.fi.intel.com> (raw)
In-Reply-To: <d3163b2e4ffb41c9c9d59f6d196fee75bacdee81.camel@intel.com>
On Thu, Jun 27, 2019 at 02:55:21AM +0300, Souza, Jose wrote:
> On Thu, 2019-06-20 at 17:05 +0300, Imre Deak wrote:
> > Make the order during detection more consistent: first reset the
> > TypeC
> > port mode if needed (adding new helpers for this), then detect any
> > connected sink.
> >
> > To check if a port mode reset is needed determine first the target
> > port
> > mode based on the live status if a sink is already connected or the
> > PHY status complete flag otherwise.
> >
> > Add a WARN in legacy mode if unexpectedly we can't set the unsafe
> > mode
> > or if the FIA doesn't provide the 4 lanes required.
> >
> > Cc: José Roberto de Souza <jose.souza@intel.com>
> > Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
> > Cc: Paulo Zanoni <paulo.r.zanoni@intel.com>
> > Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > Signed-off-by: Imre Deak <imre.deak@intel.com>
> > ---
> > drivers/gpu/drm/i915/display/intel_tc.c | 96 ++++++++++++-----------
> > --
> > 1 file changed, 47 insertions(+), 49 deletions(-)
> >
> > diff --git a/drivers/gpu/drm/i915/display/intel_tc.c
> > b/drivers/gpu/drm/i915/display/intel_tc.c
> > index fffe4c4a6602..ed2253b21b09 100644
> > --- a/drivers/gpu/drm/i915/display/intel_tc.c
> > +++ b/drivers/gpu/drm/i915/display/intel_tc.c
> > @@ -172,41 +172,43 @@ static bool icl_tc_phy_set_safe_mode(struct
> > intel_digital_port *dig_port,
> > * will require a lot of coordination with user space and thorough
> > testing for
> > * the extra possible cases.
> > */
> > -static bool icl_tc_phy_connect(struct intel_digital_port *dig_port)
> > +static void icl_tc_phy_connect(struct intel_digital_port *dig_port)
> > {
> > - u32 live_status_mask;
> > -
> > - if (dig_port->tc_mode != TC_PORT_LEGACY &&
> > - dig_port->tc_mode != TC_PORT_DP_ALT)
> > - return true;
> > -
> > if (!icl_tc_phy_status_complete(dig_port)) {
> > DRM_DEBUG_KMS("Port %s: PHY not ready\n",
> > dig_port->tc_port_name);
> > - WARN_ON(dig_port->tc_legacy_port);
> > - return false;
> > + goto out_set_tbt_alt_mode;
> > }
> >
> > - if (!icl_tc_phy_set_safe_mode(dig_port, false))
> > - return false;
> > + if (!icl_tc_phy_set_safe_mode(dig_port, false) &&
> > + !WARN_ON(dig_port->tc_legacy_port))
> > + goto out_set_tbt_alt_mode;
>
> Marking as not safe even for TBT?
You mean if the above will set not-safe mode even for TBT? No, we
will try to set not-safe mode only for DP-alt and legacy as the PHY
status complete flag was set.
>
> >
> > - if (dig_port->tc_mode == TC_PORT_LEGACY)
> > - return true;
> > + if (dig_port->tc_legacy_port) {
> > + WARN_ON(intel_tc_port_fia_max_lane_count(dig_port) !=
> > 4);
> > + dig_port->tc_mode = TC_PORT_LEGACY;
> >
> > - live_status_mask = tc_port_live_status_mask(dig_port);
> > + return;
> > + }
> >
> > /*
> > * Now we have to re-check the live state, in case the port
> > recently
> > * became disconnected. Not necessary for legacy mode.
> > */
> > - if (!(live_status_mask & BIT(TC_PORT_DP_ALT))) {
> > + if (!(tc_port_live_status_mask(dig_port) &
> > BIT(TC_PORT_DP_ALT))) {
> > DRM_DEBUG_KMS("Port %s: PHY sudden disconnect\n",
> > dig_port->tc_port_name);
> > - icl_tc_phy_disconnect(dig_port);
> > - return false;
> > + goto out_set_safe_mode;
> > }
> >
> > - return true;
> > + dig_port->tc_mode = TC_PORT_DP_ALT;
> > +
> > + return;
> > +
> > +out_set_safe_mode:
> > + icl_tc_phy_set_safe_mode(dig_port, true);
> > +out_set_tbt_alt_mode:
> > + dig_port->tc_mode = TC_PORT_TBT_ALT;
> > }
> >
> > /*
> > @@ -227,27 +229,37 @@ void icl_tc_phy_disconnect(struct
> > intel_digital_port *dig_port)
> > default:
> > MISSING_CASE(dig_port->tc_mode);
> > }
> > +}
> >
> > - DRM_DEBUG_KMS("Port %s: mode %s disconnected\n",
> > - dig_port->tc_port_name,
> > - tc_port_mode_name(dig_port->tc_mode));
> > +static enum tc_port_mode
> > +intel_tc_port_get_target_mode(struct intel_digital_port *dig_port)
> > +{
> > + u32 live_status_mask = tc_port_live_status_mask(dig_port);
> > +
> > + if (live_status_mask)
> > + return fls(live_status_mask) - 1;
> > +
> > + return icl_tc_phy_status_complete(dig_port) &&
> > + dig_port->tc_legacy_port ? TC_PORT_LEGACY :
> > + TC_PORT_TBT_ALT;
>
> You are right about the order that C will execute this but could you
> add a pair of parenthesis around icl_tc_phy_status_complete(dig_port)
> && dig_port->tc_legacy_port to make easier to read?
Not sure, I think the use of 'a && b ? c : d' without parens is usual
enough, but maybe others have a better idea for a rule-of-thumb for
using parens that we should follow everywhere. Jani?
Anyway the following would be easier to read (also we can avoid the reg
read for the !legacy case):
if (dig_port->tc_legacy_port &&
icl_tc_phy_status_complete(dig_port))
return TC_PORT_LEGACY;
return TC_PORT_TBT_ALT;
>
> > }
> >
> > -static void icl_update_tc_port_type(struct drm_i915_private
> > *dev_priv,
> > - struct intel_digital_port
> > *intel_dig_port,
> > - u32 live_status_mask)
> > +static void intel_tc_port_reset_mode(struct intel_digital_port
> > *dig_port)
> > {
> > - enum tc_port_mode old_mode = intel_dig_port->tc_mode;
> > + enum tc_port_mode old_tc_mode = dig_port->tc_mode;
> >
> > - if (!live_status_mask)
> > - return;
> > + icl_tc_phy_disconnect(dig_port);
> > + icl_tc_phy_connect(dig_port);
> >
> > - intel_dig_port->tc_mode = fls(live_status_mask) - 1;
> > + DRM_DEBUG_KMS("Port %s: TC port mode reset (%s -> %s)\n",
> > + dig_port->tc_port_name,
> > + tc_port_mode_name(old_tc_mode),
> > + tc_port_mode_name(dig_port->tc_mode));
> > +}
> >
> > - if (old_mode != intel_dig_port->tc_mode)
> > - DRM_DEBUG_KMS("Port %s: port has mode %s\n",
> > - intel_dig_port->tc_port_name,
> > - tc_port_mode_name(intel_dig_port-
> > >tc_mode));
> > +static bool intel_tc_port_needs_reset(struct intel_digital_port
> > *dig_port)
> > +{
> > + return intel_tc_port_get_target_mode(dig_port) != dig_port-
> > >tc_mode;
> > }
> >
> > /*
> > @@ -262,24 +274,10 @@ static void icl_update_tc_port_type(struct
> > drm_i915_private *dev_priv,
> > */
> > bool intel_tc_port_connected(struct intel_digital_port *dig_port)
> > {
> > - struct drm_i915_private *dev_priv = to_i915(dig_port-
> > >base.base.dev);
> > - u32 live_status_mask = tc_port_live_status_mask(dig_port);
> > -
> > - /*
> > - * The spec says we shouldn't be using the ISR bits for
> > detecting
> > - * between TC and TBT. We should use DFLEXDPSP.
> > - */
> > - if (!live_status_mask && !dig_port->tc_legacy_port) {
> > - icl_tc_phy_disconnect(dig_port);
> > -
> > - return false;
> > - }
> > -
> > - icl_update_tc_port_type(dev_priv, dig_port, live_status_mask);
> > - if (!icl_tc_phy_connect(dig_port))
> > - return false;
> > + if (intel_tc_port_needs_reset(dig_port))
> > + intel_tc_port_reset_mode(dig_port);
> >
> > - return true;
> > + return tc_port_live_status_mask(dig_port) & BIT(dig_port-
> > >tc_mode);
> > }
> >
> > void intel_tc_port_init(struct intel_digital_port *dig_port, bool
> > is_legacy)
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-06-27 9:48 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-20 14:05 [PATCH v2 00/23] drm/i915: Fix TypeC port mode switching Imre Deak
2019-06-20 14:05 ` [PATCH v2 01/23] drm/i915/icl: Add support to read out the TBT PLL HW state Imre Deak
2019-06-20 14:05 ` [PATCH v2 02/23] drm/i915: Tune down WARNs about TBT AUX power well enabling Imre Deak
2019-06-20 14:05 ` [PATCH v2 03/23] drm/i915: Move the TypeC port handling code to a separate file Imre Deak
2019-06-20 14:05 ` [PATCH v2 04/23] drm/i915: Sanitize the terminology used for TypeC port modes Imre Deak
2019-06-20 14:05 ` [PATCH v2 05/23] drm/i915: Don't enable the DDI-IO power in the TypeC TBT-alt mode Imre Deak
2019-06-20 14:05 ` [PATCH v2 06/23] drm/i915: Fix the TBT AUX power well enabling Imre Deak
2019-06-20 14:05 ` [PATCH v2 07/23] drm/i915: Use the correct AUX power domain in TypeC TBT-alt mode Imre Deak
2019-06-20 14:05 ` [PATCH v2 08/23] drm/i915: Unify the TypeC port notation in debug/error messages Imre Deak
2019-06-20 14:05 ` [PATCH v2 09/23] drm/i915: Factor out common parts from TypeC port handling functions Imre Deak
2019-06-25 13:05 ` Ville Syrjälä
2019-06-25 13:48 ` Imre Deak
2019-06-26 20:50 ` [CI v3 " Imre Deak
2019-06-26 22:55 ` Souza, Jose
2019-06-27 10:34 ` Imre Deak
2019-06-20 14:05 ` [PATCH v2 10/23] drm/i915: Wait for TypeC PHY complete flag to clear in safe mode Imre Deak
2019-06-20 14:05 ` [PATCH v2 11/23] drm/i915: Handle the TCCOLD power-down event Imre Deak
2019-06-25 13:17 ` Ville Syrjälä
2019-06-25 14:22 ` Imre Deak
2019-06-26 20:50 ` [CI v3 " Imre Deak
2019-06-20 14:05 ` [PATCH v2 12/23] drm/i915: Sanitize the TypeC connect/detect sequences Imre Deak
2019-06-25 13:42 ` Ville Syrjälä
2019-06-25 18:30 ` Imre Deak
2019-06-26 11:51 ` Ville Syrjälä
2019-06-26 23:55 ` Souza, Jose
2019-06-27 9:48 ` Imre Deak [this message]
2019-06-27 21:06 ` Souza, Jose
2019-06-20 14:05 ` [PATCH v2 13/23] drm/i915: Fix the TypeC port mode sanitization during loading/resume Imre Deak
2019-06-26 18:04 ` [PATCH v3 " Imre Deak
2019-06-26 20:50 ` [CI " Imre Deak
2019-06-27 20:38 ` Souza, Jose
2019-06-20 14:05 ` [PATCH v2 14/23] drm/i915: Keep the TypeC port mode fixed for detect/AUX transfers Imre Deak
2019-06-25 13:43 ` Ville Syrjälä
2019-06-20 14:05 ` [PATCH v2 15/23] drm/i915: Sanitize the TypeC FIA lane configuration decoding Imre Deak
2019-06-20 14:05 ` [PATCH v2 16/23] drm/i915: Sanitize the shared DPLL reserve/release interface Imre Deak
2019-06-25 13:53 ` Ville Syrjälä
2019-06-25 18:57 ` Imre Deak
2019-06-25 19:48 ` Imre Deak
2019-06-20 14:05 ` [PATCH v2 17/23] drm/i915: Sanitize the shared DPLL find/reference interface Imre Deak
2019-06-25 13:54 ` Ville Syrjälä
2019-06-20 14:05 ` [PATCH v2 18/23] drm/i915/icl: Split getting the DPLLs to port type specific functions Imre Deak
2019-06-25 13:55 ` Ville Syrjälä
2019-06-20 14:05 ` [PATCH v2 19/23] drm/i915/icl: Reserve all required PLLs for TypeC ports Imre Deak
2019-06-25 13:58 ` Ville Syrjälä
2019-06-20 14:05 ` [PATCH v2 20/23] drm/i915: Keep the TypeC port mode fixed when the port is active Imre Deak
2019-06-25 14:01 ` Ville Syrjälä
2019-06-20 14:05 ` [PATCH v2 21/23] drm/i915: Add state verification for the TypeC port mode Imre Deak
2019-06-25 14:12 ` Ville Syrjälä
2019-06-25 19:23 ` Imre Deak
2019-06-26 11:52 ` Ville Syrjälä
2019-06-26 18:04 ` [v3 " Imre Deak
2019-06-26 20:50 ` [CI v3 " Imre Deak
2019-06-20 14:05 ` [PATCH v2 22/23] drm/i915: Remove unneeded disconnect in TypeC legacy " Imre Deak
2019-06-20 14:06 ` [PATCH v2 23/23] drm/i915: WARN about invalid lane reversal in TBT-alt/DP-alt modes Imre Deak
2019-06-20 17:23 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Fix TypeC port mode switching (rev3) Patchwork
2019-06-20 17:32 ` ✗ Fi.CI.SPARSE: " Patchwork
2019-06-20 18:05 ` ✓ Fi.CI.BAT: success " Patchwork
2019-06-20 22:42 ` ✓ Fi.CI.IGT: " Patchwork
2019-06-26 22:00 ` ✗ Fi.CI.BAT: failure for drm/i915: Fix TypeC port mode switching (rev7) Patchwork
-- strict thread matches above, loose matches on Subject: below --
2019-06-26 18:04 [PATCH v3 09/23] drm/i915: Factor out common parts from TypeC port handling functions Imre Deak
2019-06-26 18:04 ` [PATCH v3 11/23] drm/i915: Handle the TCCOLD power-down event Imre Deak
2019-06-26 22:12 ` Souza, Jose
2019-06-27 10:09 ` Imre Deak
2019-06-27 12:59 ` Ville Syrjälä
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=20190627094837.GA23002@ideak-desk.fi.intel.com \
--to=imre.deak@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=jose.souza@intel.com \
--cc=paulo.r.zanoni@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