From: Linus Walleij <linus.walleij@linaro.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: "open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] pin control fixes for v4.19 take 4
Date: Fri, 28 Sep 2018 08:59:32 +0200 [thread overview]
Message-ID: <CACRpkdbQrZ7HHunuB_BdUo666riyg4ZKAOKo8BDHCY3RDYrXgQ@mail.gmail.com> (raw)
Hi Greg,
here are some three pin control fixes for v4.19.
All are x86 related.
Please pull them in!
Yours,
Linus Walleij
The following changes since commit 6bf4ca7fbc85d80446ac01c0d1d77db4d91a6d84:
Linux 4.19-rc5 (2018-09-23 19:15:18 +0200)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-pinctrl.git
tags/pinctrl-v4.19-4
for you to fetch changes up to 72923e5488f0604fac8ef2c7e683fabd3b4c203b:
Revert "pinctrl: intel: Do pin translation when lock IRQ"
(2018-09-25 12:50:00 +0200)
----------------------------------------------------------------
Pin control fixes for v4.19:
- Fixes to x86 hardware:
- AMD interrupt debounce issues
- Faulty Intel cannonlake register offset
- Revert pin translation IRQ locking
----------------------------------------------------------------
Daniel Kurtz (1):
pinctrl/amd: poll InterruptEnable bits in amd_gpio_irq_set_type
Mika Westerberg (2):
pinctrl: cannonlake: Fix HOSTSW_OWN register offset of H variant
Revert "pinctrl: intel: Do pin translation when lock IRQ"
drivers/pinctrl/intel/pinctrl-cannonlake.c | 33 ++++++++++++++++++------------
drivers/pinctrl/intel/pinctrl-intel.c | 32 -----------------------------
drivers/pinctrl/pinctrl-amd.c | 33 +++++++++++++++++++++---------
3 files changed, 43 insertions(+), 55 deletions(-)
next reply other threads:[~2018-09-28 6:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-28 6:59 Linus Walleij [this message]
2018-09-29 1:01 ` [GIT PULL] pin control fixes for v4.19 take 4 Greg KH
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=CACRpkdbQrZ7HHunuB_BdUo666riyg4ZKAOKo8BDHCY3RDYrXgQ@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=gregkh@linuxfoundation.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 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).