[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAL_JsqKRqKJmPc-QQBcN9j5=_y+MH+Rn1aZNun=MAgBMpvDL2w@mail.gmail.com>
Date: Tue, 29 May 2018 10:38:09 -0500
From: Rob Herring <robh@...nel.org>
To: Ricardo Ribalda Delgado <ricardo.ribalda@...il.com>
Cc: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"open list:SERIAL DRIVERS" <linux-serial@...r.kernel.org>,
Johan Hovold <johan@...nel.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Jiri Slaby <jslaby@...e.com>
Subject: Re: [PATCH 07/19] serdev: Allows dynamic creation of devices via sysfs
On Tue, May 29, 2018 at 8:10 AM, Ricardo Ribalda Delgado
<ricardo.ribalda@...il.com> wrote:
> Allow creating and deleting devices via sysfs. Devices created will be
> matched to serdev drivers via modalias (the string provided by the user)
> and deleted via their name. Eg:
>
> # Create device
> root@...022:~# echo ttydev > /sys/bus/serial/devices/serial0/new_device
>
> # Delete device
> root@...022:~#
> echo serial0-0 > /sys/bus/serial/devices/serial0/delete_device
I think the model here should be the kernel provides dummy slave
device for each serial port and then you can use bind and unbind to
bind to a particular driver.
Rob
Powered by blists - more mailing lists