linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Hollis Blanchard <hollis@penguinppc.org>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>,
	debian-powerpc <debian-powerpc@lists.debian.org>
Subject: Re: snd-aoa status update / automatic driver loading
Date: Tue, 23 May 2006 14:27:52 +0200	[thread overview]
Message-ID: <1148387282.25971.8.camel@johannes> (raw)
In-Reply-To: <20060522221138.683790c2@diesel>

[-- Attachment #1: Type: text/plain, Size: 3046 bytes --]

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

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 793 bytes --]

  reply	other threads:[~2006-05-23 12:28 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-17 10:09 snd-aoa status update / automatic driver loading Johannes Berg
2006-05-17 18:57 ` Tony Vroon
2006-05-19 10:22   ` Johannes Berg
2006-05-20 23:56     ` Benjamin Herrenschmidt
2006-05-22  6:42       ` Johannes Berg
2006-05-23 22:15         ` Benjamin Herrenschmidt
2006-05-24  9:42           ` Johannes Berg
2006-05-25  8:00             ` Benjamin Herrenschmidt
2006-05-25  9:42               ` Johannes Berg
2006-05-26  1:30                 ` Benjamin Herrenschmidt
2006-05-17 19:53 ` Andreas Schwab
2006-05-18 10:14   ` Johannes Berg
2006-05-17 21:54 ` Wolfgang Pfeiffer
2006-05-17 22:19   ` Wolfgang Pfeiffer
2006-05-18 10:13     ` Johannes Berg
2006-05-18 18:17       ` Wolfgang Pfeiffer
2006-05-18 22:06         ` Andreas Schwab
2006-05-19 12:50         ` Johannes Berg
2006-05-19 14:40           ` Wolfgang Pfeiffer
2006-05-19 14:40             ` Johannes Berg
2006-05-17 22:30   ` Dean Hamstead
2006-05-18  0:28     ` Wolfgang Pfeiffer
2006-05-18  0:39       ` Dean Hamstead
2006-05-18  1:01   ` Wolfgang Pfeiffer
2006-05-18  1:08   ` Benjamin Herrenschmidt
2006-05-18  7:25 ` Eddy Petrişor
2006-05-18 10:23   ` Johannes Berg
2006-05-19 13:20     ` Paul Collins
2006-05-19 13:46       ` Johannes Berg
2006-05-19 14:40         ` Paul Collins
2006-05-19 14:49           ` Johannes Berg
2006-05-19 15:13             ` Paul Collins
2006-05-19 14:33       ` Andreas Schwab
2006-05-19 14:37         ` Johannes Berg
2006-05-23 15:41       ` Sjoerd Simons
2006-05-25  7:21         ` Eddy Petrişor
2006-05-25  7:21           ` Eddy Petrişor
2006-05-25  9:43           ` Johannes Berg
2006-05-25 17:44     ` Eddy Petrişor
2006-05-25 18:47       ` Johannes Berg
2006-05-18  8:56 ` Rene Rebe
2006-05-18 10:08   ` Johannes Berg
     [not found] ` <200605180002.01669.borge@arivene.net>
     [not found]   ` <20060518004141.GC1552@kunpuu.plessy.org>
2006-05-20 14:57     ` Benjamin Berg
2006-05-20 23:59       ` Benjamin Herrenschmidt
2006-05-23  3:11 ` Hollis Blanchard
2006-05-23 12:27   ` Johannes Berg [this message]
2006-05-23 14:46     ` Hollis Blanchard
2006-05-23 15:25       ` Hollis Blanchard
2006-05-24  9:41       ` Johannes Berg

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=1148387282.25971.8.camel@johannes \
    --to=johannes@sipsolutions.net \
    --cc=debian-powerpc@lists.debian.org \
    --cc=hollis@penguinppc.org \
    --cc=linuxppc-dev@ozlabs.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).