On Sat, Jan 7, 2017 at 5:00 AM, Andy Shevchenko <andriy.shevchenko@xxxxxxxxxxxxxxx> wrote: > On Fri, 2017-01-06 at 10:26 -0600, Rob Herring wrote: >> Here goes another attempt at a serial device bus (aka uart slaves, tty >> slaves, etc.). >> >> After some discussions with Dmitry at LPC, I decided to move away from >> extending serio and moved back to making a new bus type instead. He >> didn't >> think using serio was a good fit, and serio has a number of >> peculiarities >> in regards to sysfs and it's driver model. I don't think we want to >> inherit >> those for serial slave devices. >> >> This version sits on top of tty_port rather than uart_port as Alan >> requested. Once I created a struct tty rather than moving everything >> needed to tty_port, it became a lot easier and less invasive to the >> tty >> core code. >> >> I have hacked up versions of the BT ldisc and TI ST drivers moved over >> to >> use the serdev bus. I have BT working on the HiKey board which has TI >> BT. >> With the serdev bus support, it eliminates the need for the TI >> userspace >> UIM daemon. >> >> This series and the mentioned drivers can be found here[1]. > > For patches 1-4: > Reviewed-by: Andy Shevchenko <andriy.shevchenko@xxxxxxxxxxxxxxx> Thanks. > Regarding to naming. Why can't we just name bus "serial"? If you are > worrying about folder name under drivers/tty, I can propose at lease > couple of options serialdev, serialbus. Naming is hard, right? I have don't have too much opinion on what the name should be. I just came up with something unique and inspired by serio. It is a bit easier to grep for serdev rather than just serial. Rob -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
