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 v4 0/9] serial/gpio: exar: Fixes and support for IOT2000
Date: Tue, 30 May 2017 09:01:15 +0200 [thread overview]
Message-ID: <cover.1496127684.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 v4:
- fold v3 patches 8 and 9 together
- use DT-like property names
I would suggest to send this series as a whole through one branch,
either gpio after receiving acks from Greg or serial (most acks from
Linus are there).
Jan
Jan Kiszka (9):
serial: exar: Leave MPIOs as output for Commtech adapters
gpio-exar/8250-exar: Do not even instantiate a GPIO device for
Commtech cards
gpio-exar/8250-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: Rearrange gpiochip parenthood
gpio-exar/8250-exar: Make set of exported GPIOs configurable
serial: exar: Add support for IOT2040 device
drivers/gpio/gpio-exar.c | 75 ++++++++-------
drivers/tty/serial/8250/8250_exar.c | 180 ++++++++++++++++++++++++++++++++++--
2 files changed, 208 insertions(+), 47 deletions(-)
--
2.12.3
next reply other threads:[~2017-05-30 7:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-30 7:01 Jan Kiszka [this message]
2017-05-30 7:01 ` [PATCH v4 1/9] serial: exar: Leave MPIOs as output for Commtech adapters Jan Kiszka
2017-05-30 7:01 ` [PATCH v4 2/9] gpio-exar/8250-exar: Do not even instantiate a GPIO device for Commtech cards Jan Kiszka
2017-05-30 18:33 ` Andy Shevchenko
2017-05-31 16:34 ` Jan Kiszka
2017-05-31 18:02 ` Andy Shevchenko
2017-05-30 7:01 ` [PATCH v4 3/9] gpio-exar/8250-exar: Fix passing in of parent PCI device Jan Kiszka
2017-05-30 7:01 ` [PATCH v4 4/9] gpio: exar: Allocate resources on behalf of the platform device Jan Kiszka
2017-05-30 7:01 ` [PATCH v4 5/9] gpio: exar: Fix iomap request Jan Kiszka
2017-05-30 7:01 ` [PATCH v4 6/9] gpio: exar: Fix reading of directions and values Jan Kiszka
2017-05-30 7:01 ` [PATCH v4 7/9] gpio-exar/8250-exar: Rearrange gpiochip parenthood Jan Kiszka
2017-05-30 7:01 ` [PATCH v4 8/9] gpio-exar/8250-exar: Make set of exported GPIOs configurable Jan Kiszka
2017-05-30 18:35 ` Andy Shevchenko
2017-05-30 7:01 ` [PATCH v4 9/9] serial: exar: Add support for IOT2040 device Jan Kiszka
2017-05-30 18:38 ` Andy Shevchenko
2017-05-30 18:39 ` [PATCH v4 0/9] serial/gpio: exar: Fixes and support for IOT2000 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.1496127684.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).