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: Tue, 25 Oct 2016 13:35:53 +0300 [thread overview]
Message-ID: <20161025103553.GH1476@lahna.fi.intel.com> (raw)
In-Reply-To: <CACRpkdY7mV6MXD0Pvv2R0jMDd=3Pj=eFaNDcSSD+z+qyyVAedQ@mail.gmail.com>
On Tue, Oct 25, 2016 at 11:26:48AM +0200, Linus Walleij wrote:
> On Mon, Oct 24, 2016 at 10:14 AM, Mika Westerberg
> <mika.westerberg@linux.intel.com> wrote:
>
> > 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.
>
> I was more thinking about detecting the old BIOS and if that
> is present, mask off the interrupts on the resume path or something,
> as it is probably a bigger problem to see the warnings than to
> loose these settings.
>
> Possibly also add a warning at probe() like you describe.
I think we can do masking of these IRQs (0..community->nirqs-1)
unconditionally in probe() because those should belong to the GPIO
driver as far as I understand. But I need to double check that from the
spec.
next prev parent reply other threads:[~2016-10-25 10:35 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
2016-10-25 9:26 ` Linus Walleij
2016-10-25 10:35 ` Mika Westerberg [this message]
-- 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=20161025103553.GH1476@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