Using the right address for Wolfram On Tue, May 29, 2018 at 6:30 PM Ricardo Ribalda Delgado < ricardo.ribalda@xxxxxxxxx> wrote: > Hi Rob > On Tue, May 29, 2018 at 5:38 PM Rob Herring <robh@xxxxxxxxxx> wrote: > > On Tue, May 29, 2018 at 8:10 AM, Ricardo Ribalda Delgado > > <ricardo.ribalda@xxxxxxxxx> 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@qt5022:~# echo ttydev > /sys/bus/serial/devices/serial0/new_device > > > > > > # Delete device > > > root@qt5022:~# > > > 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. > I have been researching a bit that approach, but I found a couple of issues: > - With the bind/unbind you need to modprobe manually the module. Something > like > modprobe myserdev > echo myserdev > bind > - You need one module per part_number, with modalias you can have a > different alias per module > - I guess that the final user will appreciate that the serdev has the same > API as other serial slow bus (i2c). > ccing Wolfram becase maybe he has some feedback to same from his experience > with the i2c bus. > Thanks! > > Rob > -- > Ricardo Ribalda -- Ricardo Ribalda -- To unsubscribe from this list: send the line "unsubscribe linux-serial" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
