From: Linus Walleij <linus.walleij@linaro.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>
Subject: [GIT PULL] GPIO fixes for v5.4 take two
Date: Thu, 17 Oct 2019 09:18:32 +0200 [thread overview]
Message-ID: <CACRpkdb_iv9Ywpddu1AiG+b+AMC7LUcnPRjf7yPHnt78JNDtuQ@mail.gmail.com> (raw)
Hi Linus,
here are some GPIO fixes, pertaining to Intel SoCs.
Details in the signed tag as usual.
Please pull it in!
Yours,
Linus Walleij
The following changes since commit 4f5cafb5cb8471e54afdc9054d973535614f7675:
Linux 5.4-rc3 (2019-10-13 16:37:36 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-gpio.git
tags/gpio-v5.4-3
for you to fetch changes up to 75e99bf5ed8fa74bc80d693d8e0a24eeaa38202b:
gpio: lynxpoint: set default handler to be handle_bad_irq()
(2019-10-15 01:19:05 +0200)
----------------------------------------------------------------
GPIO fixes for the v5.4 series
The fixes pertain to a problem with initializing the Intel GPIO
irqchips when adding gpiochips, Andy fixed it up elegantly by
adding a hardware initialization callback to the struct
gpio_irq_chip so let's use this. Tested and verified on the
target hardware.
----------------------------------------------------------------
Andy Shevchenko (6):
gpio: merrifield: Restore use of irq_base
gpiolib: Initialize the hardware with a callback
gpio: intel-mid: Move hardware initialization to callback
gpio: lynxpoint: Move hardware initialization to callback
gpio: merrifield: Move hardware initialization to callback
gpio: lynxpoint: set default handler to be handle_bad_irq()
drivers/gpio/gpio-intel-mid.c | 9 ++++++---
drivers/gpio/gpio-lynxpoint.c | 10 ++++++----
drivers/gpio/gpio-merrifield.c | 9 ++++++---
drivers/gpio/gpiolib.c | 22 +++++++++++++++++++++-
include/linux/gpio/driver.h | 8 ++++++++
5 files changed, 47 insertions(+), 11 deletions(-)
next reply other threads:[~2019-10-17 7:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-17 7:18 Linus Walleij [this message]
2019-10-17 16:10 ` [GIT PULL] GPIO fixes for v5.4 take two pr-tracker-bot
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=CACRpkdb_iv9Ywpddu1AiG+b+AMC7LUcnPRjf7yPHnt78JNDtuQ@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).