From: William Breathitt Gray <vilhelm.gray@gmail.com>
To: linus.walleij@linaro.org, gnurou@gmail.com
Cc: linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
William Breathitt Gray <vilhelm.gray@gmail.com>
Subject: [PATCH 0/5] gpio: Add support for GPIO names for several ISA_BUS_API drivers
Date: Mon, 30 Jan 2017 12:04:56 -0500 [thread overview]
Message-ID: <cover.1485795642.git.vilhelm.gray@gmail.com> (raw)
This patchset sets the gpio_chip names option of several ISA_BUS_API
GPIO drivers with an array of GPIO line names that match their
respective manual documentation. This should make it easier for users to
identify which GPIO line corresponds to a respective GPIO pin on their
device.
William Breathitt Gray (5):
gpio: 104-dio-48e: Add support for GPIO names
gpio: 104-idi-48: Add support for GPIO names
gpio: 104-idio-16: Add support for GPIO names
gpio: gpio-mm: Add support for GPIO names
gpio: ws16c48: Add support for GPIO names
drivers/gpio/gpio-104-dio-48e.c | 23 ++++++++++++++++++++++-
drivers/gpio/gpio-104-idi-48.c | 15 ++++++++++++++-
drivers/gpio/gpio-104-idio-16.c | 11 ++++++++++-
drivers/gpio/gpio-gpio-mm.c | 15 ++++++++++++++-
drivers/gpio/gpio-ws16c48.c | 19 ++++++++++++++++++-
5 files changed, 78 insertions(+), 5 deletions(-)
--
2.11.0
next reply other threads:[~2017-01-30 17:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-30 17:04 William Breathitt Gray [this message]
2017-01-30 17:05 ` [PATCH 1/5] gpio: 104-dio-48e: Add support for GPIO names William Breathitt Gray
2017-01-30 17:05 ` [PATCH 2/5] gpio: 104-idi-48: " William Breathitt Gray
2017-01-30 17:05 ` [PATCH 3/5] gpio: 104-idio-16: " William Breathitt Gray
2017-01-30 17:05 ` [PATCH 4/5] gpio: gpio-mm: " William Breathitt Gray
2017-01-30 17:05 ` [PATCH 5/5] gpio: ws16c48: " William Breathitt Gray
2017-01-30 17:59 ` kbuild test robot
2017-01-30 17:59 ` kbuild test robot
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=cover.1485795642.git.vilhelm.gray@gmail.com \
--to=vilhelm.gray@gmail.com \
--cc=gnurou@gmail.com \
--cc=linus.walleij@linaro.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 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.