[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <554B86D5.8080403@hurleysoftware.com>
Date: Thu, 07 May 2015 11:37:57 -0400
From: Peter Hurley <peter@...leysoftware.com>
To: "Dr. H. Nikolaus Schaller" <hns@...delico.com>,
Mark Rutland <mark.rutland@....com>
CC: Pavel Machek <pavel@....cz>,
List for communicating with real GTA04 owners
<gta04-owner@...delico.com>, NeilBrown <neil@...wn.name>,
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@...aro.org" <grant.likely@...aro.org>,
Jiri Slaby <jslaby@...e.cz>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
"linux-kernel@...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 09:28 AM, Dr. H. Nikolaus Schaller wrote:
> The key point appears to be how we want to see the serial connection. Is the
> device connected to the uart or the uart to a device?
>
> In OO terminology: „device connects to uart“ vs. „uart has device connected“.
> "d -> u“ vs. "u <- d“.
This is not a very good analogy because both relationships need to be
represented.
The practical consideration is the lifetime of the target device.
If the target device should/must have a lifetime (as viewed from the host)
outside that of the uart, then the target device should not be a slave device.
Object lifetime is controlled by expressions of ownership or scope.
Since devicetree offers no expression of ownership, scope is the
obvious and natural way to control lifetime.
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