From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752082AbcAOPnf (ORCPT ); Fri, 15 Jan 2016 10:43:35 -0500 Received: from mail-lb0-f175.google.com ([209.85.217.175]:36206 "EHLO mail-lb0-f175.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750907AbcAOPnd (ORCPT ); Fri, 15 Jan 2016 10:43:33 -0500 Subject: Re: [Gta04-owner] [PATCH 0/4] UART slave device support - version 4 To: "H. Nikolaus Schaller" , Mark Rutland Cc: List for communicating with real GTA04 owners , tomeu@tomeuvizoso.net, NeilBrown , One Thousand Gnomes , Peter Hurley , Arnd Bergmann , "devicetree@vger.kernel.org" , Greg Kroah-Hartman , Sebastian Reichel , "linux-kernel@vger.kernel.org" , Rob Herring , Pavel Machek , linux-serial@vger.kernel.org, Grant Likely , Jiri Slaby , Marek Belisko 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> From: Andrey Vostrikov Organization: Cogent Embedded Message-ID: <569913A1.80606@cogentembedded.com> Date: Fri, 15 Jan 2016 18:43:29 +0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:42.0) Gecko/20100101 Firefox/42.0 SeaMonkey/2.39 MIME-Version: 1.0 In-Reply-To: <69F8E1E5-EF49-4C8E-88E9-973F82F7102E@goldelico.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Nikolaus, H. Nikolaus Schaller wrote: > And IMHO nobody has described that he/she needs a solution to model the*data* relationship > for devices connected behind a tty port. I am not sure if my case fits *data* relationship or not in this case. Some time ago I asked about state of your patches. In my case I have supervising microcontroller unit (MCU) that is connected to one of UARTs on SoC. This MCU implements several functions that will be implemented as MFD driver: - watchdog and system reset - NVMEM EEPROM - HWMON sensors - Input/power button - and similar low level functions So in my case DTS binding looks like: &uart3 { mcu { line-speed = ; watchdog { timeout = ; ...other params... }; eeprom { #address-cells #size-cells cell1 : cell@1 { reg = <1 2>; }; cell2 : cell@2 { reg = <2 1>; }; }; hwmon { sensors-list = "voltage", "current", etc...; } } } This MCU receives commands and notifies MFD driver about events via UART protocol. It looks like not really a slave though, more like a partnership from data flow point of view. There is no user space code involved in this case as whole interactions are between drivers (just a kick to open /dev/ttyXXX using sys_open, as there is no way to start probe on uart_slave bus and assign line discipline). Best regards, Andrey