From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Grygorii Strashko <grygorii.strashko@ti.com>,
Linus Walleij <linus.walleij@linaro.org>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Chris Gorman <chrisjohgorman@gmail.com>,
Heikki Krogerus <heikki.krogerus@linux.intel.com>
Subject: Re: [PATCH] pinctrl: cherryview: fix issues caused by dynamic gpio irqs mapping
Date: Wed, 4 Oct 2017 09:41:03 +0300 [thread overview]
Message-ID: <20171004064103.GO2761@lahna.fi.intel.com> (raw)
In-Reply-To: <CAHp75Vce0v0d9x4AiDnbNfqv4c_erxwNXsd+ApCTEfybCEOMdA@mail.gmail.com>
On Tue, Oct 03, 2017 at 08:54:30PM +0300, Andy Shevchenko wrote:
> I'm not sure about this approach. It might be some other broken BIOS
> discovered with some other driver (like pinctrl-baytrail.c as an
> hypothetical example).
Let's deal that separately if it ever happens.
> Alternative is to deselect SPARSE_IRQ (though it makes it non-usable
> in entire x86 world).
No way.
next prev parent reply other threads:[~2017-10-04 6:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-03 17:00 [PATCH] pinctrl: cherryview: fix issues caused by dynamic gpio irqs mapping Grygorii Strashko
2017-10-03 17:00 ` Grygorii Strashko
2017-10-03 17:54 ` Andy Shevchenko
2017-10-03 18:20 ` Grygorii Strashko
2017-10-03 18:20 ` Grygorii Strashko
2017-10-04 6:41 ` Mika Westerberg [this message]
2017-10-04 6:42 ` Mika Westerberg
2017-10-06 8:19 ` Mika Westerberg
2017-10-06 13:02 ` Chris Gorman
2017-10-04 17:01 ` Chris Gorman
2017-10-08 0:42 ` Linus Walleij
2017-10-09 18:04 ` Grygorii Strashko
-- strict thread matches above, loose matches on Subject: below --
2017-10-04 16:07 Chris Gorman
2017-10-04 16:25 ` Mika Westerberg
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=20171004064103.GO2761@lahna.fi.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=andy.shevchenko@gmail.com \
--cc=chrisjohgorman@gmail.com \
--cc=grygorii.strashko@ti.com \
--cc=heikki.krogerus@linux.intel.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.