Hi Fred, > > I am debating to actually call this SBC_FLAG_MSBC instead of just > > SBC_MSBC. Anyone any comments? > > The use of the flag may not be the most elegant API. As an alternative, > maybe we could have a specific function for msbc initialization. Then, > instead of sbc_init(), sbc_encode() sbc_decode(), we could have > msbc_init(), sbc_encode(), sbc_decode(). > The biggest advantage is that parameters like bitpool, subbands, > allocation, and other parts could be specified inside this function > instead of being given from the application. we could do an sbc_init_msbc() function. As this is the only real external visible API change, we need to be 100% sure with this one. 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
