On Mon, Jan 02, 2012 at 08:33:03PM +0200, Felipe Contreras wrote: > On Sat, Dec 31, 2011 at 2:59 AM, Mark Brown
> > Which is relevant because...? To repeat, the ordering of module loading > > is totally ortogonal as any ordering of modules is supported. You > > appear to be totally ignoring what I am writing here. > One thing how things _should_ be, and another is how things actually > _are_. Right now snd-soc-rx51 doesn't work if it's loaded before > snd_soc_tlv320aic3x. Period. Can you provide logs showing this (with debug logging enabled in soc-core)? If this is happening it's a very serious issue, though I am rather surprised that nobody else has noticed such an issue since the usual instantiation order would have the card appear before the CODEC (due to the fact that the card is normally a platform device) and the structure of the code makes it difficult to imagine a failure path. > That means that *right now*, snd-soc-rx51 works fine with udev, > because snd_soc_tlv320aic3x will be loaded at boot time. Now, if > snd-soc-rx51 is converted and loaded automatically by udev as well, > the issues might appear again. Not if we look at and resolve the actual issue. Once again, any instantation ordering should be supported. I really don't understand why you keep on talking about fixing the module ordering, -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
