From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] serial: 8250: Make ISA ports optional
Date: Thu, 08 Jan 2015 23:05:12 +0100 [thread overview]
Message-ID: <1896224.oMI8M6J5T7@wuerfel> (raw)
In-Reply-To: <54AEAC47.1040403@hurleysoftware.com>
On Thursday 08 January 2015 11:11:51 Peter Hurley wrote:
>
> This interface is just storage and minor allocation, since the
> port-reuse behavior will be limited to the "universal" driver.
> From a sub-driver perspective, the shared storage is actually
> a hindrance, so that reduces the requirement to minor allocation.
>
> And that's where I'm stuck at the moment -- how to share ttyS
> minor allocation. ttyS console is a related problem.
One idea that has come up in the past but never saw an implementation
is to make the ttyS namespace and minor numbers completely generic and
let any serial port driver use it. This would be a major rework, but
have the added advantage of cleaning up a number of other namespace
issues as well. There also lots of open question, in particular how
to maintain compatibility with existing drivers. One could imagine
that each uart always gets a ttyS device and optionally also gets
a device node for the same port with a driver specific chardev as
most of them do today. Or it could be an either/or decision that is
made at compile time or as a module parameter.
Arnd
next prev parent reply other threads:[~2015-01-08 22:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-06 3:09 [PATCH] serial: 8250: Make ISA ports optional Peter Hurley
2015-01-06 13:13 ` Arnd Bergmann
2015-01-06 14:32 ` Peter Hurley
2015-01-06 19:43 ` Arnd Bergmann
2015-01-06 21:47 ` Peter Hurley
2015-01-07 10:05 ` Arnd Bergmann
2015-01-08 13:10 ` One Thousand Gnomes
2015-01-08 16:11 ` Peter Hurley
2015-01-08 22:05 ` Arnd Bergmann [this message]
2015-01-08 22:36 ` One Thousand Gnomes
2015-01-08 23:25 ` Peter Hurley
2015-01-09 5:13 ` Peter Hurley
2015-01-09 8:48 ` Arnd Bergmann
2015-01-09 14:14 ` Peter Hurley
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=1896224.oMI8M6J5T7@wuerfel \
--to=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.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