From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Hans de Goede <hdegoede@redhat.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Heikki Krogerus <heikki.krogerus@linux.intel.com>,
Linus Walleij <linus.walleij@linaro.org>
Cc: linux-gpio@vger.kernel.org
Subject: Re: [PATCH] pinctrl: baytrail: Do not call WARN_ON for a firmware bug
Date: Wed, 12 Jul 2017 18:25:35 +0300 [thread overview]
Message-ID: <1499873135.22624.366.camel@linux.intel.com> (raw)
In-Reply-To: <87931ddb-5a5a-dc20-7e79-e1a507532e2b@redhat.com>
On Wed, 2017-07-12 at 16:18 +0200, Hans de Goede wrote:
> On 12-07-17 15:12, Andy Shevchenko wrote:
> > On Wed, 2017-07-12 at 14:44 +0200, Hans de Goede wrote:
> > > On 12-07-17 14:38, Andy Shevchenko wrote:
> > > > On Wed, 2017-07-12 at 14:31 +0200, Hans de Goede wrote:
> > > > >
> > > that the ACPI tables / or a driver want to use a pin as gpio and
> > > it
> > > has
> > > been setup differently (as a special function) by the firmware.
> >
> > Yes, and what I'm asking are the details of it, what product, what
> > device needs that pin, and why do we think that is the rightful
> > request
> > from the OS?
>
> I will need to do some digging to get you these details, I will get
> back to you on that later.
Thanks!
> This discussion really is orthogonal to this patch,
Correct. I would like to know the details to have this knowledge in case
of something similar might happen with other device(s).
> calling WARN_ON
> for something outside of the control of the kernel clearly is the
> wrong
> thing to do. So in the mean time can I have your ack for this patch ?
As I said, patch is okay to me.
Acked-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
--
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy
next prev parent reply other threads:[~2017-07-12 15:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-12 12:31 [PATCH] pinctrl: baytrail: Do not call WARN_ON for a firmware bug Hans de Goede
2017-07-12 12:38 ` Andy Shevchenko
2017-07-12 12:44 ` Hans de Goede
2017-07-12 13:12 ` Andy Shevchenko
2017-07-12 14:18 ` Hans de Goede
2017-07-12 15:25 ` Andy Shevchenko [this message]
2017-08-01 13:19 ` Linus Walleij
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=1499873135.22624.366.camel@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=hdegoede@redhat.com \
--cc=heikki.krogerus@linux.intel.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
/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).