From: Bartosz Golaszewski <brgl@bgdev.pl>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: linux-gpio@vger.kernel.org,
Bartosz Golaszewski <bgolaszewski@baylibre.com>
Subject: [GIT PULL] gpio: updates for v5.7 part 3
Date: Tue, 24 Mar 2020 09:29:03 +0100 [thread overview]
Message-ID: <20200324082903.19366-1-brgl@bgdev.pl> (raw)
From: Bartosz Golaszewski <bgolaszewski@baylibre.com>
Linus,
this is the third and probably last batch of changes for v5.7 I picked up
into my tree. Details are in the signed tag. Please pull.
Bartosz
The following changes since commit 9cd0c5e02ee4fcf8d0905def9b096b4222e179c2:
Merge branch 'devel' into for-next (2020-03-03 15:02:01 +0100)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/brgl/linux.git tags/gpio-updates-for-v5.7-part3
for you to fetch changes up to 8afb2c17f8309c99df1cb6a97918663978128e2c:
tools: gpio: Fix typo in gpio-utils (2020-03-23 10:39:15 +0100)
----------------------------------------------------------------
gpio updates for v5.7 part 3
- improve comments in the uapi header
- fix documentation issues
- add a warning to gpio-pl061 when the IRQ line is not configured
- allow building gpio-mxc and gpio-mxs with COMPILE_TEST enabled
- don't print an error message when an optional IRQ is missing in gpio-mvebu
- fix a potential segfault in gpio-hammer
- fix a couple typos and coding style issues in gpio tools
- provide a new flag in gpio-mmio and use it in mt7621 to fix an issue with
the controller ignoring value setting when a GPIO is in input mode
- slightly refactor gpio_name_to_desc()
----------------------------------------------------------------
Alexander Sverdlin (1):
gpio: pl061: Warn when IRQ line has not been configured
Anson Huang (2):
gpio: mxc: Add COMPILE_TEST support for GPIO_MXC
gpio: mxs: add COMPILE_TEST support for GPIO_MXS
Chris Packham (1):
gpio: mvebu: avoid error message for optional IRQ
Chuanhong Guo (2):
gpio: mmio: introduce BGPIOF_NO_SET_ON_INPUT
gpio: mt7621: add BGPIOF_NO_SET_ON_INPUT flag
Colin Ian King (1):
tools: gpio-hammer: fix spelling mistake: "occurences" -> "occurrences"
Gabriel Ravier (2):
tools: gpio-hammer: Avoid potential overflow in main
tools: gpio-hammer: Apply scripts/Lindent and retain good changes
Jonathan Neuschäfer (1):
gpio: uapi: Improve phrasing around arrays representing empty strings
Mauro Carvalho Chehab (1):
docs: gpio: driver.rst: don't mark literal blocks twice
Michał Mirosław (1):
gpiolib: gpio_name_to_desc: factor out !name check
Mykyta Poturai (1):
tools: gpio: Fix typo in gpio-utils
Documentation/driver-api/gpio/driver.rst | 4 ++--
drivers/gpio/Kconfig | 4 ++--
drivers/gpio/gpio-mmio.c | 23 +++++++++++++++++++----
drivers/gpio/gpio-mt7621.c | 4 ++--
drivers/gpio/gpio-mvebu.c | 2 +-
drivers/gpio/gpio-pl061.c | 6 ++----
drivers/gpio/gpiolib.c | 5 ++++-
include/linux/gpio/driver.h | 1 +
include/uapi/linux/gpio.h | 8 ++++----
tools/gpio/gpio-hammer.c | 19 +++++++++++++++++--
tools/gpio/gpio-utils.c | 6 +++---
11 files changed, 57 insertions(+), 25 deletions(-)
next reply other threads:[~2020-03-24 8:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-24 8:29 Bartosz Golaszewski [this message]
2020-03-24 9:04 ` [GIT PULL] gpio: updates for v5.7 part 3 Linus Walleij
2020-03-24 12:34 ` Bartosz Golaszewski
2020-03-24 16:58 ` Linus Walleij
2020-03-24 17:59 ` Bartosz Golaszewski
2020-03-24 21:15 ` Linus Walleij
2020-03-25 8:54 ` Bartosz Golaszewski
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=20200324082903.19366-1-brgl@bgdev.pl \
--to=brgl@bgdev.pl \
--cc=bgolaszewski@baylibre.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@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.