public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Shuah Khan <shuahkh@osg.samsung.com>,
	daniel.vetter@intel.com, seanpaul@chromium.org, airlied@linux.ie
Cc: Shuah Khan <shuahkh@osg.samsung.com>,
	dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm: change connector disconnected debug message to an error
Date: Thu, 02 Feb 2017 10:32:59 +0200	[thread overview]
Message-ID: <874m0d0z7o.fsf@intel.com> (raw)
In-Reply-To: <20170202025904.25810-1-shuahkh@osg.samsung.com>

On Thu, 02 Feb 2017, Shuah Khan <shuahkh@osg.samsung.com> wrote:
> Change drm_helper_probe_single_connector_modes() to print an error to
> report connector disconnected status instead of a debug message.
>
> When this condition occurs, application doesn't know the real error and
> reports it as driver lacking support for mode setting. Change it to an
> error to make it easier to debug.

Please explain what makes this condition an error. Connectors get
connected and disconnected, business as usual, why should this be an
error?

BR,
Jani.


>
> Signed-off-by: Shuah Khan <shuahkh@osg.samsung.com>
> ---
>  drivers/gpu/drm/drm_probe_helper.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/drm_probe_helper.c b/drivers/gpu/drm/drm_probe_helper.c
> index ac953f0..6472b7f 100644
> --- a/drivers/gpu/drm/drm_probe_helper.c
> +++ b/drivers/gpu/drm/drm_probe_helper.c
> @@ -282,8 +282,8 @@ int drm_helper_probe_single_connector_modes(struct drm_connector *connector,
>  	dev->mode_config.poll_running = drm_kms_helper_poll;
>  
>  	if (connector->status == connector_status_disconnected) {
> -		DRM_DEBUG_KMS("[CONNECTOR:%d:%s] disconnected\n",
> -			connector->base.id, connector->name);
> +		DRM_ERROR("[CONNECTOR:%d:%s] disconnected\n",
> +			  connector->base.id, connector->name);
>  		drm_mode_connector_update_edid_property(connector, NULL);
>  		verbose_prune = false;
>  		goto prune;

-- 
Jani Nikula, Intel Open Source Technology Center

  reply	other threads:[~2017-02-02  8:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-02  2:59 [PATCH] drm: change connector disconnected debug message to an error Shuah Khan
2017-02-02  8:32 ` Jani Nikula [this message]
2017-02-02 17:25   ` Shuah Khan
2017-02-03  7:59     ` Jani Nikula
2017-02-03  8:06     ` Daniel Vetter
2017-02-10 16:29       ` Shuah Khan
2017-02-14 20:05         ` Daniel Vetter

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=874m0d0z7o.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=airlied@linux.ie \
    --cc=daniel.vetter@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=seanpaul@chromium.org \
    --cc=shuahkh@osg.samsung.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox