From: jingchang.lu@freescale.com (Jingchang Lu)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv2 0/2] tty: serial: fsl_lpuart: add 32-bit register support and dt-binding
Date: Mon, 14 Jul 2014 17:41:09 +0800 [thread overview]
Message-ID: <1405330871-9038-1-git-send-email-jingchang.lu@freescale.com> (raw)
This two patches change the fsl-lpuart dt-binding to exact SoC product revision
and add 32-bit big-endian register interface support which can be found on
Freescale LS1021A SoC platform.
---
changes in v2:
Fix undifined lpuart32_reg error.
----------------------------------------------------------------
Jingchang Lu (2):
dt-binding: fsl-lpuart: use exact SoC revision to document binding
tty: serial: fsl_lpuart: add 32-bit register interface support
Documentation/devicetree/bindings/serial/fsl-lpuart.txt | 6 +-
drivers/tty/serial/fsl_lpuart.c | 645 +++++++++++++++++++++++++++++++++++++++-
2 files changed, 642 insertions(+), 9 deletions(-)
next reply other threads:[~2014-07-14 9:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-14 9:41 Jingchang Lu [this message]
2014-07-14 9:41 ` [RESEND 1/2] dt-binding: fsl-lpuart: use exact SoC revision to document binding Jingchang Lu
2014-07-14 9:41 ` [PATCHv2 2/2] tty: serial: fsl_lpuart: add 32-bit register interface support Jingchang Lu
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=1405330871-9038-1-git-send-email-jingchang.lu@freescale.com \
--to=jingchang.lu@freescale.com \
--cc=linux-arm-kernel@lists.infradead.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).