Re: [alsa-devel] It looks like snd-soc-rx51 only works as built-in, not as a module
On Thu, Dec 29, 2011 at 11:51:11PM +0200, Felipe Contreras wrote:
On Thu, Dec 29, 2011 at 11:27 PM, Mark Brown
On Thu, Dec 29, 2011 at 11:25:50PM +0200, Felipe Contreras wrote:
On Thu, Dec 29, 2011 at 8:37 PM, Mark Brown
On Sat, Dec 10, 2011 at 05:59:57PM +0200, Felipe Contreras wrote:
It was not working for me, but it seems the problem was related to mdev/udev; snd_soc_tlv320aic3x has to be loaded before snd-soc-rx51.
That should not be required, the modules should be loadable in any order.
Are you sure? I recall having a similar discussion with Rusell King, and the conclusion is that certain modules are supposed to be loaded by udev at boot time, and it seems snd_soc_tlv320aic3x is one of them.
I'm absolutely positive. ASoC supports loading the modules in any order. udev is supposed to load anything autoloadable at boot time, including I2C devices, but that's orthogonal to the order in which things actually get loaded - udev can randomly reorder things if it feels like it.
Yes, but udev loads snd_soc_tlv320aic3x, not snd-soc-rx51.
That is compltelely orthogonal to what you were saying above about the ordering of module loading.
The reason the driver is not loaded automatically is that the OMAP machine drivers have not been converted to platform devices.
Mark Brown broonie@opensource.wolfsonmicro.com writes:
On Thu, Dec 29, 2011 at 11:51:11PM +0200, Felipe Contreras wrote:
On Thu, Dec 29, 2011 at 11:27 PM, Mark Brown
On Thu, Dec 29, 2011 at 11:25:50PM +0200, Felipe Contreras wrote:
On Thu, Dec 29, 2011 at 8:37 PM, Mark Brown
On Sat, Dec 10, 2011 at 05:59:57PM +0200, Felipe Contreras wrote:
It was not working for me, but it seems the problem was related to mdev/udev; snd_soc_tlv320aic3x has to be loaded before snd-soc-rx51.
That should not be required, the modules should be loadable in any order.
Are you sure? I recall having a similar discussion with Rusell King, and the conclusion is that certain modules are supposed to be loaded by udev at boot time, and it seems snd_soc_tlv320aic3x is one of them.
I'm absolutely positive. ASoC supports loading the modules in any order. udev is supposed to load anything autoloadable at boot time, including I2C devices, but that's orthogonal to the order in which things actually get loaded - udev can randomly reorder things if it feels like it.
Yes, but udev loads snd_soc_tlv320aic3x, not snd-soc-rx51.
That is compltelely orthogonal to what you were saying above about the ordering of module loading.
The reason the driver is not loaded automatically is that the OMAP machine drivers have not been converted to platform devices.
I posted patches doing the conversion a long time ago (September?). It seems they got lost somewhere.
On Thu, Dec 29, 2011 at 10:22:31PM +0000, M?ns Rullg?rd wrote:
Mark Brown broonie@opensource.wolfsonmicro.com writes:
The reason the driver is not loaded automatically is that the OMAP machine drivers have not been converted to platform devices.
I posted patches doing the conversion a long time ago (September?). It seems they got lost somewhere.
Most of them have been converted, but the rx51 wasn't.
On 12/30/2011 12:52 PM, Mark Brown wrote:
On Thu, Dec 29, 2011 at 10:22:31PM +0000, M?ns Rullg?rd wrote:
Mark Brownbroonie@opensource.wolfsonmicro.com writes:
The reason the driver is not loaded automatically is that the OMAP machine drivers have not been converted to platform devices.
I posted patches doing the conversion a long time ago (September?). It seems they got lost somewhere.
Most of them have been converted, but the rx51 wasn't.
I guess that patch has been forgotten. Måns: care to check and resend? It's definitely great to get OMAP ASoC machine driver autoloading working.
participants (3)
-
Jarkko Nikula -
Mark Brown -
Måns Rullgård