[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160818154019.40f4df45@lxorguk.ukuu.org.uk>
Date: Thu, 18 Aug 2016 15:40:19 +0100
From: One Thousand Gnomes <gnomes@...rguk.ukuu.org.uk>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: "H. Nikolaus Schaller" <hns@...delico.com>,
Pavel Machek <pavel@....cz>, Rob Herring <robh@...nel.org>,
Marcel Holtmann <marcel@...tmann.org>,
Jiri Slaby <jslaby@...e.com>,
Sebastian Reichel <sre@...nel.org>,
Peter Hurley <peter@...leysoftware.com>,
NeilBrown <neil@...wn.name>, Arnd Bergmann <arnd@...db.de>,
Linus Walleij <linus.walleij@...aro.org>,
linux-bluetooth@...r.kernel.org, linux-serial@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH 0/3] UART slave device bus
On Thu, 18 Aug 2016 12:57:59 +0200
Greg Kroah-Hartman <gregkh@...uxfoundation.org> wrote:
> On Thu, Aug 18, 2016 at 12:54:15PM +0200, H. Nikolaus Schaller wrote:
> > Hi Pavel,
> >
> > > Am 18.08.2016 um 12:47 schrieb Pavel Machek <pavel@....cz>:
> > >
> > >
> > >>
> > >> Thereof 4 files, ~260 changes w/o gps demo and documentation/bindings.
> > >
> > > So what do you use for the serial devices? platform_device was vetoed
> > > for that purpose by Greg.
> >
> > device tree?
>
> No.
>
> This patchset from Rob is the way I have been saying it should be done
> for years now. Yes, a "bus" takes up more boilerplate code (blame me
> for that), but overall, it makes the drivers simpler, and fits into the
> rest of the kernel driver/device model much better.
The basic problem is that the bus should be tty_ports not uart, fix that
and the rest starts to make sense.
Alan
Powered by blists - more mailing lists