From: David Daney <ddaney@caviumnetworks.com>
To: linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mips@linux-mips.org
Cc: "Paoletti, Tomaso" <Tomaso.Paoletti@caviumnetworks.com>
Subject: [PATCH 0/4] serial: 8250 driver improvements & Cavium OCTEON serial support
Date: Tue, 07 Oct 2008 16:43:34 -0700 [thread overview]
Message-ID: <48EBF426.9080500@caviumnetworks.com> (raw)
This is a follow up to the 'Allow for replaceable I/O functions in
8250 driver' patch I sent yesterday. I hope it addresses the issues
raised by Alan Cox and Arnd Bergmann.
The four parts of the patch are as follows:
1/4) Add replaceable I/O functions to the 8250 driver. This allows
platform specific register access code to be moved out of the
driver into the platform support files.
2/4) Add a new port flag UPF_FIXED_TYPE that allows callers of
serial8250_register_port() to specify the port type and disables
probing.
3/4) Add a 'bugs' field to the serial8250_config. Used in conjunction
with 2/4, this allows the bugs flags to be set without probing.
4/4) Add an entry to uart_config for PORT_OCTEON describing the
OCTEON's internal UARTs. Two new bug flags are defined to
account for PORT_OCTEON's peculiarities.
Comments welcome,
David Daney
next reply other threads:[~2008-10-07 23:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-07 23:43 David Daney [this message]
2008-10-07 23:49 ` [PATCH 1/4] serial: 8250 driver replaceable i/o functions David Daney
2008-10-08 0:12 ` H. Peter Anvin
2008-10-08 0:29 ` David Daney
2008-10-07 23:52 ` [PATCH 2/4] serial: Allow port type to be specified when calling serial8250_register_port David Daney
2008-10-07 23:57 ` [PATCH 3/4] serial: Allow port type to specify bugs that are not probed for David Daney
2008-10-07 23:59 ` [PATCH 4/4] serial: Add new uart_config for PORT_OCTEON David Daney
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=48EBF426.9080500@caviumnetworks.com \
--to=ddaney@caviumnetworks.com \
--cc=Tomaso.Paoletti@caviumnetworks.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.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