From: Arnd Bergmann <arnd@arndb.de>
To: "Alon Ziv" <alonz@discretix.com>
Cc: linuxppc-dev@lists.ozlabs.org, linux-serial@vger.kernel.org,
Greg KH <greg@kroah.com>
Subject: Re: Bug in drivers/serial/of_serial.c?
Date: Thu, 19 Nov 2009 15:09:31 +0100 [thread overview]
Message-ID: <200911191509.31270.arnd@arndb.de> (raw)
In-Reply-To: <8B957E110B62714A84290A01A597805F05D2AE47@Exchange.discretix.com>
On Thursday 19 November 2009, Alon Ziv wrote:
> On Thursday, November 19, 2009, Arnd Bergmann wrote:
> > I'd still add support for the compatible="ns16550a" property
> > so that we do the right thing for future systems.
> >
>
> OK...
> ---
> Xilinx 16550 UART is actually 16550A-compatible
>
> Signed-off-by: Alon Ziv <alonz@discretix.com>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Does this go through the powerpc or the tty tree?
I'd be happy if either Ben or Greg could pick this up.
I'm happy to keep maintaining the driver itself but it
would be nice to know a definite subsystem maintainer
responsible for it.
Greg, if you want to take patches for of_serial.c generally,
I'll start forwarding them to you as they come in and make
sure they apply to your tree.
Arnd <><
> diff --git a/drivers/serial/of_serial.c b/drivers/serial/of_serial.c
> index 02406ba..241be77 100644
> --- a/drivers/serial/of_serial.c
> +++ b/drivers/serial/of_serial.c
> @@ -161,7 +161,9 @@ static int of_platform_serial_remove(struct
> of_device *ofdev)
> static struct of_device_id __devinitdata of_platform_serial_table[] = {
> { .type = "serial", .compatible = "ns8250", .data = (void
> *)PORT_8250, },
> { .type = "serial", .compatible = "ns16450", .data = (void
> *)PORT_16450, },
> + { .type = "serial", .compatible = "xlnx,xps-uart16550-2.00.b",
> .data = (void *)PORT_16550A, },
> { .type = "serial", .compatible = "ns16550", .data = (void
> *)PORT_16550, },
> + { .type = "serial", .compatible = "ns16550a", .data = (void
> *)PORT_16550A, },
> { .type = "serial", .compatible = "ns16750", .data = (void
> *)PORT_16750, },
> { .type = "serial", .compatible = "ns16850", .data = (void
> *)PORT_16850, },
> #ifdef CONFIG_SERIAL_OF_PLATFORM_NWPSERIAL
next prev parent reply other threads:[~2009-11-19 14:10 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-15 9:30 Bug in drivers/serial/of_serial.c? Alon Ziv
2009-11-16 8:09 ` Arnd Bergmann
2009-11-19 12:47 ` Alon Ziv
2009-11-19 13:01 ` Arnd Bergmann
2009-11-19 13:32 ` Alon Ziv
2009-11-19 13:41 ` Arnd Bergmann
2009-11-19 13:49 ` Alon Ziv
2009-11-19 14:09 ` Arnd Bergmann [this message]
2009-11-19 16:03 ` Greg KH
2009-11-19 17:22 ` Stephen Neuendorffer
2009-11-19 17:33 ` Arnd Bergmann
2009-11-19 17:42 ` Stephen Neuendorffer
2009-11-20 21:58 ` Grant Likely
2009-11-20 22:11 ` John Linn
2009-11-21 7:51 ` Grant Likely
2009-11-21 19:45 ` Arnd Bergmann
2009-11-22 22:42 ` Grant Likely
2009-11-22 22:43 ` Grant Likely
2009-11-20 21:56 ` Grant Likely
[not found] ` <977C41F842E66D4CB2E41332313B615008FC3C2F@XSJ-EXCHVS1.xlnx.xilinx.com>
2009-11-19 17:36 ` John Linn
2009-11-19 17:20 ` Stephen Neuendorffer
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=200911191509.31270.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=alonz@discretix.com \
--cc=greg@kroah.com \
--cc=linux-serial@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.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).