public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: Dhinakaran Pandiyan <dhinakaran.pandiyan@intel.com>
Subject: Re: [PATCH 5/5] drm/i915/dp: Remove useless debug about	TPS3 support
Date: Tue, 19 Sep 2017 13:13:55 +0300	[thread overview]
Message-ID: <87wp4v807w.fsf@nikula.org> (raw)
In-Reply-To: <20170918222141.4674-5-dhinakaran.pandiyan@intel.com>

On Mon, 18 Sep 2017, Dhinakaran Pandiyan <dhinakaran.pandiyan@intel.com> wrote:
> We already print training pattern used during link training and also
> print if the source or sink does not support TPS3 for HBR2 link rates,
> see intel_dp_training_pattern().

Yeah, this was useful a long time ago.

Reviewed-by: Jani Nikula <jani.nikula@intel.com>



>
> Signed-off-by: Dhinakaran Pandiyan <dhinakaran.pandiyan@intel.com>
> ---
>  drivers/gpu/drm/i915/intel_dp.c | 4 ----
>  1 file changed, 4 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/intel_dp.c b/drivers/gpu/drm/i915/intel_dp.c
> index cc129aa444ac..2d41cd684557 100644
> --- a/drivers/gpu/drm/i915/intel_dp.c
> +++ b/drivers/gpu/drm/i915/intel_dp.c
> @@ -4718,10 +4718,6 @@ intel_dp_long_pulse(struct intel_connector *intel_connector)
>  	if (intel_encoder->type != INTEL_OUTPUT_EDP)
>  		intel_encoder->type = INTEL_OUTPUT_DP;
>  
> -	DRM_DEBUG_KMS("Display Port TPS3 support: source %s, sink %s\n",
> -		      yesno(intel_dp_source_supports_hbr2(intel_dp)),
> -		      yesno(drm_dp_tps3_supported(intel_dp->dpcd)));
> -
>  	if (intel_dp->reset_link_params) {
>  		/* Initial max link lane count */
>  		intel_dp->max_link_lane_count = intel_dp_max_common_lane_count(intel_dp);

-- 
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2017-09-19 10:14 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-18 22:21 [PATCH 1/5] drm/i915/mst: Debug log connector name in destroy_connector() Dhinakaran Pandiyan
2017-09-18 22:21 ` [PATCH 2/5] drm/i915/mst: Print active mst links after update Dhinakaran Pandiyan
2017-09-18 22:21 ` [PATCH 3/5] drm/i915/dp: Fix buffer size for sink_irq_esi read Dhinakaran Pandiyan
2017-09-18 22:21 ` [PATCH 4/5] drm/i915/dp: Clean up intel_dp_check_mst_status Dhinakaran Pandiyan
2017-09-20 19:11   ` Ausmus, James
2017-09-20 19:55     ` Pandiyan, Dhinakaran
2017-09-20 20:02       ` Ausmus, James
2017-09-20 22:47         ` Pandiyan, Dhinakaran
2017-09-20 22:53           ` Ausmus, James
2017-09-21 18:54             ` [PATCH v2] " Dhinakaran Pandiyan
2017-09-22 17:53               ` Ausmus, James
2017-09-25 12:39               ` Jani Nikula
2017-09-18 22:21 ` [PATCH 5/5] drm/i915/dp: Remove useless debug about TPS3 support Dhinakaran Pandiyan
2017-09-19 10:13   ` Jani Nikula [this message]
2017-09-19 12:17 ` ✓ Fi.CI.BAT: success for series starting with [1/5] drm/i915/mst: Debug log connector name in destroy_connector() Patchwork
2017-09-19 16:18 ` ✗ Fi.CI.IGT: warning " Patchwork
2017-09-21 19:18 ` ✗ Fi.CI.BAT: failure for series starting with [1/5] drm/i915/mst: Debug log connector name in destroy_connector() (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=87wp4v807w.fsf@nikula.org \
    --to=jani.nikula@linux.intel.com \
    --cc=dhinakaran.pandiyan@intel.com \
    --cc=intel-gfx@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