On Mon, Feb 07, 2011 at 11:55:22PM +0100, Lars-Peter Clausen wrote:
I did some research on the topic and it seems that this is a pretty common setup in embedded devices.
Yes, this is a totally vanilla setup except that for modern hardware the baseband is connected digitally also.
But the bluetooth audio support seems to be entirely written in userspace. The in-kernel bluetooth drivers in general seem only to provide a common interface to the underlying hardware and all of the higher level functionality seems to be implemented in userspace. So right now I have no idea where to start if one wanted to add a ASoC driver which did the bt-dai configuration.
The obvious starting point would seem to be to provide a driver which allows userspace to tell the kernel about configuration changes - that's what we're doing at the minute for the trivial case where the hardware doesn't change configuration. We could then look at pushing more of the code into the kernel if that made sense.