linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Alon Ziv" <alonz@discretix.com>
To: "Arnd Bergmann" <arnd@arndb.de>,<linuxppc-dev@lists.ozlabs.org>
Subject: RE: Bug in drivers/serial/of_serial.c?
Date: Thu, 19 Nov 2009 15:32:19 +0200	[thread overview]
Message-ID: <8B957E110B62714A84290A01A597805F05D2AE44@Exchange.discretix.com> (raw)
In-Reply-To: <200911191401.37531.arnd@arndb.de>

Hi,

On Thursday, November 19, 2009, Arnd wrote:
> In that case, add another entry for the device encoded in the firmware
> itself. The ns16550 entry should be the second one after a more
specific
> one telling which device it is exactly.
>=20

Is the following better?

---
[PATCH] Xilinx 16550 UART is actually 16550A-compatible

diff --git a/drivers/serial/of_serial.c b/drivers/serial/of_serial.c
index 02406ba..40bf8f4 100644
--- a/drivers/serial/of_serial.c
+++ b/drivers/serial/of_serial.c
@@ -161,6 +161,7 @@ static int of_platform_serial_remove(struct
of_device *ofdev)
 static struct of_device_id __devinitdata of_platform_serial_table[] =3D =
{
 	{ .type =3D "serial", .compatible =3D "ns8250",   .data =3D (void
*)PORT_8250, },
 	{ .type =3D "serial", .compatible =3D "ns16450",  .data =3D (void
*)PORT_16450, },
+	{ .type =3D "serial", .compatible =3D "xlnx,xps-uart16550-2.00.b",
=2Edata =3D (void *)PORT_16550A, },
 	{ .type =3D "serial", .compatible =3D "ns16550",  .data =3D (void
*)PORT_16550, },
 	{ .type =3D "serial", .compatible =3D "ns16750",  .data =3D (void
*)PORT_16750, },
 	{ .type =3D "serial", .compatible =3D "ns16850",  .data =3D (void
*)PORT_16850, },
*************************************************************************=
*********************
IMPORTANT: The contents of this email and any attachments are confidentia=
l. They are intended for the=20
named recipient(s) only.
If you have received this email in error, please notify the system manage=
r or the sender immediately and do=20
not disclose the contents to anyone or make copies thereof.

  reply	other threads:[~2009-11-19 13:32 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 [this message]
2009-11-19 13:41         ` Arnd Bergmann
2009-11-19 13:49           ` Alon Ziv
2009-11-19 14:09             ` Arnd Bergmann
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=8B957E110B62714A84290A01A597805F05D2AE44@Exchange.discretix.com \
    --to=alonz@discretix.com \
    --cc=arnd@arndb.de \
    --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).