On Fri, Apr 27, 2012 at 09:14:23PM +0300, Ujfalusi, Peter wrote: > On Fri, Apr 27, 2012 at 8:19 PM, Russell King - ARM Linux > <linux@xxxxxxxxxxxxxxxx> wrote: > > root@omap-4430sdp:~# lsmod > > Module Size Used by > > snd_soc_dmic 1492 0 > > snd_soc_omap4_hdmi 1724 0 > > snd_soc_omap_hdmi 1536 0 > > snd_soc_omap_abe_twl6040 4867 0 > > snd_soc_omap_dmic 4248 0 > > snd_soc_omap_mcpdm 3077 1 snd_soc_omap_abe_twl6040 > > snd_soc_omap 2987 0 > > snd_soc_twl6040 18601 1 snd_soc_omap_abe_twl6040 > > root@omap-4430sdp:~# cat /proc/asound/cards > > --- no soundcards --- > > root@omap-4430sdp:~# grep . /sys/kernel/debug/asoc/* > > /sys/kernel/debug/asoc/codecs:dmic-codec > > /sys/kernel/debug/asoc/codecs:snd-soc-dummy > > /sys/kernel/debug/asoc/codecs:omapdss_hdmi > > the twl6040 codec is missing. > > > /sys/kernel/debug/asoc/dais:dmic-hifi > > /sys/kernel/debug/asoc/dais:omap-dmic > > /sys/kernel/debug/asoc/dais:omap-mcpdm > > /sys/kernel/debug/asoc/dais:snd-soc-dummy-dai > > /sys/kernel/debug/asoc/dais:hdmi-audio-codec > > as well the dai for the twl6040. > > > /sys/kernel/debug/asoc/platforms:omap-pcm-audio > > /sys/kernel/debug/asoc/platforms:snd-soc-dummy > > > > So the answer is... no. > > Hrm. > I don't think you can build the twl6040 MFD core driver as a module. > Do you have CONFIG_TWL6040_CORE=y ? > We have MFD for twl6040 since it provides audio and vibra functionality as well. CONFIG_TWL6040_CORE=y > Can you check if you have this commit: > http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=commit;h=8eaeb9393397be8eb700ab38a69c450975463b77 I don't have that in the branch I'm building because I started the DMA engine work against v3.4-rc3. > This is the second patch to separate the twl6040 from twl-core. > If you are missing this patch twl6040 will not probe (twl core will > not register the audio if we have twl6030). So it sounds like if I rebase stuff forward to -rc4, it should start working? -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html