On Mon, Oct 31, 2016 at 10:40 PM, Rob Herring <robh@xxxxxxxxxx> wrote: > On Mon, Oct 31, 2016 at 3:00 PM, Peter Hurley <peter@xxxxxxxxxxxxxxxxxx> wrote: >> On Tue, Oct 25, 2016 at 4:02 PM, Rob Herring <robh@xxxxxxxxxx> wrote: >>> >>> > Maybe you can try to find some minutes at the Kernel Summit to talk >>> > about this? >>> >>> Still waiting for my invite... >>> >>> But I will be at Plumbers if folks want to discuss this. >> >> >> Hey Rob, >> >> I'm here so let's make time to discuss this. > > Tomorrow should be good for me after the complex device dependencies discussion. I have a somewhat working branch using ttyport and serio here[1]. It works with a BT device to the level the device works with my PC which is only identifying the BCM device and loading the firmware. I'm still not sure using serio really buys us much. We probably want to hide some of the sysfs files when using DT binding. It also provides a file to reconnect devices. I suppose this is because there is typically no hotplug detection on PS/2 ports? Serio also provides its own async binding mechanism. Perhaps this can be updated to use async probing? The registration of serio ports is a bit problematic. I had the tty port registration call into the serio ttyport driver to register, but this broke serio working as a module. While serial drivers can be modules, the tty_port code is always built-in. So the serio ttyport driver will request a callback for all tty ports when the serio driver is loaded. This means any tty driver hotplugged after serio will not be registered with serio. The only other solution I see is serio would have to be built-in. Rob [1] git://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git serio-tty-slave -- 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
