Once more I've reflowed your text. *Please* fix this, it's really hurting the legibility of your mail.
On Mon, Feb 07, 2011 at 07:09:30PM +0100, Lars-Peter Clausen wrote:
On 02/07/2011 06:49 PM, Mark Brown wrote:
The card is only registering one DAI, all the other DAIs are attached to other devices in the system.
Isn't the card the combination of these other devices?
Well, yes...
The bluetooth chip is an actual device which I can point to on the board and schematic, having a struct device to represent a device that's actually present doesn't seem like a great leap.
Well, there is an actual device representing the bt device, but since this is the standard bt usb device I have no idea how we would get an reference to it from within the sound board driver.
If you've got a real device and a driver binding to it then you can make the driver for that device register the DAI from its probe function, no need for the machine driver to get involved.
It does mean it's named after the board.
Ok. Could you please explain how snd_soc_register_machine would work and how it would effekt the naming of the dai? I couldn't find any reference to it.
Sorry, snd_soc_register_card(). This skips the soc-audio device and allows the card to be registered from a regular device, meaning you can do things like pass platform data in sanely and handle multiple boards in a kernel without machine_is_() faff.