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, LKML <linux-kernel@vger.kernel.org>
Subject: [PATCH 0/5] serial: 8250: 8250_dw changes and dynamic capabilities
Date: Wed, 28 Nov 2012 14:48:39 +0200 [thread overview]
Message-ID: <1354106924-11013-1-git-send-email-heikki.krogerus@linux.intel.com> (raw)
Hi,
These are mainly small changes to 8250_dw.c. The interesting patch is
probable the addition to 8250.c that would allow the drivers to
deliver their UART's capabilities when they are registering ports.
Heikki Krogerus (5):
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
drivers/tty/serial/8250/8250.c | 22 ++++--
drivers/tty/serial/8250/8250_dw.c | 140 +++++++++++++++++++++++++++----------
2 files changed, 120 insertions(+), 42 deletions(-)
--
1.7.10.4
next reply other threads:[~2012-11-28 12:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-28 12:48 Heikki Krogerus [this message]
2012-11-28 12:48 ` [PATCH 1/5] serial: 8250: Allow drivers to deliver capabilities Heikki Krogerus
2012-11-28 12:48 ` [PATCH 2/5] serial: 8250_dw: Don't use UPF_FIXED_TYPE Heikki Krogerus
2012-11-28 12:48 ` [PATCH 3/5] serial: 8250_dw: Map IO memory Heikki Krogerus
2012-11-28 12:48 ` [PATCH 4/5] serial: 8250_dw: Move device tree code to separate function Heikki Krogerus
2012-11-28 12:48 ` [PATCH 5/5] serial: 8250_dw: Set FIFO size dynamically Heikki Krogerus
2012-11-28 13:18 ` Alan Cox
2012-11-28 13:37 ` Heikki Krogerus
2012-11-28 14:29 ` Heikki Krogerus
2012-11-30 13:48 ` [PATCH 0/5] serial: 8250: 8250_dw changes and dynamic capabilities 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=1354106924-11013-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).