Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752315AbbEGO5D (ORCPT ); Thu, 7 May 2015 10:57:03 -0400 Received: from mail-qg0-f53.google.com ([209.85.192.53]:32993 "EHLO mail-qg0-f53.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751650AbbEGO47 (ORCPT ); Thu, 7 May 2015 10:56:59 -0400 Message-ID: <554B7D33.602@hurleysoftware.com> Date: Thu, 07 May 2015 10:56:51 -0400 From: Peter Hurley User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0 MIME-Version: 1.0 To: "Dr. H. Nikolaus Schaller" , Mark Rutland CC: Pavel Machek , List for communicating with real GTA04 owners , NeilBrown , One Thousand Gnomes , Arnd Bergmann , Greg Kroah-Hartman , Sebastian Reichel , "grant.likely@linaro.org" , Jiri Slaby , "devicetree@vger.kernel.org" , "linux-kernel@vger.kernel.org" Subject: Re: [Gta04-owner] [PATCH 0/3] tty slave device support - version 3. References: <55492001.30806@hurleysoftware.com> <20150506092738.GB4508@amd> <554A03A7.2000504@hurleysoftware.com> <20150506123632.GA1764@leverpostej> <20150506141547.GB1764@leverpostej> <20150506171802.GE2974@leverpostej> In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1662 Lines: 36 On 05/07/2015 08:46 AM, Dr. H. Nikolaus Schaller wrote: > So I don’t think that being able to control the slave is a common property > of all UART-slave connections. > > BTW: the GPS chip we use is doing something without any instructions. It starts > to send NMEA records right after power on. It would even be useful with a unidirectional > connection from GPS to UART. Hence there are no commands that need to be > sent through UART. Rather it just needs some GPIO to be activated or powered down > when /dev/tty is opened/closed. In this example, the GPIO is a workaround for the lack of DTR. > So one could argue that in this real case (which we try to solve in an acceptable way > since 2 years) the fundamental/main interface (control command interface) of this chip > is the power on/off line. And UART isn’t involved at all. Or just as an “activity detector”. The indirect nature of control in this case only reflects the workaround, not the underlying concept. Control is still derived from the UART status. Both devicetree and tty/serial can already represent independent control; what is proposed is a way to express dependent control, and in all cases, that control stems directly from either the UART state itself or via commands sent over that interface. Any target not requiring UART involvement doesn't (and probably, shouldn't) be expressed as a slave device. Regards, Peter Hurley -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/