Hi Arnd, >>> My impression is that there is some overlap in what you want >>> to do here, and what serio does today as a line discipline on top >>> of a tty line discipline (and on top of other non-uart serial >>> connections), so we should look into whether the two can be unified >>> or not. Here is what I found so far: >>> >>> For all I can tell, serio is only used for drivers/input/ but could >>> easily be extended to other subsystems. It currently uses its own >>> binary ID matching between drivers and devices through user space >>> interfaces, though adding a DT binding for it would appear to be >>> a good idea regardless. >>> >>> It also has a bus_type already, and with some operations defined on >>> it. In particular, it has an "interrupt" method that is used to >>> notify the client driver when a byte is available (and pass >>> that byte along with it). This seems to be a useful addition to >>> what you have. Since it is based on sending single characters >>> both ways, transferring large amounts of data would be slower, >>> but the interface is somewhat simpler. In principle, both >>> character based and buffer based interfaces could coexist here >>> as they do in some other interfaces (e.g. smbus). >> >> Given that about the only things it really provided are the bus_type >> and associated boilerplate without much of a client interface, it >> seemed to me that creating a new subsystem first made more sense. Then >> we can convert serio to use the new subsystem. > > One possible downside of merging later is that we end up having to > support the existing user space ABI for serio that may not fit well > within whatever we come up with independently. if we need any kind of userspace ABI to setup of Bluetooth over UART devices, then we have failed. We want that the special UARTs are identified via ACPI or DT and become an enumeratable bus. So we can attach a driver to it. Regards Marcel -- 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
