Re: Baytrail problems (was Re: Linux 3.13-rc8)

["Rafael J. Wysocki" <rjw@rjwysocki.net>]

On Thursday, January 16, 2014 10:29:45 AM Linus Walleij wrote:
> On Thu, Jan 16, 2014 at 2:49 AM, Linus Torvalds
> <torvalds@linux-foundation.org> wrote:
> > Adding in the appropriate people...
> >
> > On Tue, Jan 14, 2014 at 7:01 PM, One Thousand Gnomes
> > <gnomes@lxorguk.ukuu.org.uk> wrote:
> >>
> >> It seems to hate Baytrail/T
> >>
> >> My ASUS T100TA has gone from 3.11 'needs video=VGA-1:blah' to get the mode
> >> right but otherwise running nicely and playing 3D games to 3.13-rc8
> >>
> >> - crashes and burns during boot if the Baytrail pinctrl driver is compiled
> >>   in
> >
> > Andy, Paul? The changes to the pinctrl driver since 3.11 look trivial,
> > but I guess the GPIO and ACPI ID addition ends up also enabling all
> > the old code that Alan probably never ran in 3.11 because the driver
> > didn't trigger on his machine.
> 
> So that is commit f6308b36c411dc5
> "ACPI: Add BayTrail SoC GPIO and LPSS ACPI IDs"?
> 
> This seems to have been selected for -stable as well so the
> problem will be spreading as distros start pushing stable kernel
> updates :-(
> 
> That came in through the ACPI tree, Rafael do you want to
> revert it if there is no better quickfix?

Yes, I'll push either a revert or a fix before the weekend.

> This adds an interesting twist to the general statement that
> new PCI/ACPI IDs should go into stable BTW, maybe they
> should not always do that.

Well, this is the first time we've had such a problem with ACPI IDs, but
since we do have this problem, I'm not going to tag any commits like that for
stable any more (and I'm not going to fast-track them any more for that
matter).

Thanks!

-- 
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.