From: Nicolas Ferre <nicolas.ferre@atmel.com>
To: linux-arm-kernel@lists.infradead.org, grant.likely@secretlab.ca,
devicetree-discuss@lists.ozlabs.org, robherring2@gmail.com,
claudio@evidence.eu.com, jesper.nilsson@axis.com, alan@lxor
Cc: linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org
Subject: [PATCH v2 0/5] tty/serial: atmel_serial: Device Tree support
Date: Wed, 12 Oct 2011 18:06:55 +0200 [thread overview]
Message-ID: <1318435620-7481-1-git-send-email-nicolas.ferre@atmel.com> (raw)
Hi,
The goal of this patch series is to add device tree support to Atmel USART
driver: atmel_serial.
As this driver support RS485 mode, generic RS485 bindings have been added.
Some modifications are also included to ease the transition to parameter
settings comming from device tree.
The enumeration of ports is enhanced to be able to deal with several types
of port numbering: platform data, device tree or automatic.
Nicolas Ferre (5):
tty/serial: RS485 bindings for device tree
tty/serial: atmel_serial: change platform_data variable name
tty/serial: atmel_serial: whitespace and braces modifications
tty/serial: atmel_serial: auto-enumerate ports
tty/serial: atmel_serial: add device tree support
Documentation/devicetree/bindings/serial/rs485.txt | 31 +++++
.../devicetree/bindings/tty/serial/atmel-usart.txt | 27 +++++
Documentation/serial/serial-rs485.txt | 5 +
drivers/tty/serial/atmel_serial.c | 122 +++++++++++++++++---
4 files changed, 170 insertions(+), 15 deletions(-)
create mode 100644 Documentation/devicetree/bindings/serial/rs485.txt
create mode 100644 Documentation/devicetree/bindings/tty/serial/atmel-usart.txt
next reply other threads:[~2011-10-12 16:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-12 16:06 Nicolas Ferre [this message]
2011-10-12 16:06 ` [PATCH v2 1/5] tty/serial: RS485 bindings for device tree Nicolas Ferre
2011-10-12 16:06 ` [PATCH v2 3/5] tty/serial: atmel_serial: whitespace and braces modifications Nicolas Ferre
2011-10-13 1:02 ` Grant Likely
[not found] ` <37a19e194d02144aecd24f284f5e43979643a3c3.1318433947.git.nicolas.ferre-AIFe0yeh4nAAvxtiuMwx3w@public.gmane.org>
[not found] ` <1318435620-7481-1-git-send-email-nicolas.ferre-AIFe0yeh4nAAvxtiuMwx3w@public.gmane.org>
2011-10-12 16:06 ` [PATCH v2 2/5] tty/serial: atmel_serial: change platform_data variable name Nicolas Ferre
[not found] ` <58d65421a85737b7a25b967da09c3f564fc49be7.1318433947.git.nicolas.ferre-AIFe0yeh4nAAvxtiuMwx3w@public.gmane.org>
2011-10-13 1:01 ` Grant Likely
2011-10-12 16:06 ` [PATCH v2 4/5] tty/serial: atmel_serial: auto-enumerate ports Nicolas Ferre
2011-10-13 1:03 ` Grant Likely
2011-10-12 16:07 ` [PATCH v2 5/5] tty/serial: atmel_serial: add device tree support Nicolas Ferre
[not found] ` <46ce59e472d36715d8bed57570d2b7747323f4d4.1318433947.git.nicolas.ferre-AIFe0yeh4nAAvxtiuMwx3w@public.gmane.org>
2011-10-13 1:04 ` Grant Likely
2011-10-13 1:02 ` [PATCH v2 1/5] tty/serial: RS485 bindings for device tree Grant Likely
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=1318435620-7481-1-git-send-email-nicolas.ferre@atmel.com \
--to=nicolas.ferre@atmel.com \
--cc=alan@lxor \
--cc=claudio@evidence.eu.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=jesper.nilsson@axis.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=robherring2@gmail.com \
/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).