From: Jun Sun <jsun@mvista.com>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: "Maciej W. Rozycki" <macro@linux-mips.org>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Linux/MIPS Development <linux-mips@linux-mips.org>,
jsun@mvista.com
Subject: Re: [patch] Incorrect mapping of serial ports to lines
Date: Tue, 29 Jun 2004 17:15:37 -0700 [thread overview]
Message-ID: <20040629171537.F6498@mvista.com> (raw)
In-Reply-To: <20040629224932.GA10375@linux-mips.org>; from ralf@linux-mips.org on Wed, Jun 30, 2004 at 12:49:32AM +0200
On Wed, Jun 30, 2004 at 12:49:32AM +0200, Ralf Baechle wrote:
> On Tue, Jun 29, 2004 at 03:13:13PM -0700, Jun Sun wrote:
>
> > > > The NEC DDB Vrc-5074 (and probably the other DDB variants as well) has one
> > > > serial port in the Nile 4 host bridge, and 2 serial ports in the Super I/O.
> > > >
> > > > To me it sounds the most logical if the one in the Nile 4 is ttyS0.
> > >
> > > Then we need to find a way to make the order configurable somehow.
> >
> > This is why I favor run-time serial port configuration. My view
> > (maybe a little dramatic) is to remove all static serial port definition
> > and push them into board setup routine. asm/serial.h only needs
> > to define the number serial lines, which itself could be configurable.
>
> <asm/serial.h> is on it's way out of the kernel - it's only a question of
> time until either the current maintainer of the serial driver or somebody
> with more time at hands will eleminate it. And serial.h was always only
> meant to handle the kind of serial interfaces of which you just have to
> know that they're there because probing for it isn't possible. Something
> which these days is getting increasingly more rare thanks to PCI.
>
> What I really wouldn't like to see is the runtime registration for all
> the legacy serial stuff that possibly could be plugged into some board
> be duplicated into half a dozen of systems ...
>
No fear really. You can still provide STD_SERIAL_PORT in the asm/serial.h
where each individual board simply does a registration for each line
defined there. You might even provide some inline function for
doing so in asm/serial.h.
The big advantage of this scheme is that the board-level complexity is not
exposed to MIPS arch layer. So when it is time for a board to die, one
does not have to clean up a dozen or so common files like asm/serial.h file.
Of course it also offers complete control over the ordering of serial
ports to the board.
See arch/mips/vr4181/common/serial.c for a simple example of run-time
registeration. I believe a couple of other boards are doing this too.
Jun
prev parent reply other threads:[~2004-06-30 0:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-28 13:25 [patch] Incorrect mapping of serial ports to lines Maciej W. Rozycki
2004-06-28 23:59 ` Ralf Baechle
2004-06-29 11:57 ` Maciej W. Rozycki
2004-06-29 12:09 ` Geert Uytterhoeven
2004-06-29 13:49 ` Maciej W. Rozycki
2004-06-29 15:03 ` Ralf Baechle
2004-07-02 15:09 ` Maciej W. Rozycki
2004-06-29 22:13 ` Jun Sun
2004-06-29 22:43 ` Maciej W. Rozycki
2004-06-30 8:07 ` Geert Uytterhoeven
2004-06-30 12:10 ` Maciej W. Rozycki
2004-06-29 22:49 ` Ralf Baechle
2004-06-30 0:15 ` Jun Sun [this message]
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=20040629171537.F6498@mvista.com \
--to=jsun@mvista.com \
--cc=geert@linux-m68k.org \
--cc=linux-mips@linux-mips.org \
--cc=macro@linux-mips.org \
--cc=ralf@linux-mips.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.