public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Chris Wilson <chris@chris-wilson.co.uk>,
	Daniel Vetter <daniel@ffwll.ch>,
	intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Use the connector name in fbdev debug messages
Date: Wed, 14 May 2014 12:07:09 +0200	[thread overview]
Message-ID: <20140514100709.GD8790@phenom.ffwll.local> (raw)
In-Reply-To: <20140513141145.GL7239@nuc-i3427.alporthouse.com>

On Tue, May 13, 2014 at 03:11:45PM +0100, Chris Wilson wrote:
> On Tue, May 13, 2014 at 04:02:40PM +0200, Daniel Vetter wrote:
> > On Tue, May 13, 2014 at 02:26:39PM +0100, Chris Wilson wrote:
> > > During initial probing of the modes to assign to the fbdev console, we
> > > use the CRTC and connector ids. These are much harder for us to
> > > understand than if we used their actual names (or pipe in the CRTC
> > > case). Similarly, we want to manually print the mode size rather than
> > > rely on mode->name being set.
> > > 
> > > v2: Use '%c' for pipe_name()
> > > 
> > > Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> > > Reviewed-by: Damien Lespiau <damien.lespiau@intel.com>
> > > ---
> > >  drivers/gpu/drm/i915/intel_fbdev.c | 28 ++++++++++++++++------------
> > >  1 file changed, 16 insertions(+), 12 deletions(-)
> > > 
> > > diff --git a/drivers/gpu/drm/i915/intel_fbdev.c b/drivers/gpu/drm/i915/intel_fbdev.c
> > > index fbe7941f88c8..1d3f0a9cce31 100644
> > > --- a/drivers/gpu/drm/i915/intel_fbdev.c
> > > +++ b/drivers/gpu/drm/i915/intel_fbdev.c
> > > @@ -344,14 +344,14 @@ static bool intel_fb_initial_config(struct drm_fb_helper *fb_helper,
> > >  			num_connectors_detected++;
> > >  
> > >  		if (!enabled[i]) {
> > > -			DRM_DEBUG_KMS("connector %d not enabled, skipping\n",
> > > -				      connector->base.id);
> > > +			DRM_DEBUG_KMS("connector %s not enabled, skipping\n",
> > > +				      drm_get_connector_name(connector));
> > >  			continue;
> > >  		}
> > >  
> > >  		if (connector->force == DRM_FORCE_OFF) {
> > 
> > I seem to be lacking the patch to obey the connector->force stuff you have
> > here. Instead I have an early bail-out at the top of fb_initial_config.
> > 
> > Do I miss some crucial patch or can you please rebase on top of dinq?
> 
> It's not crucial, just a patch you missed to fix up some of Jesse's
> shortcomings.

Hm, looked at that patch again and I guess that needs to be rebased to
take out the logic from Jesse's patch. So merged this one for now and
resolved the conflict.
-Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch

      reply	other threads:[~2014-05-14 10:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-13 12:45 [PATCH] drm/i915: Use the connector name in fbdev debug messages Chris Wilson
2014-05-13 12:51 ` Damien Lespiau
2014-05-13 12:59   ` Chris Wilson
2014-05-13 13:02     ` Damien Lespiau
2014-05-13 13:26       ` Chris Wilson
2014-05-13 14:02         ` Daniel Vetter
2014-05-13 14:11           ` Chris Wilson
2014-05-14 10:07             ` Daniel Vetter [this message]

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=20140514100709.GD8790@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=chris@chris-wilson.co.uk \
    --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