From: Linus Walleij <linus.walleij@linaro.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Amelie Delaunay <amelie.delaunay@st.com>
Subject: [GIT PULL] pin control fixes for v5.4
Date: Sun, 10 Nov 2019 01:26:26 +0100 [thread overview]
Message-ID: <CACRpkdaomX3PGdf9LPvi+S2yzTCs0f-G+TJkdfo=5HcoOJjehg@mail.gmail.com> (raw)
Hi Linus,
some late pin control fixes, mostly Intel stuff.
Details in the signed tag and the commits!
Please pull it in!
Yours,
Linus Walleij
The following changes since commit d6d5df1db6e9d7f8f76d2911707f7d5877251b02:
Linux 5.4-rc5 (2019-10-27 13:19:19 -0400)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-pinctrl.git
tags/pinctrl-v5.4-3
for you to fetch changes up to 63e006c107ff4235d2a8fd52704f283d23642537:
pinctrl: stmfx: fix valid_mask init sequence (2019-11-07 10:06:46 +0100)
----------------------------------------------------------------
Pin control fixes for v5.4:
- Fix glitch risks in the Intel GPIO
- Fix the Intel Cherryview valid irq mask calculation.
- Allocate the Intel Cherryview irqchip dynamically.
- Fix the valid mask init sequency on the ST STMFX driver.
----------------------------------------------------------------
Amelie Delaunay (1):
pinctrl: stmfx: fix valid_mask init sequence
Andy Shevchenko (2):
pinctrl: intel: Avoid potential glitches if pin is in GPIO mode
pinctrl: cherryview: Allocate IRQ chip dynamic
Hans de Goede (1):
pinctrl: cherryview: Fix irq_valid_mask calculation
Linus Walleij (1):
Merge tag 'intel-pinctrl-fixes-v5.4-2' of
git://git.kernel.org/.../pinctrl/intel into fixes
drivers/pinctrl/intel/pinctrl-cherryview.c | 26 +++++++++++++-------------
drivers/pinctrl/intel/pinctrl-intel.c | 21 ++++++++++++++++++++-
drivers/pinctrl/pinctrl-stmfx.c | 14 --------------
3 files changed, 33 insertions(+), 28 deletions(-)
next reply other threads:[~2019-11-10 0:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-10 0:26 Linus Walleij [this message]
2019-11-10 21:00 ` [GIT PULL] pin control fixes for v5.4 pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2019-10-22 8:57 Linus Walleij
2019-10-22 11:20 ` 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='CACRpkdaomX3PGdf9LPvi+S2yzTCs0f-G+TJkdfo=5HcoOJjehg@mail.gmail.com' \
--to=linus.walleij@linaro.org \
--cc=amelie.delaunay@st.com \
--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).