> - Introduce a new ldisc called N_H4_COMBO with a ldisc driver > accordingly that will be placed under drivers/char That seems sensible. That code should also be entirely hardware independent. > solution more complex than actually needed. We think that creating a > new ldisc creates a cleaner solution. It will to some extent remind of > hci_ldisc, but it will not register to any framework except tty. Ok. So presumably both the SPI and the tty interfaces would then use the same library code to do the demux - or are the protocols different ? > We've thought about if we should switch cg2900 to a bus, but after > discussing this we feel that CG2900 has such individual > characteristics that it could be hard to create a bus that would suite > it. We therefore will keep the MFD type. We might in the future add > new chips to the driver, but they will most likely not require so much > rework of the driver that we will have to create something completely > new. We will rather create a lib file that contains common code to > reduce total code size of the driver. No particular opinion either way. Whatever works best and keeps it modular. -- 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
