From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Greg KH <greg@kroah.com>
Cc: stable@vger.kernel.org, Hans de Goede <hdegoede@redhat.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Linus Walleij <linus.walleij@linaro.org>,
Benjamin Tissoires <btissoir@redhat.com>
Subject: Re: Revert f5a26acf0162 ("pinctrl: intel: Initialize GPIO properly when used through irqchip") from stable trees
Date: Thu, 26 Apr 2018 16:36:23 +0300 [thread overview]
Message-ID: <20180426133623.GI2173@lahna.fi.intel.com> (raw)
In-Reply-To: <20180426132427.GA20051@kroah.com>
On Thu, Apr 26, 2018 at 03:24:27PM +0200, Greg KH wrote:
> On Thu, Apr 26, 2018 at 03:53:02PM +0300, Mika Westerberg wrote:
> > Hi,
> >
> > It seems that commit f5a26acf0162 ("pinctrl: intel: Initialize GPIO
> > properly when used through irqchip") can cause problems on some Skylake
> > systems with Sunrisepoint PCH-H. Namely on certain systems it may turn
> > the backlight PWM pin from native mode to GPIO which makes the screen
> > blank during boot.
> >
> > There is more information here:
> >
> > https://bugzilla.redhat.com/show_bug.cgi?id=1543769
> >
> > The actual reason is that GPIO numbering used in BIOS is using "Windows"
> > numbers meaning that they don't match the hardware 1:1 and because of
> > this a wrong pin (backlight PWM) is picked and switched to GPIO mode.
> >
> > There is a proper fix for this but since it has quite many dependencies
> > on commits that cannot be considered stable material, I suggest we
> > revert commit f5a26acf0162 from stable trees 4.9, 4.14 and 4.15 to
> > prevent the backlight issue.
>
> What is the "proper fix"? Is it in Linus's tree yet?
This patch
https://patchwork.ozlabs.org/patch/892813/
However, it is not yet in Linus' tree.
next prev parent reply other threads:[~2018-04-26 13:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-26 12:53 Revert f5a26acf0162 ("pinctrl: intel: Initialize GPIO properly when used through irqchip") from stable trees Mika Westerberg
2018-04-26 13:24 ` Greg KH
2018-04-26 13:36 ` Mika Westerberg [this message]
2018-04-26 15:32 ` Greg KH
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=20180426133623.GI2173@lahna.fi.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=btissoir@redhat.com \
--cc=greg@kroah.com \
--cc=hdegoede@redhat.com \
--cc=linus.walleij@linaro.org \
--cc=stable@vger.kernel.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