From: Felipe Balbi <balbi@ti.com>
To: Javier Martinez Canillas <javier@dowhile0.org>
Cc: Sebastian Reichel <sre@kernel.org>, Felipe Balbi <balbi@ti.com>,
Robert Nelson <robertcnelson@gmail.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 12:08:22 -0500 [thread overview]
Message-ID: <20140703170822.GB5814@saruman.home> (raw)
In-Reply-To: <CABxcv=nGPyK7SeQZ+W1ZEfBPQ-RraVTawyYuKOGz02df0g=6Qg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 963 bytes --]
On Thu, Jul 03, 2014 at 06:19:47PM +0200, Javier Martinez Canillas wrote:
> On Thu, Jul 3, 2014 at 6:06 PM, Sebastian Reichel <sre@kernel.org> wrote:
> > Hi,
> >
> > On Thu, Jul 03, 2014 at 10:52:40AM -0500, Felipe Balbi wrote:
> >> > DT is supposed to contain information about the hardware, so it
> >> > should stay the same? I think there is no non-hackish way to decide
> >>
> >> compatible would change, at a minimum.
> >
> > why? I would expect it to stay the same (and the current patch uses
> > the same compatible strings).
> >
>
> Exactly, the new driver must support all the compatible strings
> defined in Documentation/devicetree/bindings/serial/omap_serial.tx
> (which already does as you pointed out).
>
> Otherwise the current drivers/tty/serial/omap-serial.c could never be
> removed since that would mean breaking DT backward compatibility.
that settles it then... good. I'll start testing this next week.
--
balbi
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-07-03 17:08 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 [this message]
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=20140703170822.GB5814@saruman.home \
--to=balbi@ti.com \
--cc=aaro.koskinen@iki.fi \
--cc=bigeasy@linutronix.de \
--cc=javier@dowhile0.org \
--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=sre@kernel.org \
--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).