From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S964814AbcATUJr (ORCPT ); Wed, 20 Jan 2016 15:09:47 -0500 Received: from mail-lb0-f172.google.com ([209.85.217.172]:34833 "EHLO mail-lb0-f172.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752784AbcATUJp (ORCPT ); Wed, 20 Jan 2016 15:09:45 -0500 Date: Wed, 20 Jan 2016 23:09:39 +0300 From: Vostrikov Andrey Reply-To: Vostrikov Andrey Organization: Cogent Embedded X-Priority: 3 (Normal) Message-ID: <691920039.20160120230939@cogentembedded.com> To: Dmitry Torokhov CC: Rob Herring , Peter Hurley , "H. Nikolaus Schaller" , Mark Rutland , List for communicating with real GTA04 owners , Tomeu Vizoso , NeilBrown , One Thousand Gnomes , Arnd Bergmann , "devicetree@vger.kernel.org" , Greg Kroah-Hartman , Sebastian Reichel , "linux-kernel@vger.kernel.org" , Pavel Machek , "linux-serial@vger.kernel.org" , Grant Likely , Jiri Slaby , Marek Belisko Subject: Re: [Gta04-owner] [PATCH 0/4] UART slave device support - version 4 In-Reply-To: References: <20150511013540.5709.93626.stgit@notabene.brown> <481E05A9-A192-438D-B092-D7700B30BBC4@goldelico.com> <20160113191542.GA12086@leverpostej> <1CD6CA14-AE4F-444F-A9A2-CF9B9485F2DC@goldelico.com> <20160115110106.GA3262@leverpostej> <69F8E1E5-EF49-4C8E-88E9-973F82F7102E@goldelico.com> <569913A1.80606@cogentembedded.com> <56992959.2020204@hurleysoftware.com> <744620565.20160116103445@cogentembedded.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, Dmitry. > On Fri, Jan 15, 2016 at 11:34 PM, Vostrikov Andrey > wrote: >> >> Yes, such implementation will help. There is a need for interface like UART BUS that will probe devices without user space. >> Serial I/O for input subsystem defines new type of bus and uses dedicated line discipline, but it still unable to start driver by itself and requires call from 'inputattach' to open port, assign line discipline and go to forever wait on 'read'. > That was done mainly because almost none of the serial protocols could > be auto-probed, so device initialization/setup was moved out of kernel > and thus we have the separate line discipline and inputattach utility. This is understandable for "dummy" devices like mice, that only report input events. But in case there is "intellectual" MCU, that must reply on specific commands with specific response - it could be auto-probed. Especially when it is hardwired. Unfortunately, there is no API to do it. Opening port and attaching line discipline from kernel side does not look good. The only example is '/dev/console', which is implemented that way. > Thanks. -- Best regards, Andrey Vostrikov