From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: Sebastian Reichel <sre@debian.org>,
alsa-devel@alsa-project.org, linux-omap@vger.kernel.org,
Jarkko Nikula <jarkko.nikula@bitmer.com>
Subject: Re: It looks like snd-soc-rx51 only works as built-in, not as a module
Date: Sat, 31 Dec 2011 00:59:38 +0000 [thread overview]
Message-ID: <20111231005935.GA5835@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <CAMP44s0EzmhdZ4X91c5X7Rn9q44QcUDm2KNDO81ue16SBWM6_g@mail.gmail.com>
On Fri, Dec 30, 2011 at 10:00:55PM +0200, Felipe Contreras wrote:
> On Thu, Dec 29, 2011 at 11:54 PM, Mark Brown
> > On Thu, Dec 29, 2011 at 11:51:11PM +0200, Felipe Contreras wrote:
> >> >> > That should not be required, the modules should be loadable in any
> >> >> > order.
> >> 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.
> Not really, because if both are compiled as modules,
> snd_soc_tlv320aic3x will always be loaded first (automatically by
> udev).
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.
> > The reason the driver is not loaded automatically is that the OMAP
> > machine drivers have not been converted to platform devices.
> Well, if that's the case then there's a real issue. There doesn't seem
> to be a MODULE_DEPENDS(), or anything like that.
A MODULE_DEPENDS() would also be irrelevant here.
> snd-soc-rx51 seems to depend on snd_soc_tlv320aic3x through
> codec_dai_name, and codec_name, and so on. I don't know how this
> dependency is supposed to work out.
All the drivers should load via the normal driver instantiation
mechainsms and when they're all there they'll get matched together.
next prev parent reply other threads:[~2011-12-31 0:59 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-09 23:04 It looks like snd-soc-rx51 only works as built-in, not as a module Felipe Contreras
2011-12-10 8:27 ` Sebastian Reichel
2011-12-10 15:59 ` Felipe Contreras
2011-12-29 18:37 ` Mark Brown
2011-12-29 21:25 ` Felipe Contreras
2011-12-29 21:27 ` Mark Brown
2011-12-29 21:51 ` Felipe Contreras
2011-12-29 21:54 ` Mark Brown
2011-12-29 22:22 ` Måns Rullgård
2011-12-30 10:52 ` [alsa-devel] " Mark Brown
2011-12-30 11:15 ` Jarkko Nikula
2011-12-30 18:21 ` Måns Rullgård
2011-12-30 19:34 ` Måns Rullgård
2011-12-31 1:02 ` Mark Brown
2011-12-30 20:00 ` Felipe Contreras
2011-12-31 0:59 ` Mark Brown [this message]
2012-01-02 18:33 ` Felipe Contreras
2012-01-02 19:40 ` Mark Brown
2012-01-03 0:19 ` Måns Rullgård
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20111231005935.GA5835@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=felipe.contreras@gmail.com \
--cc=jarkko.nikula@bitmer.com \
--cc=linux-omap@vger.kernel.org \
--cc=sre@debian.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.