On Fri, 4 Jul 2014 11:57:40 -0500
Robert Nelson [off-list ref] wrote:

On Fri, Jul 4, 2014 at 11:51 AM, Sebastian Andrzej Siewior
[off-list ref] wrote:

quoted

On 07/03/2014 09:34 AM, Tony Lindgren wrote:

quoted

Heh. Just to summarize the reason ttyO needs to be a separate name
and device entry from ttyS is because we also have external 8250
devices on GPMC and hotplug busses.

So the GPMC devices will first get a higher minor/device number. The
internal serial ports should show up first. I don't see the problem
(yet).

If you need a separate major number (and name) like we do have it now
(between ttySx and ttyOx) then one of requirements would be to tell
Kconfig that one driver can be active at a time.

For me the ttyS vs ttyO thing is purely cosmetic. I personally don't
like that it is different on different platforms like ttymxc, ttySC,
ttyTHS, ?

Maybe it's time to migrate them all to one name? (ttyS)  Does the end
user really care if they have a soc with an omap/imx serial port
driver? Or do they just want to access /dev/ttySx and connect to their
device?

Userspace question. Actual userspace visible device naming policy belongs
to udev.

Alan