Return-Path: Date: Mon, 6 Jan 2014 01:27:55 +0100 From: Pavel Machek To: Marcel Holtmann , Pali =?iso-8859-1?Q?Roh=E1r?= , =?utf-8?B?0JjQstCw0LnQu9C+INCU0LjQvNC40YLRgNC+0LI=?= , "Gustavo F. Padovan" , Johan Hedberg , linux-kernel , "linux-bluetooth@vger.kernel.org development" , Ville Tervo Subject: Re: [PATCH v4] Bluetooth: Add hci_h4p driver Message-ID: <20140106002755.GC27517@amd.pavel.ucw.cz> References: <1379703710-5757-1-git-send-email-pali.rohar@gmail.com> <1727897.LBX8128hIo@izba> <20140102161824.GA8204@amd.pavel.ucw.cz> <20140103001753.GA21023@amd.pavel.ucw.cz> <20140103010519.GA27678@earth.universe> <20140105223250.GB27517@amd.pavel.ucw.cz> <20140105230155.GA2681@earth.universe> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <20140105230155.GA2681@earth.universe> List-ID: > > > The drivers can still be initialized the old way using pdata quirks > > > until all drivers are converted, but I think this driver can simply > > > be prepared for DT directly: > > > > Well, normally DT support means a bit of argumentation and bikeshed > > painting... I believe it would be better to get the driver in as-is > > and then work on adding DT support. > > Maybe. Especially the UART reference may result in some discussion. > But having the discussion early means its finished earlier :) Well, merging the basic driver does not mean discussion can't start early. If it is going to be complex, that's a very good reason to do it in separate step. That is, have a working driver, then add device tree support. Thanks, Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html