Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751431AbdGRHif (ORCPT ); Tue, 18 Jul 2017 03:38:35 -0400 Received: from mga02.intel.com ([134.134.136.20]:40999 "EHLO mga02.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751189AbdGRHie (ORCPT ); Tue, 18 Jul 2017 03:38:34 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.40,377,1496127600"; d="scan'208";a="879983987" From: Jani Nikula To: Paul Kocialkowski , intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org Cc: Manasi Navare , Daniel Vetter , David Airlie , Paul Kocialkowski Subject: Re: [PATCH] drm/i915: Explicit the connector name for DP link training result In-Reply-To: <20170717142726.18761-1-paul.kocialkowski@linux.intel.com> Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo References: <20170717142726.18761-1-paul.kocialkowski@linux.intel.com> Date: Tue, 18 Jul 2017 10:38:00 +0300 Message-ID: <8760eqb3fr.fsf@intel.com> MIME-Version: 1.0 Content-Type: text/plain Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1946 Lines: 46 On Mon, 17 Jul 2017, Paul Kocialkowski wrote: > This adds the connector name when printing a debug message about the DP > link training result. It is useful to figure out what connector is > failing when multiple DP connectors are used. Perhaps more consistent would be using a prefix like this: DRM_DEBUG_KMS("[CONNECTOR:%d:%s] bla bla blaa\n", connector->base.base.id, connector->base.name); BR, Jani. > > Signed-off-by: Paul Kocialkowski > --- > drivers/gpu/drm/i915/intel_dp_link_training.c | 10 ++++++---- > 1 file changed, 6 insertions(+), 4 deletions(-) > > diff --git a/drivers/gpu/drm/i915/intel_dp_link_training.c b/drivers/gpu/drm/i915/intel_dp_link_training.c > index b79c1c0e404c..75a411c94ce5 100644 > --- a/drivers/gpu/drm/i915/intel_dp_link_training.c > +++ b/drivers/gpu/drm/i915/intel_dp_link_training.c > @@ -321,13 +321,15 @@ intel_dp_start_link_train(struct intel_dp *intel_dp) > if (!intel_dp_link_training_channel_equalization(intel_dp)) > goto failure_handling; > > - DRM_DEBUG_KMS("Link Training Passed at Link Rate = %d, Lane count = %d", > - intel_dp->link_rate, intel_dp->lane_count); > + DRM_DEBUG_KMS("Link Training Passed at Link Rate = %d, Lane count = %d for connector %s", > + intel_dp->link_rate, intel_dp->lane_count, > + intel_connector->base.name); > return; > > failure_handling: > - DRM_DEBUG_KMS("Link Training failed at link rate = %d, lane count = %d", > - intel_dp->link_rate, intel_dp->lane_count); > + DRM_DEBUG_KMS("Link Training failed at link rate = %d, lane count = %d for connector %s", > + intel_dp->link_rate, intel_dp->lane_count, > + intel_connector->base.name); > if (!intel_dp_get_link_train_fallback_values(intel_dp, > intel_dp->link_rate, > intel_dp->lane_count)) -- Jani Nikula, Intel Open Source Technology Center