linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: "Bruno Prémont" <bonbons@linux-vserver.org>,
	"Carbonated Beverage" <ramune@psychosnugglebunnies.net>,
	"Intel Graphics Development" <intel-gfx@lists.freedesktop.org>,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: [Intel-gfx] 3.14.3 i915 dead display under X11
Date: Wed, 14 May 2014 12:33:39 -0700	[thread overview]
Message-ID: <20140514193339.GA18197@kroah.com> (raw)
In-Reply-To: <CAKMK7uFDJym3fKewmivps_894_P_ifQ0TYeBXg5oevP6wrz1zw@mail.gmail.com>

On Wed, May 14, 2014 at 09:19:32PM +0200, Daniel Vetter wrote:
> On Wed, May 14, 2014 at 08:47:38PM +0200, Bruno Prémont wrote:
> > CCing intel-gfx as otherwise it will probably not get seen by developers.
> >
> > On Sun, 11 May 2014 Carbonated Beverage <ramune@psychosnugglebunnies.net> wrote:
> > > Bisecting from 3.13.6 (good) to 3.14.3 (bad) ended up with...
> > >
> > > commit b35684b8fa94e04f55fd38bf672b737741d2f9e2
> > > Author: Jani Nikula <jani.nikula@intel.com>
> > > Date:   Thu Nov 14 12:13:41 2013 +0200
> > >
> > >     drm/i915: do full backlight setup at enable time
> > >
> > >     We should now have all the information we need to do a full
> > >     initialization of the backlight registers.
> > >
> > >     v2: Keep QUIRK_NO_PCH_PWM_ENABLE for now (Imre).
> > >
> > >     Signed-off-by: Jani Nikula <jani.nikula@intel.com>
> > >     Reviewed-by: Imre Deak <imre.deak@intel.com>
> > >     Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
> > >
> > > Which is in 3.12.0????
> > >
> > > I'm not sure how that came to be.  Does that look right?  What other
> > > information would be required to track this down?
> 
> We've killed this again in 3.14 since we've hoped the backlight rework in
> there fixed it. For 3.15 we finally have the right fix - vbt has a bit
> telling us not to look at the integrated PWM for the panel.
> 
> For 3.14 we will (again) resurrect the quirk because the vbt thing is a
> bit too risky an imo needs a full -rc cycle for testing. But that revert
> is currently stalled because Greg KH is travelling too much ;-)
> 
> Cc'ing him to make sure that patch doesn't miss the next 3.14.x release.

What specific patch are you wanting to make sure makes it in?  I've been
avoiding all of the drm patches so far for 3.14.y as it's an easy thing
to do, but I'll eventually have to start paying attention to them :)

thanks,

greg k-h

  reply	other threads:[~2014-05-14 19:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-12  3:10 3.14.3 i915 dead display under X11 Carbonated Beverage
2014-05-14 18:47 ` Bruno Prémont
2014-05-14 19:19   ` [Intel-gfx] " Daniel Vetter
2014-05-14 19:33     ` Greg KH [this message]
2014-05-14 19:43       ` Josh Boyer
2014-05-14 20:06         ` Greg KH
2014-05-14 20:19         ` 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=20140514193339.GA18197@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=bonbons@linux-vserver.org \
    --cc=daniel@ffwll.ch \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ramune@psychosnugglebunnies.net \
    /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;
as well as URLs for NNTP newsgroup(s).