On 21/07/17 12:27, Marcel Holtmann wrote: >> A far better approach would be to teach ACPI platforms how to chreate >> their own serdev devices. > > I agree that ACPI and even pure platform devices should create serdev nodes. Then my driver will work as is (if the irq/sleep dt entries are implemented. I can do a respin with these added, and it can use the same DT labels as the Nokia driver does. No need for modifying the old driver at all. >> Platforms with zero hardware info available should NOT be using serdev. > > Actually there will be development hardware that comes via USB-TTY converters > and we need to make this work somehow. I am not going to write two drivers for > each hardware in the future. And we are using development boards often for > hardware testing and bringup. That should work. I havent looked, but it seems to me that all we need to do is allow serial port drivers to register a DT structure for the BT subdevice attached to them when they probe, if such a function doesnt already exist. I dont see what other glue we would need - perhaps the USB ones might need a callback to allow them to send USB packets to control the wakeup lines etc. -Ian -- 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
