Return-Path: Date: Mon, 22 Aug 2016 22:32:23 +0100 From: One Thousand Gnomes To: Marcel Holtmann Cc: Rob Herring , Arnd Bergmann , Greg Kroah-Hartman , Jiri Slaby , Sebastian Reichel , Pavel Machek , Peter Hurley , NeilBrown , "Dr . H . Nikolaus Schaller" , Linus Walleij , "open list:BLUETOOTH DRIVERS" , "linux-serial@vger.kernel.org" , "linux-kernel@vger.kernel.org" Subject: Re: [RFC PATCH 0/3] UART slave device bus Message-ID: <20160822223223.398ee72d@lxorguk.ukuu.org.uk> In-Reply-To: <2D07EA08-1055-4292-96B3-32913EC9BBE1@holtmann.org> References: <20160818011445.22726-1-robh@kernel.org> <12886761.WF058qtZp8@wuerfel> <2775954.hrE2UdODgU@wuerfel> <20160822180254.5c95af7c@lxorguk.ukuu.org.uk> <20160822183849.6dfdb9d2@lxorguk.ukuu.org.uk> <2D07EA08-1055-4292-96B3-32913EC9BBE1@holtmann.org> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII List-ID: > why would we even have it create a /dev/ttyX for these devices in the first place. Lets just not create an uevent for it and lets not create a dev_t for it. Because if you don't it's a regression. It's not permissible to break existing userspace. > Internally the setup stage does a hciconfig hci0 up and it is already abstracted out that way. So there has been a lot of work in the Bluetooth subsystem to allow for this. That part is really solved. So you'd create a kernel side tty struct and bind it to the tty_port on hci0 up and drop it on hci0 down ? Alan