From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Ville Syrjala <ville.syrjala@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 2/3] drm/i915: Assume eDP is always connected
Date: Tue, 17 Jul 2018 13:00:25 -0700 [thread overview]
Message-ID: <20180717200025.GB2233@intel.com> (raw)
In-Reply-To: <20180717174216.22252-2-ville.syrjala@linux.intel.com>
On Tue, Jul 17, 2018 at 08:42:15PM +0300, Ville Syrjala wrote:
> From: Ville Syrjälä <ville.syrjala@linux.intel.com>
>
> We never registered any kind of lid notifier for eDP, so looking at the
> lid status is pretty much bonkers. Let's just consider eDP always
> connected instead.
hm....
I've seen in the past, specially on rvps, so many times that
we detect edp or assume edp is there and it is not...
that generates a flood of aux timeout reads...
I never investigate that, but I wonder if this change here
couldn't make that case even more common...
>
> Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> ---
> drivers/gpu/drm/i915/intel_dp.c | 11 ++---------
> 1 file changed, 2 insertions(+), 9 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/intel_dp.c b/drivers/gpu/drm/i915/intel_dp.c
> index b45b08420c1f..61657b8b109c 100644
> --- a/drivers/gpu/drm/i915/intel_dp.c
> +++ b/drivers/gpu/drm/i915/intel_dp.c
> @@ -4532,14 +4532,7 @@ intel_dp_detect_dpcd(struct intel_dp *intel_dp)
> static enum drm_connector_status
> edp_detect(struct intel_dp *intel_dp)
> {
> - struct drm_i915_private *dev_priv = to_i915(intel_dp_to_dev(intel_dp));
> - enum drm_connector_status status;
> -
> - status = intel_panel_detect(dev_priv);
> - if (status == connector_status_unknown)
> - status = connector_status_connected;
> -
> - return status;
> + return connector_status_connected;
> }
>
> static bool ibx_digital_port_connected(struct intel_encoder *encoder)
> @@ -4802,7 +4795,7 @@ intel_dp_long_pulse(struct intel_connector *connector)
>
> intel_display_power_get(dev_priv, intel_dp->aux_power_domain);
>
> - /* Can't disconnect eDP, but you can close the lid... */
> + /* Can't disconnect eDP */
> if (intel_dp_is_edp(intel_dp))
> status = edp_detect(intel_dp);
> else if (intel_digital_port_connected(&dp_to_dig_port(intel_dp)->base))
> --
> 2.16.4
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2018-07-17 20:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-17 17:42 [PATCH 1/3] drm/i915: Nuke the LVDS lid notifier Ville Syrjala
2018-07-17 17:42 ` Ville Syrjala
2018-07-17 17:42 ` [PATCH 2/3] drm/i915: Assume eDP is always connected Ville Syrjala
2018-07-17 20:00 ` Rodrigo Vivi [this message]
2018-07-18 10:03 ` Ville Syrjälä
2018-07-18 21:00 ` Rodrigo Vivi
2018-07-19 10:11 ` Ville Syrjälä
2018-07-17 17:42 ` [PATCH 3/3] drm/i915: Remove intel_panel_detect() Ville Syrjala
2018-07-17 20:02 ` Rodrigo Vivi
2018-07-17 18:23 ` ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/3] drm/i915: Nuke the LVDS lid notifier Patchwork
2018-07-17 18:25 ` ✗ Fi.CI.SPARSE: " Patchwork
2018-07-17 18:47 ` ✓ Fi.CI.BAT: success " Patchwork
2018-07-17 19:57 ` [Intel-gfx] [PATCH 1/3] " Rodrigo Vivi
2018-07-17 19:57 ` Rodrigo Vivi
2018-07-18 0:34 ` ✓ Fi.CI.IGT: success for series starting with [1/3] " 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=20180717200025.GB2233@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=intel-gfx@lists.freedesktop.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.