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 0/8] serial/gpio: exar: Fixes and support for IOT2000
Date: Sat, 13 May 2017 09:28:58 +0200 [thread overview]
Message-ID: <cover.1494660546.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.
Jan
Jan Kiszka (8):
serial: exar: Preconfigure xr17v35x MPIOs as output
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
serial: uapi: Add support for bus termination
gpio-exar/8250-exar: Make set of exported GPIOs configurable
serial: exar: Add support for IOT2040 device
drivers/gpio/gpio-exar.c | 55 ++++++++------
drivers/tty/serial/8250/8250_exar.c | 145 +++++++++++++++++++++++++++++++++---
include/uapi/linux/serial.h | 3 +
3 files changed, 169 insertions(+), 34 deletions(-)
--
2.12.0
next reply other threads:[~2017-05-13 7:28 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-13 7:28 Jan Kiszka [this message]
2017-05-13 7:28 ` [PATCH 1/8] serial: exar: Preconfigure xr17v35x MPIOs as output Jan Kiszka
2017-05-22 15:38 ` Linus Walleij
2017-05-26 13:04 ` Jan Kiszka
2017-05-26 14:22 ` Andy Shevchenko
2017-05-26 18:38 ` Greg Kroah-Hartman
2017-05-13 7:29 ` [PATCH 2/8] gpio: exar: Fix passing in of parent PCI device Jan Kiszka
2017-05-13 13:25 ` Andy Shevchenko
2017-05-14 8:11 ` Jan Kiszka
2017-05-13 7:29 ` [PATCH 3/8] gpio: exar: Allocate resources on behalf of the platform device Jan Kiszka
2017-05-13 13:26 ` Andy Shevchenko
2017-05-22 15:39 ` Linus Walleij
2017-05-13 7:29 ` [PATCH 4/8] gpio: exar: Fix iomap request Jan Kiszka
2017-05-13 13:28 ` Andy Shevchenko
2017-05-13 7:29 ` [PATCH 5/8] gpio: exar: Fix reading of directions and values Jan Kiszka
2017-05-13 13:36 ` Andy Shevchenko
2017-05-18 5:20 ` Jan Kiszka
2017-05-18 10:11 ` Andy Shevchenko
2017-05-18 10:16 ` Jan Kiszka
2017-05-18 10:23 ` Andy Shevchenko
2017-05-18 10:28 ` Jan Kiszka
2017-05-13 7:29 ` [PATCH 6/8] serial: uapi: Add support for bus termination Jan Kiszka
2017-05-13 7:29 ` [PATCH 7/8] gpio-exar/8250-exar: Make set of exported GPIOs configurable Jan Kiszka
2017-05-13 13:50 ` Andy Shevchenko
2017-05-13 7:29 ` [PATCH 8/8] serial: exar: Add support for IOT2040 device Jan Kiszka
2017-05-13 13:54 ` Andy Shevchenko
2017-05-18 5:06 ` Jan Kiszka
2017-05-18 10:17 ` Andy Shevchenko
2017-05-18 10:37 ` Jan Kiszka
2017-05-18 10:56 ` Andy Shevchenko
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.1494660546.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).