From: Lyude Paul <lyude@redhat.com>
To: dri-devel@lists.freedesktop.org, nouveau@lists.freedesktop.org,
intel-gfx@lists.freedesktop.org
Cc: Jani Nikula <jani.nikula@intel.com>,
David Airlie <airlied@linux.ie>,
open list <linux-kernel@vger.kernel.org>,
greg.depoire@gmail.com, Ben Skeggs <bskeggs@redhat.com>,
Daniel Vetter <daniel@ffwll.ch>
Subject: [Nouveau] [RFC v4 02/11] drm/nouveau/kms: Don't probe eDP connectors more then once
Date: Mon, 8 Feb 2021 18:38:52 -0500 [thread overview]
Message-ID: <20210208233902.1289693-3-lyude@redhat.com> (raw)
In-Reply-To: <20210208233902.1289693-1-lyude@redhat.com>
eDP doesn't do hotplugging, so there's no reason for us to reprobe it (unless a
connection status change is being forced, of course).
Signed-off-by: Lyude Paul <lyude@redhat.com>
Cc: Jani Nikula <jani.nikula@intel.com>
Cc: Dave Airlie <airlied@gmail.com>
Cc: greg.depoire@gmail.com
---
drivers/gpu/drm/nouveau/nouveau_connector.c | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/drivers/gpu/drm/nouveau/nouveau_connector.c b/drivers/gpu/drm/nouveau/nouveau_connector.c
index 61e6d7412505..55e986b3cad9 100644
--- a/drivers/gpu/drm/nouveau/nouveau_connector.c
+++ b/drivers/gpu/drm/nouveau/nouveau_connector.c
@@ -556,6 +556,12 @@ nouveau_connector_detect(struct drm_connector *connector, bool force)
int ret;
enum drm_connector_status conn_status = connector_status_disconnected;
+ /* eDP doesn't do hotplugging, never probe more then once */
+ if (nv_connector->type == DCB_CONNECTOR_eDP &&
+ connector->force == DRM_FORCE_UNSPECIFIED &&
+ connector->status != connector_status_unknown)
+ return connector->status;
+
/* Outputs are only polled while runtime active, so resuming the
* device here is unnecessary (and would deadlock upon runtime suspend
* because it waits for polling to finish). We do however, want to
--
2.29.2
_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/nouveau
next prev parent reply other threads:[~2021-02-08 23:39 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-08 23:38 [Nouveau] [RFC v4 00/11] drm: Extract DPCD backlight helpers from i915, add support in nouveau Lyude Paul
2021-02-08 23:38 ` [Nouveau] [RFC v4 01/11] drm/nouveau/kms/nv40-/backlight: Assign prop type once Lyude Paul
2021-02-08 23:38 ` Lyude Paul [this message]
2021-02-08 23:38 ` [Nouveau] [RFC v4 03/11] drm/i915/dpcd_bl: Remove redundant AUX backlight frequency calculations Lyude Paul
2021-02-08 23:38 ` [Nouveau] [RFC v4 04/11] drm/i915/dpcd_bl: Handle drm_dpcd_read/write() return values correctly Lyude Paul
2021-02-08 23:38 ` [Nouveau] [RFC v4 05/11] drm/i915/dpcd_bl: Cleanup intel_dp_aux_vesa_enable_backlight() a bit Lyude Paul
2021-02-11 3:56 ` Rodrigo Vivi
2021-02-12 11:28 ` Jani Nikula
2021-02-08 23:38 ` [Nouveau] [RFC v4 06/11] drm/i915/dpcd_bl: Cache some backlight capabilities in intel_panel.backlight Lyude Paul
2021-02-08 23:38 ` [Nouveau] [RFC v4 07/11] drm/i915/dpcd_bl: Move VESA backlight enabling code closer together Lyude Paul
2021-02-08 23:38 ` [Nouveau] [RFC v4 08/11] drm/i915/dpcd_bl: Return early in vesa_calc_max_backlight if we can't read PWMGEN_BIT_COUNT Lyude Paul
2021-02-11 3:52 ` [Nouveau] [Intel-gfx] " Rodrigo Vivi
2021-02-08 23:38 ` [Nouveau] [RFC v4 09/11] drm/i915/dpcd_bl: Print return codes for VESA backlight failures Lyude Paul
2021-02-11 3:47 ` [Nouveau] [Intel-gfx] " Rodrigo Vivi
2021-02-08 23:39 ` [Nouveau] [RFC v4 10/11] drm/dp: Extract i915's eDP backlight code into DRM helpers Lyude Paul
2021-02-11 4:15 ` [Nouveau] [Intel-gfx] " Rodrigo Vivi
2021-02-11 18:35 ` Lyude Paul
2021-02-12 22:15 ` Lyude Paul
2021-02-18 8:35 ` Jani Nikula
2021-02-18 15:31 ` Ville Syrjälä
2021-02-19 21:14 ` Lyude Paul
2021-02-08 23:39 ` [Nouveau] [RFC v4 11/11] drm/nouveau/kms/nv50-: Add basic DPCD backlight support for nouveau Lyude Paul
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=20210208233902.1289693-3-lyude@redhat.com \
--to=lyude@redhat.com \
--cc=airlied@linux.ie \
--cc=bskeggs@redhat.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=greg.depoire@gmail.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nouveau@lists.freedesktop.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;
as well as URLs for NNTP newsgroup(s).