From: Felipe Balbi <balbi@ti.com>
To: Robert Nelson <robertcnelson@gmail.com>
Cc: Felipe Balbi <balbi@ti.com>, Tony Lindgren <tony@atomide.com>,
Aaro Koskinen <aaro.koskinen@iki.fi>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
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: Thu, 3 Jul 2014 09:07:36 -0500 [thread overview]
Message-ID: <20140703140736.GF5814@saruman.home> (raw)
In-Reply-To: <CAOCHtYi0JwRO12gHa+KFGH1k7pPk4TL40igwhzRRxutw-tqf6A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1984 bytes --]
On Thu, Jul 03, 2014 at 08:34:44AM -0500, Robert Nelson wrote:
> On Thu, Jul 3, 2014 at 8:25 AM, Felipe Balbi <balbi@ti.com> wrote:
> > On Thu, Jul 03, 2014 at 12:34:11AM -0700, Tony Lindgren wrote:
> >> * Robert Nelson <robertcnelson@gmail.com> [140702 12:27]:
> >> > On Wed, Jul 2, 2014 at 2:09 PM, Aaro Koskinen <aaro.koskinen@iki.fi> wrote:
> >> > > Hi,
> >> > >
> >> > > On Wed, Jul 02, 2014 at 11:09:32AM -0500, Felipe Balbi wrote:
> >> > >> > It has been only tested as console UART.
> >> > >> > The tty name is ttyS based instead of ttyO. How big is the pain here,
> >> > >> > what could be the easiest way to provide compatibility?
> >> > >>
> >> > >> have been considering that myself for months. You could pass an optional
> >> > >> argument to serial8250_register_8250_port() but that only solves part of
> >> > >> the problem :-(
> >>
> >> Some kind of compability layer sure would be nice.
> >>
> >> > > When ttyS -> ttyO change was done on OMAP, compatibility was not an issue.
> >> > > Why should we care about it now?
> >> >
> >> > It would be a good opportunity to force everyone to update their bootloader. ;)
> >> >
> >> > Besides the BeagleBoard forum is quiet now, no one is complaining
> >> > about that old (ttyS -> ttyO) transition anymore..
> >>
> >> How about a Kconfig option to provide ttyO by default? The not even
> >> do that if kernel has cmdline option nottyomap.
> >
> > what about single zImage ? I don't want to use ttyO on my
> > Allwinner/Exynos/Snapdragon/whatever SoC just because OMAP is in the
> > same image ;-)
>
> What if we just kept it simple, leave the ttyO driver enabled and add
> a warning (pr_info) that it's deprecated. It's not like it's broken,
> it just won't get later features or devices support added.
Fine by me, I'd switch to 8250 as soon as it's merged though :-) would
be nice to get an example DTS change just so I can start testing on the
boards I have around.
--
balbi
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-07-03 14:07 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 [this message]
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
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=20140703140736.GF5814@saruman.home \
--to=balbi@ti.com \
--cc=aaro.koskinen@iki.fi \
--cc=bigeasy@linutronix.de \
--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).