Re: snd-aoa status update / automatic driver loading
From: Johannes Berg <johannes@sipsolutions.net>
Date: 2006-05-23 12:28:20
On Mon, 2006-05-22 at 22:11 -0500, Hollis Blanchard wrote:
The "auto-loading" stuff doesn't seem to be working for me on my PowerMac11,2, with a fresh git clone as of right now. What is the base module that should load all the others? After a "make install", I still had to modprobe almost everything by hand (`find ./snd-aoa -name \*.ko` in the source directory to get a list).
Odd. i2sbus should pull in all other required modules, and should itself load automatically at boot due to having a modalias that matches the of:... modalias the mac-io bus device for the i2s stuff has.
snd-aoa-codec-tas: found keywest-i2c-bus, checking if tas chip is on it snd-aoa-codec-tas: created and attached tas instance snd-aoa-codec-tas: found keywest-i2c-bus, checking if tas chip is on it snd-aoa-codec-tas: created and attached tas instance
Uh. That one I need to check, there is no tas codec on your machine.
snd: Unknown layout ID 0x44
That looks like you have snd-powermac loaded too. Or not? I don't think I have anything that prints "snd:" as the prefix but I might be wrong.
snd-aoa-fabric-layout: found bus with layout 68 (using) snd-aoa: fabric didn't like codec tas snd-aoa: fabric didn't like codec tas snd-aoa-codec-onyx: found pcm3052 snd-aoa-fabric-layout: platform-onyx-codec-ref doesn't match! snd-aoa: fabric didn't like codec onyx snd-aoa-codec-onyx: created and attached onyx instance snd-aoa-codec-onyx: found pcm3052 snd-aoa-fabric-layout: can use this codec snd-aoa-codec-onyx: attached to onyx codec via i2c snd-aoa-codec-onyx: created and attached onyx instance
Most of this is due to that device-tree bug on those machines.
For the record, there are two "layout-id" properties in my device tree, as discussed in this patch: http://patchwork.ozlabs.org/linuxppc/patch?id=4867
Note that the patch is mine :) But also note that this isn't the reason that there are two layout-id properties, there really *are* two sound nodes with layout-id property because there are two i2s busses for the two codecs.
Ultimately, snd_aoa_codec_onyx seems to be the happy module. Only the headphone jack was enabled; I had to use GNOME's "Volume Control" panel applet to enable speakers or line out (both of which work). However, volume control doesn't work at all, for both line-out and headphone jacks. Should it?
Yes, it should. I think the bug is that the tas module thinks it can attach a codec here. Can you try *not* loading that module and see if it works better then? I'll try to see if I can make the tas module not attach on those machines, but as long as you don't load it manually all should be fine.
Also, it would be helpful if the git tree were better publicized somewhere (e.g. http://johannes.sipsolutions.net/). I had to dig through a LOT of mails to find the source.
Sorry. I linked it up on http://johannes.sipsolutions.net/Projects/ and will add a few more details later. johannes
Attachments
- signature.asc [application/pgp-signature] 793 bytes