From: Jeevan B <jeevan.b@intel.com>
To: uma.shankar@intel.com
Cc: Jeevan B <jeevan.b@intel.com>, intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] [PATCH 2/5] drm/i915: utilize subconnector property for DP
Date: Wed, 1 Apr 2020 17:42:25 +0530 [thread overview]
Message-ID: <1585743148-31205-2-git-send-email-jeevan.b@intel.com> (raw)
In-Reply-To: <1585743148-31205-1-git-send-email-jeevan.b@intel.com>
Since DP-specific information is stored in driver's structures, every
driver needs to implement subconnector property by itself.
v2: updates to match previous commit changes
Reviewed-by: Emil Velikov <emil.velikov@collabora.com>
Tested-by: Oleg Vasilev <oleg.vasilev@intel.com>
Signed-off-by: Oleg Vasilev <oleg.vasilev@intel.com>
Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Signed-off-by: Jeevan B <jeevan.b@intel.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20190829114854.1539-4-oleg.vasilev@intel.com
---
drivers/gpu/drm/i915/display/intel_dp.c | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/drivers/gpu/drm/i915/display/intel_dp.c b/drivers/gpu/drm/i915/display/intel_dp.c
index 2e715e6..c2c9ed3 100644
--- a/drivers/gpu/drm/i915/display/intel_dp.c
+++ b/drivers/gpu/drm/i915/display/intel_dp.c
@@ -6140,6 +6140,11 @@ intel_dp_detect(struct drm_connector *connector,
*/
intel_display_power_flush_work(dev_priv);
+ if (!intel_dp_is_edp(intel_dp))
+ drm_dp_set_subconnector_property(connector,
+ status,
+ intel_dp->dpcd,
+ intel_dp->downstream_ports);
return status;
}
@@ -7192,6 +7197,9 @@ intel_dp_add_properties(struct intel_dp *intel_dp, struct drm_connector *connect
struct drm_i915_private *dev_priv = to_i915(connector->dev);
enum port port = dp_to_dig_port(intel_dp)->base.port;
+ if (!intel_dp_is_edp(intel_dp))
+ drm_mode_add_dp_subconnector_property(connector);
+
if (!IS_G4X(dev_priv) && port != PORT_A)
intel_attach_force_audio_property(connector);
--
2.7.4
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2020-04-01 12:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-01 12:12 [Intel-gfx] [PATCH 1/5] drm: report dp downstream port type as a subconnector property Jeevan B
2020-04-01 12:12 ` Jeevan B [this message]
[not found] ` <1585743148-31205-1-git-send-email-jeevan.b-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2020-04-01 12:12 ` [PATCH 3/5] drm/nouveau: utilize subconnector property for DP Jeevan B
2020-04-01 12:12 ` [PATCH 5/5] drm/amdgpu: utilize subconnector property for DP through DisplayManager Jeevan B
2020-04-01 15:21 ` Alex Deucher
2020-04-01 12:26 ` [Intel-gfx] [PATCH 1/5] drm: report dp downstream port type as a subconnector property Shankar, Uma
2020-04-01 12:38 ` Shankar, Uma
2020-04-01 13:03 ` Ville Syrjälä
2020-04-03 7:01 ` Jeevan B
-- strict thread matches above, loose matches on Subject: below --
2020-04-07 6:50 Jeevan B
2020-04-07 6:50 ` [Intel-gfx] [PATCH 2/5] drm/i915: utilize subconnector property for DP Jeevan B
2020-04-15 10:01 ` Jani Nikula
2020-04-21 9:37 ` Jeevan B
2020-04-24 12:50 [PATCH 1/5] drm: report dp downstream port type as a subconnector property Jeevan B
2020-04-24 12:50 ` [Intel-gfx] [PATCH 2/5] drm/i915: utilize subconnector property for DP Jeevan B
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=1585743148-31205-2-git-send-email-jeevan.b@intel.com \
--to=jeevan.b@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=uma.shankar@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.