From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Kars de Jong <jongk@linux-m68k.org>
Cc: Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: 8250_hp300: initialisation ordering bug
Date: Wed, 7 Sep 2005 21:33:16 +0100 [thread overview]
Message-ID: <20050907213316.G19199@flint.arm.linux.org.uk> (raw)
In-Reply-To: <1126124269.3968.5.camel@kars.perseus.home>; from jongk@linux-m68k.org on Wed, Sep 07, 2005 at 10:17:49PM +0200
On Wed, Sep 07, 2005 at 10:17:49PM +0200, Kars de Jong wrote:
> Yes, you are right. I am working on rewriting the driver a bit to use a
> platform device for the APCI driver, I'll take your bug report into
> account as well.
Thanks.
> On a related note: can I use the "serial8250" platform driver also for
> non-ISA devices (like my APCI platform device)? The comments in
> drivers/serial/8250.c suggest it's for ISA devices only, but I don't see
> a particular reason for not using it for my APCI devices.
The legacy platform device (serial8250_isa_devs) is for the old
legacy ISA tables, found in include/asm-*/serial.h.
Other serial8250 platform devices can be used to register other
devices - preferably groups of platform specific serial ports.
However, if you're talking about registering a set of devices
found on a different bus type (eg, PCI) then look at how 8250_pci
handles that. I'd prefer bus-specific device registration to be
done in a similar way to 8250_pci rather than creating extra
platform devices.
I hope that's clear.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 Serial core
next prev parent reply other threads:[~2005-09-07 20:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-04 10:19 8250_hp300: initialisation ordering bug Russell King
2005-09-07 20:17 ` Kars de Jong
2005-09-07 20:33 ` Russell King [this message]
2005-09-08 19:42 ` Kars de Jong
2005-09-08 19:45 ` Russell King
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=20050907213316.G19199@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=jongk@linux-m68k.org \
--cc=linux-kernel@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 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.