From: Jan Kiszka <jan.kiszka@siemens.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Linus Walleij <linus.walleij@linaro.org>,
Alexandre Courbot <gnurou@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-serial@vger.kernel.org, linux-gpio@vger.kernel.org,
Sudip Mukherjee <sudip.mukherjee@codethink.co.uk>,
Andy Shevchenko <andy.shevchenko@gmail.com>,
Sascha Weisenberger <sascha.weisenberger@siemens.com>
Subject: [PATCH v2 0/6] serial/gpio: exar: Fixes and support for IOT2000
Date: Thu, 18 May 2017 16:59:03 +0200 [thread overview]
Message-ID: <cover.1495119548.git.jan.kiszka@siemens.com> (raw)
This makes the gpio-exar driver usable, which was prevented by a number
of fatal bugs, and adds support for the SIMATIC IOT2040 to the 8250-exar
driver and, indirectly, to gpio-exar as well. It's a cross-subsystem
series, so I'm also cross-posting to the serial and gpio lists.
Changes in v2:
- dropped already merged patches
- switched to platform_data structure for exar <-> gpio driver
communication
- use dmi_check_system() to express platform match
- adjusted bit logic style in exar_get_direction/value
Jan
Jan Kiszka (6):
gpio: exar: Fix passing in of parent PCI device
gpio: exar: Allocate resources on behalf of the platform device
gpio: exar: Fix iomap request
gpio: exar: Fix reading of directions and values
gpio-exar/8250-exar: Make set of exported GPIOs configurable
serial: exar: Add support for IOT2040 device
drivers/gpio/gpio-exar.c | 54 +++++++-----
drivers/tty/serial/8250/8250_exar.c | 151 ++++++++++++++++++++++++++++++--
include/linux/platform_data/gpio-exar.h | 25 ++++++
3 files changed, 198 insertions(+), 32 deletions(-)
create mode 100644 include/linux/platform_data/gpio-exar.h
--
2.12.0
next reply other threads:[~2017-05-18 14:59 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-18 14:59 Jan Kiszka [this message]
2017-05-18 14:59 ` [PATCH v2 1/6] gpio: exar: Fix passing in of parent PCI device Jan Kiszka
2017-05-18 17:14 ` Andy Shevchenko
2017-05-21 11:44 ` Jan Kiszka
2017-05-22 15:43 ` Linus Walleij
2017-05-18 14:59 ` [PATCH v2 2/6] gpio: exar: Allocate resources on behalf of the platform device Jan Kiszka
2017-05-18 14:59 ` [PATCH v2 3/6] gpio: exar: Fix iomap request Jan Kiszka
2017-05-18 14:59 ` [PATCH v2 4/6] gpio: exar: Fix reading of directions and values Jan Kiszka
2017-05-18 15:28 ` Andy Shevchenko
2017-05-18 14:59 ` [PATCH v2 5/6] gpio-exar/8250-exar: Make set of exported GPIOs configurable Jan Kiszka
2017-05-18 17:43 ` Andy Shevchenko
2017-05-21 11:43 ` Jan Kiszka
2017-05-22 16:33 ` Andy Shevchenko
2017-05-22 17:04 ` Jan Kiszka
2017-05-22 15:44 ` Linus Walleij
2017-05-18 14:59 ` [PATCH v2 6/6] serial: exar: Add support for IOT2040 device Jan Kiszka
2017-05-18 16:33 ` Andy Shevchenko
2017-05-18 16:39 ` Jan Kiszka
2017-05-18 16:58 ` Jan Kiszka
2017-05-18 17:23 ` Jan Kiszka
2017-05-18 17:41 ` Andy Shevchenko
2017-05-22 15:46 ` Linus Walleij
2017-05-22 16:28 ` Jan Kiszka
2017-05-22 16:34 ` Andy Shevchenko
2017-05-22 16:40 ` Jan Kiszka
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.1495119548.git.jan.kiszka@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=andy.shevchenko@gmail.com \
--cc=gnurou@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=sascha.weisenberger@siemens.com \
--cc=sudip.mukherjee@codethink.co.uk \
/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).