From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Kumar Gala <kumar.gala@freescale.com>, Greg KH <greg@kroah.com>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: serial8250_init and platform_device
Date: Thu, 20 Jan 2005 19:38:45 +0000 [thread overview]
Message-ID: <20050120193845.H13242@flint.arm.linux.org.uk> (raw)
In-Reply-To: <736677C2-6B16-11D9-BD44-000393DBC2E8@freescale.com>; from kumar.gala@freescale.com on Thu, Jan 20, 2005 at 01:06:55PM -0600
On Thu, Jan 20, 2005 at 01:06:55PM -0600, Kumar Gala wrote:
> Russell,
>
> I think this all makes sense to me. I'm just wondering why we would
> have a platform device register in a system for 'legacy ISA' when we
> know the system doesnt have any ports that will fit the category.
>
> As you show in example #2 you have
>
> .../devices/platform/serial82500
> .../devices/platform/serial8250
>
> why have the 'serial8250' if you know your system doesnt have any ports
> that will exist there?
In this case, it is a placeholder, and needs to be there if you're using
power management.
For instance, you may use setserial on /dev/ttyS2 to reconfigure it
to an address where you know a serial port is. Without the "serial8250"
device, it isn't linked into the device model, and therefore doesn't
receive any power management notifications.
Once the SERIAL_PORT_DFNS are gone, and we have a more modern interface
than setserial for setting up random ports, this "serial8250" device
will vanish.
While we're here, you've reminded me about an annoying point about
platform device naming...
Greg - the name is constructed from "name" + "id num" thusly:
serial8250
serial82500
serial82501
serial82502
When "name" ends in a number, it gets rather confusing. Can we have
an optional delimiter in there when we append the ID number, maybe
something like a '.' or ':' ?
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 PCMCIA - http://pcmcia.arm.linux.org.uk/
2.6 Serial core
next prev parent reply other threads:[~2005-01-20 19:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-20 7:14 serial8250_init and platform_device Kumar Gala
2005-01-20 11:43 ` Russell King
2005-01-20 15:23 ` Kumar Gala
2005-01-20 15:44 ` Russell King
2005-01-20 19:06 ` Kumar Gala
2005-01-20 19:38 ` Russell King [this message]
2005-01-20 19:50 ` Greg KH
2005-01-20 20:10 ` Russell King
2005-01-20 20:25 ` Kumar Gala
2005-02-01 8:41 ` Greg KH
2005-01-20 20:26 ` Kumar Gala
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=20050120193845.H13242@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=greg@kroah.com \
--cc=kumar.gala@freescale.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox