[alsa-devel] ASoC: OMAP mcbsp: dai->dev is missing warning
Hello,
Recently the following warnings appeared during the bootup on OMAP platforms:
No device for DAI omap-mcbsp-dai-0 No device for DAI omap-mcbsp-dai-1 No device for DAI omap-mcbsp-dai-2 No device for DAI omap-mcbsp-dai-3 No device for DAI omap-mcbsp-dai-4
I have taken a look, and it is printed, because the dai->dev is NULL for OMAP McBSP DAIs. Also the comment there states, that the dai->dev will become mandatory in the future. At the moment the platform device/driver is not used for the sound/soc/omap/omap-mcbsp, it is used for the arch/arm/plat-omap/mcbsp.c, so we really don't have possibility at the moment to provide a valid dai->dev for ASoC at the moment.
Mark: Do you have some estimates, when the dai->dev will become mandatory?
Jarkko: Shall we start to think about the possibilities to provide a valid dai-
dev for the mcbsp DAIs?
On Thu, Dec 03, 2009 at 11:45:47AM +0200, Peter Ujfalusi wrote:
Recently the following warnings appeared during the bootup on OMAP platforms:
For fairly large definitions of recent :)
At the moment the platform device/driver is not used for the sound/soc/omap/omap-mcbsp, it is used for the arch/arm/plat-omap/mcbsp.c, so we really don't have possibility at the moment to provide a valid dai->dev for ASoC at the moment.
You could presumably get the plat-omap code to tell the ASoC code what the dev is and use that? When the board driver code loads it could ask the McBSP ASoC driver to register the required ports.
Mark: Do you have some estimates, when the dai->dev will become mandatory?
Not firm. I would hope to start using it for things like suspend/resume sequencing before 2.6.34 but it's not likely to be mandatory then. To a certain extent it depends on getting the major platforms converted over.
participants (2)
-
Mark Brown -
Peter Ujfalusi