Return-Path: Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: [RFC PATCH 0/3] UART slave device bus From: "H. Nikolaus Schaller" In-Reply-To: <20160820143405.04303834@lxorguk.ukuu.org.uk> Date: Sun, 21 Aug 2016 09:50:57 +0200 Cc: Oleksij Rempel , Sebastian Reichel , Rob Herring , Greg Kroah-Hartman , Marcel Holtmann , Jiri Slaby , Pavel Machek , Peter Hurley , NeilBrown , Arnd Bergmann , Linus Walleij , "open list:BLUETOOTH DRIVERS" , "linux-serial@vger.kernel.org" , "linux-kernel@vger.kernel.org" Message-Id: References: <20160818011445.22726-1-robh@kernel.org> <20160818202900.hyvm4hfxedifuefn@earth> <20160819052125.ze5zilppwoe3f2lx@earth> <53A846F1-33E5-48C3-B3A6-DB251661CDD5@goldelico.com> <20160820143405.04303834@lxorguk.ukuu.org.uk> To: One Thousand Gnomes Sender: linux-serial-owner@vger.kernel.org List-ID: > Am 20.08.2016 um 15:34 schrieb One Thousand Gnomes = : >> What it is not about are UART/RS232 converters connected through USB = or virtual >> serial ports created for WWAN modems (e.g. /dev/ttyACM, /dev/ttyHSO). = Or BT devices >> connected through USB (even if they also run HCI protocol). >=20 > It actually has to be about both because you will find the exact same > device wired via USB SSIC/HSIC to a USB UART or via a classic UART. = Not is > it just about embedded boards.=20 Not necessarily. We often have two interface options for exactly the sam sensor chips. = They can be connected either through SPI or I2C. Which means that there is a core driver for = the chip and two different transport glue components (see e.g. iio/accel/bmc150). This does not require I2C to be able to handle SPI or vice versa or = provide a common API. And most Bluetooth devices I know have either UART or a direct USB = interface. So in the USB case there is no need to connect it through some USB-UART bridge and = treat it as an UART at all. BR, Nikolaus