From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Simon Ser <simon.ser@intel.com>
Cc: intel-gfx@lists.freedesktop.org,
Manasi Navare <nanasi.d.navare@intel.com>
Subject: Re: [PATCH v2] drm/i915: add port info to debugfs
Date: Wed, 28 Aug 2019 19:40:13 +0300 [thread overview]
Message-ID: <20190828164013.GI7482@intel.com> (raw)
In-Reply-To: <20190823094946.5708-1-simon.ser@intel.com>
On Fri, Aug 23, 2019 at 12:49:46PM +0300, Simon Ser wrote:
> This patch adds a line with the port name to connectors in
> debugfs/i915_debug_info. If the port is Type-C, the Type-C port number is
> printed too.
>
> Signed-off-by: Simon Ser <simon.ser@intel.com>
> Cc: Imre Deak <imre.deak@intel.com>
> Cc: Manasi Navare <nanasi.d.navare@intel.com>
> Reviewed-by: Imre Deak <imre.deak@intel.com>
> ---
>
> Resending v2 to the correct mailing list.
>
> drivers/gpu/drm/i915/i915_debugfs.c | 10 ++++++++++
> 1 file changed, 10 insertions(+)
>
> diff --git a/drivers/gpu/drm/i915/i915_debugfs.c b/drivers/gpu/drm/i915/i915_debugfs.c
> index b39226d7f8d2..4ba508c954f8 100644
> --- a/drivers/gpu/drm/i915/i915_debugfs.c
> +++ b/drivers/gpu/drm/i915/i915_debugfs.c
> @@ -2557,9 +2557,11 @@ static void intel_lvds_info(struct seq_file *m,
> static void intel_connector_info(struct seq_file *m,
> struct drm_connector *connector)
> {
> + struct drm_i915_private *i915 = to_i915(connector->dev);
> struct intel_connector *intel_connector = to_intel_connector(connector);
> struct intel_encoder *intel_encoder = intel_connector->encoder;
> struct drm_display_mode *mode;
> + enum tc_port tc_port;
>
> seq_printf(m, "connector %d: type %s, status: %s\n",
> connector->base.id, connector->name,
> @@ -2578,6 +2580,14 @@ static void intel_connector_info(struct seq_file *m,
> if (!intel_encoder)
> return;
>
> + if (intel_encoder->port != PORT_NONE) {
> + seq_printf(m, "\tport: %c", port_name(intel_encoder->port));
> + tc_port = intel_port_to_tc(i915, intel_encoder->port);
> + if (tc_port != PORT_TC_NONE)
> + seq_printf(m, "/TC#%d", tc_port + 1);
> + seq_printf(m, "\n");
Maybe just print encoder->name instead?
> + }
> +
> switch (connector->connector_type) {
> case DRM_MODE_CONNECTOR_DisplayPort:
> case DRM_MODE_CONNECTOR_eDP:
> --
> 2.22.1
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
--
Ville Syrjälä
Intel
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-08-28 16:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-23 9:49 [PATCH v2] drm/i915: add port info to debugfs Simon Ser
2019-08-23 14:36 ` ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2019-08-23 15:02 ` ✗ Fi.CI.BAT: failure " Patchwork
2019-08-26 11:08 ` [PATCH v2] " Imre Deak
2019-08-26 16:38 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915: add port info to debugfs (rev2) Patchwork
2019-08-26 17:51 ` ✓ Fi.CI.BAT: success " Patchwork
2019-08-28 16:40 ` Ville Syrjälä [this message]
2019-08-29 9:08 ` [PATCH v2] drm/i915: add port info to debugfs Ser, Simon
2019-08-29 10:29 ` Ville Syrjälä
2019-08-28 23:57 ` ✓ Fi.CI.IGT: success for drm/i915: add port info to debugfs (rev2) 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=20190828164013.GI7482@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=nanasi.d.navare@intel.com \
--cc=simon.ser@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.