From: ben.hutchings@codethink.co.uk (Ben Hutchings)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] [PATCH 00/25] EXAR UART support for IOT2040 device
Date: Thu, 14 Sep 2017 17:55:32 +0100 [thread overview]
Message-ID: <1505408132.1860.3.camel@codethink.co.uk> (raw)
In-Reply-To: <cover.1504119982.git.jan.kiszka@siemens.com>
On Wed, 2017-08-30 at 21:05 +0200, Jan Kiszka wrote:
> Second chunk: This imports a number of preparatory patches in order to
> fully exploit the PCI-attached dual-port EXAR with RS232/422/485 on the
> IOT2040.
>
> To avoid having to backport also API-changing patches for platform
> devices, I've slightly modified two patches to use a communication
> pattern that does not require these changes.
[...]
Applied this series, except the gpiolib additions which were needed
earlier.
Ben.
--
Ben Hutchings
Software Developer, Codethink Ltd.
next prev parent reply other threads:[~2017-09-14 16:55 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-30 19:05 [cip-dev] [PATCH 00/25] EXAR UART support for IOT2040 device Jan Kiszka
2017-08-30 19:05 ` [cip-dev] [PATCH 01/25] serial: exar: split out the exar code from 8250_pci Jan Kiszka
2017-08-30 19:05 ` [cip-dev] [PATCH 02/25] serial: 8250_pci: Use symbolic constants for EXAR's MPIO registers Jan Kiszka
2017-08-30 19:06 ` [cip-dev] [PATCH 03/25] serial: 8250_pci: remove exar code Jan Kiszka
2017-08-30 19:06 ` [cip-dev] [PATCH 04/25] serial: exar: Fix mapping of port I/O resources Jan Kiszka
2017-08-30 19:06 ` [cip-dev] [PATCH 05/25] serial: exar: Fix initialization of EXAR registers for ports > 0 Jan Kiszka
2017-08-30 19:06 ` [cip-dev] [PATCH 06/25] serial: exar: Fix feature control register constants Jan Kiszka
2017-08-30 19:06 ` [cip-dev] [PATCH 07/25] serial: exar: Move Commtech adapters to 8250_exar as well Jan Kiszka
2017-08-30 19:06 ` [cip-dev] [PATCH 08/25] serial: pci: Remove unused pci_boards entries Jan Kiszka
2017-08-30 19:06 ` [cip-dev] [PATCH 09/25] serial: 8250_EXAR: fix duplicate Kconfig text and add missing help text Jan Kiszka
2017-08-30 19:06 ` [cip-dev] [PATCH 10/25] serial: exar: Preconfigure xr17v35x MPIOs as output Jan Kiszka
2017-08-30 19:06 ` [cip-dev] [PATCH 11/25] serial: exar: Leave MPIOs as output for Commtech adapters Jan Kiszka
2017-08-30 19:06 ` [cip-dev] [PATCH 12/25] serial: uapi: Add support for bus termination Jan Kiszka
2017-08-30 19:06 ` [cip-dev] [PATCH 13/25] gpio: add a data pointer to gpio_chip Jan Kiszka
2017-08-30 19:06 ` [cip-dev] [PATCH 14/25] gpio: Add devm_ apis for gpiochip_add_data and gpiochip_remove Jan Kiszka
2017-08-30 19:06 ` [cip-dev] [PATCH 15/25] gpio: exar: add gpio for exar cards Jan Kiszka
2017-08-30 19:06 ` [cip-dev] [PATCH 16/25] gpio: exar: Set proper output level in exar_direction_output Jan Kiszka
2017-08-30 19:06 ` [cip-dev] [PATCH 17/25] gpio-exar/8250-exar: Fix passing in of parent PCI device Jan Kiszka
2017-08-30 19:06 ` [cip-dev] [PATCH 18/25] gpio: exar: Allocate resources on behalf of the platform device Jan Kiszka
2017-08-30 19:06 ` [cip-dev] [PATCH 19/25] gpio: exar: Fix reading of directions and values Jan Kiszka
2017-08-30 19:06 ` [cip-dev] [PATCH 20/25] gpio-exar/8250-exar: Do not even instantiate a GPIO device for Commtech cards Jan Kiszka
2017-08-30 19:06 ` [cip-dev] [PATCH 21/25] gpio: exar: Fix iomap request Jan Kiszka
2017-08-30 19:06 ` [cip-dev] [PATCH 22/25] gpio-exar/8250-exar: Rearrange gpiochip parenthood Jan Kiszka
2017-08-30 19:06 ` [cip-dev] [PATCH 23/25] serial: exar: Factor out platform hooks Jan Kiszka
2017-08-30 19:06 ` [cip-dev] [PATCH 24/25] gpio-exar/8250-exar: Make set of exported GPIOs configurable Jan Kiszka
2017-08-30 19:06 ` [cip-dev] [PATCH 25/25] serial: exar: Add support for IOT2040 device Jan Kiszka
2017-09-14 16:55 ` Ben Hutchings [this message]
2017-09-14 19:37 ` [cip-dev] [PATCH 00/25] EXAR UART " 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=1505408132.1860.3.camel@codethink.co.uk \
--to=ben.hutchings@codethink.co.uk \
--cc=cip-dev@lists.cip-project.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox