Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
	Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH 2/2] drm/i915: ignore bios output config if not all outputs are on
Date: Tue, 4 Mar 2014 22:08:12 +0100	[thread overview]
Message-ID: <20140304210812.GO17001@phenom.ffwll.local> (raw)
In-Reply-To: <20140304123301.0876a258@jbarnes-desktop>

On Tue, Mar 04, 2014 at 12:33:01PM -0800, Jesse Barnes wrote:
> On Tue,  4 Mar 2014 21:08:42 +0100
> Daniel Vetter <daniel.vetter@ffwll.ch> wrote:
> 
> > Both Ville and QA rather immediately complained that with the new
> > initial_config logic from Jesse not all outputs get enabled. Since the
> > fbdev emulation pretty much tries to always enable as many outputs as
> > possible (it even has hotplug handling and all that) fall back if more
> > outputs could have been enabled.
> > 
> > v2: Fix up my confusion about what enabled means - it's passed from
> > the fbdev helper, we need to check for a non-zero connector->encoder
> > link. Spotted by Ville.
> > 
> > Cc: Jesse Barnes <jbarnes@virtuousgeek.org>
> > Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=75552
> > Tested-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
> > ---
> >  drivers/gpu/drm/i915/intel_fbdev.c | 17 +++++++++++++++++
> >  1 file changed, 17 insertions(+)
> > 
> > diff --git a/drivers/gpu/drm/i915/intel_fbdev.c b/drivers/gpu/drm/i915/intel_fbdev.c
> > index df00e6b01f0d..c1a20c3babde 100644
> > --- a/drivers/gpu/drm/i915/intel_fbdev.c
> > +++ b/drivers/gpu/drm/i915/intel_fbdev.c
> > @@ -290,6 +290,8 @@ static bool intel_fb_initial_config(struct drm_fb_helper *fb_helper,
> >  	int i, j;
> >  	bool *save_enabled;
> >  	bool fallback = true;
> > +	int num_connectors_enabled = 0;
> > +	int num_connectors_detected = 0;
> >  
> >  	/*
> >  	 * If the user specified any force options, just bail here
> > @@ -324,6 +326,10 @@ static bool intel_fb_initial_config(struct drm_fb_helper *fb_helper,
> >  
> >  		fb_conn = fb_helper->connector_info[i];
> >  		connector = fb_conn->connector;
> > +
> > +		if (connector->status == connector_status_connected)
> > +			num_connectors_detected++;
> > +
> >  		if (!enabled[i]) {
> >  			DRM_DEBUG_KMS("connector %d not enabled, skipping\n",
> >  				      connector->base.id);
> > @@ -338,6 +344,8 @@ static bool intel_fb_initial_config(struct drm_fb_helper *fb_helper,
> >  			continue;
> >  		}
> >  
> > +		num_connectors_enabled++;
> > +
> >  		new_crtc = intel_fb_helper_crtc(fb_helper, encoder->crtc);
> >  
> >  		/*
> > @@ -393,6 +401,15 @@ static bool intel_fb_initial_config(struct drm_fb_helper *fb_helper,
> >  		fallback = false;
> >  	}
> >  
> > +	/*
> > +	 * If the BIOS didn't enable everything it could, fall back to have the
> > +	 * same user experiencing of lighting up as much as possible like the
> > +	 * fbdev helper library.
> > +	 */
> > +	if (num_connectors_enabled != num_connectors_detected &&
> > +	    num_connectors_enabled < INTEL_INFO(dev)->num_pipes)
> > +		fallback = true;
> 
> I think we need a debug message in here so people can figure out why
> their fastboot failed with this patch included.  E.g. "some connected
> outputs weren't enabled, falling back to old behavior".
> 
> Also note that this will probably always happen in certain configs, and
> the fallback behavior won't be any better since we may not be able to
> light up everything that's attached.

Excellent suggestion, I've gone ahead and added debug output for all cases
where we fall back.
> 
> With those caveats:
> Reviewed-by: Jesse Barnes <jbarnes@virtuousgeek.org>

Thanks for the review, both patches merged to dinq.
-Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch

  reply	other threads:[~2014-03-04 21:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-04 20:08 [PATCH 1/2] drm/i915: s/any_enabled/!fallback/ in fbdev_initial_config Daniel Vetter
2014-03-04 20:08 ` [PATCH 2/2] drm/i915: ignore bios output config if not all outputs are on Daniel Vetter
2014-03-04 20:33   ` Jesse Barnes
2014-03-04 21:08     ` Daniel Vetter [this message]
2014-03-05 16:27       ` Jesse Barnes
2014-03-05 18:34         ` Daniel Vetter
2014-03-05 19:19           ` Jesse Barnes
2014-03-04 20:30 ` [PATCH 1/2] drm/i915: s/any_enabled/!fallback/ in fbdev_initial_config Jesse Barnes

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=20140304210812.GO17001@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=daniel.vetter@ffwll.ch \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jbarnes@virtuousgeek.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