From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Marc Zyngier <marc.zyngier@arm.com>,
Thomas Gleixner <tglx@linutronix.de>,
Phidias Chiang <phidias.chiang@canonical.com>,
Anisse Astier <anisse@astier.eu>,
Heikki Krogerus <heikki.krogerus@linux.intel.com>,
Yu C Chen <yu.c.chen@intel.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/3] gpio / pinctrl: cherryview: Fix missing events from EC
Date: Fri, 16 Sep 2016 13:52:40 +0300 [thread overview]
Message-ID: <20160916105243.93933-1-mika.westerberg@linux.intel.com> (raw)
Hi,
Up until now systems having Intel Cherryview/Braswell might lose GPEs
(General Purpose Events) from EC (Embedded Controller) because the pinctrl
driver masks all interrupt sources at probe time. I tried to fix this
already in bcb48cca23ec ("pinctrl: cherryview: Do not mask all interrupts
in probe") but it resulted that the irq core masked all the interrupts
because now we pass handle_bad_irq() as default handler for the irqchip.
After reading again the hardware spec, I think I finally understand the
problem correctly. In summary for southwest and north communities only the
first 8 (or 16) wires can be used to generate interrupts. Rest are reserved
for GPEs.
We fix this by excluding these only GPE capable wires from the IRQ domain
of the gpiochip.
This first follows what LinusW suggested and adds irq_valid_mask for each
gpiochip and then provides a function which allows manipulation from
drivers. Then we switch pinctrl-cherryview to use it.
Previous version of the patches and the discussion around this issue can be
found here:
https://lkml.org/lkml/2015/5/22/111
Changes from v1 of the series:
- Only allocate irq_valid_mask when needed
- Provide gpiochip_irqchip_exclude_irq() helper which allows drivers to
select which GPIOs to exclude.
- Use ->nrirqs in chv_gpio_irq_handler()
- Added patch to convert the driver to use devm_gpiochip_add_data() so
we can just return if gpiochip_irqchip_exclude_irq() fails (and also
this simplifies the driver).
Mika Westerberg (3):
gpiolib: Make it possible to exclude GPIOs from IRQ domain
pinctrl: cherryview: Convert to use devm_gpiochip_add_data()
pinctrl: cherryview: Do not add all southwest and north GPIOs to IRQ
domain
Documentation/gpio/driver.txt | 5 +++
drivers/gpio/gpiolib.c | 72 ++++++++++++++++++++++++++++--
drivers/pinctrl/intel/pinctrl-cherryview.c | 57 +++++++++++++++--------
include/linux/gpio/driver.h | 5 +++
4 files changed, 117 insertions(+), 22 deletions(-)
--
2.9.3
next reply other threads:[~2016-09-16 10:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-16 10:52 Mika Westerberg [this message]
2016-09-16 10:52 ` [PATCH v2 1/3] gpiolib: Make it possible to exclude GPIOs from IRQ domain Mika Westerberg
2016-09-17 13:13 ` Marc Zyngier
2016-09-19 8:16 ` Mika Westerberg
2016-09-16 10:52 ` [PATCH v2 2/3] pinctrl: cherryview: Convert to use devm_gpiochip_add_data() Mika Westerberg
2016-09-16 10:52 ` [PATCH v2 3/3] pinctrl: cherryview: Do not add all southwest and north GPIOs to IRQ domain 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=20160916105243.93933-1-mika.westerberg@linux.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=anisse@astier.eu \
--cc=heikki.krogerus@linux.intel.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=phidias.chiang@canonical.com \
--cc=tglx@linutronix.de \
--cc=yu.c.chen@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).