From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Christian Steiner <christian.steiner@outlook.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: pinctrl_cherryview: massive error messages (handle_bad_irq)
Date: Mon, 24 Oct 2016 11:14:17 +0300 [thread overview]
Message-ID: <20161024081417.GB24289@lahna.fi.intel.com> (raw)
In-Reply-To: <CACRpkdYJXYX4QPVpnL-ztLY2VS11rX1AuYf8fXHMfke8zOFrMg@mail.gmail.com>
On Mon, Oct 24, 2016 at 01:34:05AM +0200, Linus Walleij wrote:
> On Thu, Oct 20, 2016 at 5:36 PM, Christian Steiner
> <christian.steiner@outlook.de> wrote:
>
> >>> Currently I am using BIOS v1.22. Recently Acer released v1.23. I could
> >>> test if the BIOS update solves the problem.
> >>
> >> Please try that first.
> >
> > Updating the BIOS to v1.23 solved the problem. Thank you very much for
> > your advice!
>
> Not that I know how the Intel ecosystem works wrt this.
>
> Do you detect elder BIOS and display a warning? Are regular
> users updating their BIOSes? Or was this some kind of development
> Intel in-house BIOS?
People do upgrade their BIOSes but for Linux users it has some extra
pain if the OEM only provides you a .exe file which you need to run
under Windows.
It is possible to detect the BIOS version using DMI strings and issue a
warning in the driver, if that's what you mean, but currently we don't
do that.
next prev parent reply other threads:[~2016-10-24 8:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-19 18:32 Christian Steiner
2016-10-19 19:22 ` Mika Westerberg
2016-10-19 20:40 ` Christian Steiner
2016-10-20 10:08 ` Mika Westerberg
2016-10-20 12:22 ` Linus Walleij
2016-10-20 15:36 ` Christian Steiner
2016-10-20 17:59 ` Mika Westerberg
2016-10-23 23:34 ` Linus Walleij
2016-10-24 8:14 ` Mika Westerberg [this message]
2016-10-25 9:26 ` Linus Walleij
2016-10-25 10:35 ` Mika Westerberg
-- strict thread matches above, loose matches on Subject: below --
2016-10-19 18:32 Christian Steiner
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=20161024081417.GB24289@lahna.fi.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=christian.steiner@outlook.de \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@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
Powered by JetHome