From: Stephen Warren <swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
To: gregkh-l3A5Bk7waGM@public.gmane.org
Cc: ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org,
linux-serial-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Stephen Warren <swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
Subject: [PATCH 0/2] tty/serial: Add PORT_TEGRA, fix break handling for it
Date: Tue, 17 May 2011 13:27:44 -0600 [thread overview]
Message-ID: <1305660466-4704-1-git-send-email-swarren@nvidia.com> (raw)
8250.c needs a specific PORT_TEGRA type for two reasons:
* RTOIE bit needs to be set, but UUE is reserved, so split RTOIE handling
out of PORT_XSCALE.
* A WAR is needed for break reception.
I'd like to get the first of these two patches merged into the tegra
arch for-next branch, so that I can modify the board files to explicitly
request the new port type rather than relying on auto-detection. As such,
could you please create a branch for that/these changes, then merge it
into tty-2.6.git, so that the same branch can be merged into Tegra's
for-next branch. Thanks.
Stephen Warren (2):
tty/serial: Add explicit PORT_TEGRA type
tty/serial: Fix break handling for PORT_TEGRA
drivers/tty/serial/8250.c | 37 +++++++++++++++++++++++++++++++++++--
drivers/tty/serial/8250.h | 1 +
include/linux/serial_core.h | 3 ++-
include/linux/serial_reg.h | 2 ++
4 files changed, 40 insertions(+), 3 deletions(-)
next reply other threads:[~2011-05-17 19:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-17 19:27 Stephen Warren [this message]
[not found] ` <1305660466-4704-1-git-send-email-swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2011-05-17 19:27 ` [PATCH 1/2] tty/serial: Add explicit PORT_TEGRA type Stephen Warren
2011-05-17 19:27 ` [PATCH 2/2] tty/serial: Fix break handling for PORT_TEGRA Stephen Warren
2011-05-17 19:38 ` [PATCH 0/2] tty/serial: Add PORT_TEGRA, fix break handling for it Greg KH
[not found] ` <20110517193836.GA6912-l3A5Bk7waGM@public.gmane.org>
2011-05-17 19:44 ` Stephen Warren
2011-05-17 21:58 ` Alan Cox
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=1305660466-4704-1-git-send-email-swarren@nvidia.com \
--to=swarren-ddmlm1+adcrqt0dzr+alfa@public.gmane.org \
--cc=gregkh-l3A5Bk7waGM@public.gmane.org \
--cc=ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
--cc=linux-serial-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.