[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <554A03A7.2000504@hurleysoftware.com>
Date: Wed, 06 May 2015 08:05:59 -0400
From: Peter Hurley <peter@...leysoftware.com>
To: "Dr. H. Nikolaus Schaller" <hns@...delico.com>,
Pavel Machek <pavel@....cz>
CC: List for communicating with real GTA04 owners
<gta04-owner@...delico.com>, NeilBrown <neil@...wn.name>,
Mark Rutland <mark.rutland@....com>,
One Thousand Gnomes <gnomes@...rguk.ukuu.org.uk>,
Arnd Bergmann <arnd@...db.de>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Sebastian Reichel <sre@...nel.org>,
Grant Likely <grant.likely@...aro.org>,
Jiri Slaby <jslaby@...e.cz>, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [Gta04-owner] [PATCH 0/3] tty slave device support - version
3.
On 05/06/2015 07:50 AM, Dr. H. Nikolaus Schaller wrote:
> No, I am not playing devil’s advocate (which would imply that I am doing this
> for fun to tease the dog), but I feel I have to be the advocate of future board
> designers who want to easily import an existing board DT and overwrite device
> tree nodes to describe design changes, i.e. what slave device is connected to
> which uart.
I dont' see a big distinction at the DTS source level, so your concern is wrt
binary dtbs?
> At least in this regard, the alternatives are really differently easy to handle.
>
> And, the alternatives have some influence how a tty driver and a slave device
> driver is designed. So that is for me the root question, before discussing (some)
> implementation details.
I would expect _no_ impact on the tty driver; have I overlooked something?
Regards,
Peter Hurley
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists