linux-serial.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Tony Lindgren <tony@atomide.com>,
	Robert Nelson <robertcnelson@gmail.com>
Cc: Aaro Koskinen <aaro.koskinen@iki.fi>, Felipe Balbi <balbi@ti.com>,
	linux kernel <linux-kernel@vger.kernel.org>,
	linux-serial@vger.kernel.org,
	Linux OMAP Mailing List <linux-omap@vger.kernel.org>,
	Linux ARM Kernel Mailing List
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [RFC PATCH] tty: serial: Add 8250-core based omap driver
Date: Fri, 04 Jul 2014 18:51:00 +0200	[thread overview]
Message-ID: <53B6DB74.2050401@linutronix.de> (raw)
In-Reply-To: <20140703073411.GX28884@atomide.com>

On 07/03/2014 09:34 AM, Tony Lindgren wrote:
> 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, …

I understand that it is easier to have a specific name for it so one
does not need to find out which node is which (but then there is udev
which could create unique device names based on attributes). And then
you need enter this thingy to securetty & inittab.

That said I am easy on it. Whatever the majority here decides to be a
sane solution I will try to make it happen.

> 
> Regards,
> 
> Tony
> 

Sebastian

  parent reply	other threads:[~2014-07-04 16:51 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-02 16:00 [RFC PATCH] tty: serial: Add 8250-core based omap driver Sebastian Andrzej Siewior
2014-07-02 16:09 ` Felipe Balbi
2014-07-02 19:09   ` Aaro Koskinen
2014-07-02 19:25     ` Robert Nelson
2014-07-03  7:34       ` Tony Lindgren
2014-07-03 13:25         ` Felipe Balbi
2014-07-03 13:34           ` Robert Nelson
2014-07-03 14:07             ` Felipe Balbi
2014-07-03 15:44               ` Sebastian Reichel
2014-07-03 15:52                 ` Felipe Balbi
2014-07-03 16:06                   ` Sebastian Reichel
2014-07-03 16:19                     ` Javier Martinez Canillas
2014-07-03 17:08                       ` Felipe Balbi
2014-07-04  6:30                         ` Tony Lindgren
2014-07-04 16:51         ` Sebastian Andrzej Siewior [this message]
2014-07-04 16:57           ` Robert Nelson
2014-07-07  7:26             ` Tony Lindgren
2014-07-07 13:26             ` One Thousand Gnomes
2014-07-04 16:59     ` Peter Maydell
2014-07-03 18:48 ` Lennart Sorensen
2014-07-04 18:13   ` Lennart Sorensen
2014-07-08 16:46     ` Sebastian Andrzej Siewior
2014-07-08 17:24       ` Lennart Sorensen

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=53B6DB74.2050401@linutronix.de \
    --to=bigeasy@linutronix.de \
    --cc=aaro.koskinen@iki.fi \
    --cc=balbi@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=robertcnelson@gmail.com \
    --cc=tony@atomide.com \
    /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;
as well as URLs for NNTP newsgroup(s).