From: David Gibson <david@gibson.dropbear.id.au>
To: Josh Boyer <jwboyer@gmail.com>
Cc: linuxppc-dev@ozlabs.org, paulus@samba.org,
John Linn <john.linn@xilinx.com>, Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH 2/3] [POWERPC][V3] Xilinx: of_serial support for Xilinx uart 16550.
Date: Tue, 8 Apr 2008 12:44:40 +1000 [thread overview]
Message-ID: <20080408024440.GB17820@localhost.localdomain> (raw)
In-Reply-To: <1207406756.6809.2.camel@vader.jdub.homelinux.org>
On Sat, Apr 05, 2008 at 09:45:56AM -0500, Josh Boyer wrote:
> On Thu, 2008-04-03 at 06:16 +0200, Arnd Bergmann wrote:
> > On Thursday 03 April 2008, Grant Likely wrote:
> > > >
> > > > Since it is not really compatible with ns16550, shouldn't you at least specify
> > > > a different "compatible" property? That way, the driver won't do incorrect
> > > > accesses when you try to use an old driver with a device tree that specifies
> > > > one of these.
> > >
> > > Heh; we've gone back and forth on this issue. The problem is that we
> > > have a common case of ns16550 like devices that require a little bit
> > > of register address tweaking that spans a whole range of vendors (so
> > > adding a compatible match with each of those vendor's prefixes is
> > > probably non-scalable). So, if "ns16550" is not a good idea, then
> > > what should be used? "sparse16550" has been suggested more than once.
> >
> > After another IRC discussion between Grant, Segher and myself, we concluded
> > that we don't need to invent a new "compatible" value, as only new device
> > trees with old kernels will have a problem with this, and they don't work
> > in the first place.
> >
> > The devices will still have their specific "compatible" value, e.g.
> > "xlnx,plb-uart16550-1.00.c", followed by "ns16550", and possibly
> > "ns16450" and "i8250", although the last two do not have an effect
> > on Linux.
> >
> > Josh, can you please forward all three patches in their latest version?
> >
> > Acked-by: Arnd Bergmann <arnd@arndb.de>
>
> So is the discussion on reg-offset settled then? It seemed Paul and
> David had some issues with that, and I'd like to make sure everyone is
> agreed on that before I bring in patches 2 and 3.
I didn't like it very much, but I don't really care enough to argue
about it.
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
next prev parent reply other threads:[~2008-04-08 2:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-02 23:22 [PATCH 2/3] [POWERPC][V3] Xilinx: of_serial support for Xilinx uart 16550 John Linn
2008-04-02 23:34 ` Arnd Bergmann
2008-04-03 2:43 ` Grant Likely
2008-04-03 4:16 ` Arnd Bergmann
2008-04-03 13:29 ` John Linn
2008-04-03 22:36 ` [PATCH 2/3] [POWERPC][V3] Xilinx: of_serial support for Xilinxuart 16550 Stephen Neuendorffer
2008-04-05 14:45 ` [PATCH 2/3] [POWERPC][V3] Xilinx: of_serial support for Xilinx uart 16550 Josh Boyer
2008-04-08 2:44 ` David Gibson [this message]
2008-04-03 12:25 ` Sergei Shtylyov
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=20080408024440.GB17820@localhost.localdomain \
--to=david@gibson.dropbear.id.au \
--cc=arnd@arndb.de \
--cc=john.linn@xilinx.com \
--cc=jwboyer@gmail.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.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).