From mboxrd@z Thu Jan 1 00:00:00 1970 From: tony@atomide.com (Tony Lindgren) Date: Thu, 3 Jul 2014 23:30:10 -0700 Subject: [RFC PATCH] tty: serial: Add 8250-core based omap driver In-Reply-To: <20140703170822.GB5814@saruman.home> References: <20140703073411.GX28884@atomide.com> <20140703132509.GA5814@saruman.home> <20140703140736.GF5814@saruman.home> <20140703154425.GC23309@earth.universe> <20140703155240.GU5814@saruman.home> <20140703160622.GE23309@earth.universe> <20140703170822.GB5814@saruman.home> Message-ID: <20140704063010.GY28884@atomide.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org * Felipe Balbi [140703 10:10]: > 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 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. Yeah full compability is the way to go here. FYI we cannot switch over completely until runtime PM works as it will block the deeper idle states for omaps and make it impossible to debug PM features. Regards, Tony