From: Heikki Krogerus <heikki.krogerus@linux.intel.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Alan Cox <alan@linux.intel.com>, Jamie Iles <jamie@jamieiles.com>,
linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCHv3 0/8] serial: 8250: 8250_dw changes and dmaengine support
Date: Thu, 10 Jan 2013 11:25:04 +0200 [thread overview]
Message-ID: <1357809912-25790-1-git-send-email-heikki.krogerus@linux.intel.com> (raw)
Changes since v2:
- ACPI support for 8250_dw.c
- dmaengine API support for 8250
It looks like there are a few UART drivers that are more or less
identical with 8250.c except they include DMA support, so if we had
DMA support in 8250.c there may be no need for them. Since dmaengine
is now supported on most platforms, I decided to suggest this
solution.
I tried to make the DMA support as simple as I could. Single transfers
with single descriptors. This should be sufficient in most cases.
Heikki Krogerus (8):
serial: 8250: Allow drivers to deliver capabilities
serial: 8250_dw: Don't use UPF_FIXED_TYPE
serial: 8250_dw: Map IO memory
serial: 8250_dw: Move device tree code to separate function
serial: 8250_dw: Set FIFO size dynamically
serial: 8250_dw: Add ACPI 5.0 support
serial: 8250: Add support for dmaengine
serial: 8250_dw: Enable DMA support with ACPI
drivers/tty/serial/8250/8250.c | 53 ++++++--
drivers/tty/serial/8250/8250.h | 50 ++++++++
drivers/tty/serial/8250/8250_dma.c | 213 +++++++++++++++++++++++++++++++
drivers/tty/serial/8250/8250_dw.c | 248 ++++++++++++++++++++++++++++++------
drivers/tty/serial/8250/Kconfig | 10 +-
drivers/tty/serial/8250/Makefile | 1 +
include/linux/serial_8250.h | 4 +
7 files changed, 532 insertions(+), 47 deletions(-)
create mode 100644 drivers/tty/serial/8250/8250_dma.c
--
1.7.10.4
next reply other threads:[~2013-01-10 9:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-10 9:25 Heikki Krogerus [this message]
2013-01-10 9:25 ` [PATCHv3 1/8] serial: 8250: Allow drivers to deliver capabilities Heikki Krogerus
2013-01-10 9:25 ` [PATCHv3 2/8] serial: 8250_dw: Don't use UPF_FIXED_TYPE Heikki Krogerus
2013-01-10 9:25 ` [PATCHv3 3/8] serial: 8250_dw: Map IO memory Heikki Krogerus
2013-01-10 9:25 ` [PATCHv3 4/8] serial: 8250_dw: Move device tree code to separate function Heikki Krogerus
2013-01-10 9:25 ` [PATCHv3 5/8] serial: 8250_dw: Set FIFO size dynamically Heikki Krogerus
2013-01-10 9:25 ` [PATCHv3 6/8] serial: 8250_dw: Add ACPI 5.0 support Heikki Krogerus
2013-01-10 9:25 ` [PATCHv3 7/8] serial: 8250: Add support for dmaengine Heikki Krogerus
2013-01-10 9:25 ` [PATCHv3 8/8] serial: 8250_dw: Enable DMA support with ACPI Heikki Krogerus
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=1357809912-25790-1-git-send-email-heikki.krogerus@linux.intel.com \
--to=heikki.krogerus@linux.intel.com \
--cc=alan@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=jamie@jamieiles.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@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 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).