linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>,
	debian-powerpc <debian-powerpc@lists.debian.org>
Subject: Re: [snd] looking for layout-ids
Date: Fri, 26 May 2006 11:14:08 +1000	[thread overview]
Message-ID: <1148606048.8089.8.camel@localhost.localdomain> (raw)
In-Reply-To: <1148553785.11759.12.camel@johannes.berg>

On Thu, 2006-05-25 at 12:43 +0200, Johannes Berg wrote:
> Hey,
> 
> In order to replace snd-powermac for the newer machines where the
> 'sound' node has the 'layout-id' property, I'm looking for testers on
> machines that have a layout-id [1] property with one of the following
> values: 0x24, 0x29, 0x33, 0x50 and 0x3a.

Some tips:

 0x24 is old G5's (PowerMac7,2 and 7,3) primary i2s bus
 0x29 is not in my list so I don't know what machine it is 
 0x33 is aluminium powerbook 15" rev. 2 (PowerMac5,4)
 0x3a is mac mini (I can test that one one of these days but we'll need
the
	        toonie codec, which is basically a "null" codec with only
	        the amps GPIOs available)
 0x50 is not in my list

Also not in your list nor in the driver:

 0x3c is recent single CPU desktop G5 (PowerMac9,1) (SMU based) bus
i2s-a
 0x3d is same as above bus i2s-c

The later is a onyx + topaz setup iirc, possibly similar to the quad.

> Once I have all these, I will, along with submitting snd-aoa [2], submit
> a patch to snd-powermac that makes it refuse loading in presence of a
> layout-id property as a first step to migrate to snd-aoa.
> 
> At the same time, I'll probably make i2sbus refuse attaching to a device
> unless there's a layout-id property so that it doesn't claim devices aoa
> doesn't handle yet.
> 
> johannes
> 
> [1] to find your layout-id, execute the following:
> 
>   find /proc/device-tree/ -name layout-id | xargs hexdump -e '1/4 "0x%x\n"'
> 
> If you get no output, you have no layout-id property. If you do get
> output, it will look like this:
>   0x46
> This is the layout-id of your sound node.
> 
> [2] Before you ask: I will not do this before snd-aoa supports headphone
> detection :)
> 
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-dev

  parent reply	other threads:[~2006-05-26  1:14 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-25 10:43 [snd] looking for layout-ids Johannes Berg
2006-05-25 12:33 ` Andreas Schwab
2006-05-25 12:37   ` Johannes Berg
     [not found] ` <20060525123247.GA19308@deepthought.linux.bogus>
2006-05-25 12:41   ` Johannes Berg
     [not found]     ` <20060525221111.GB27181@deepthought.linux.bogus>
2006-05-25 22:24       ` Johannes Berg
     [not found]         ` <20060525224905.GA28647@deepthought.linux.bogus>
2006-05-25 23:02           ` Johannes Berg
2006-05-25 13:43 ` Paul Collins
2006-05-26  1:14 ` Benjamin Herrenschmidt [this message]
2006-05-26  1:17 ` Benjamin Herrenschmidt
2006-05-26  7:28   ` Johannes Berg
2006-05-26  7:59     ` Benjamin Herrenschmidt
2006-05-26 16:02 ` Eddy Petrişor
2006-05-26 21:41   ` Benjamin Herrenschmidt
2006-05-29 11:49     ` Michael Schmitz

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=1148606048.8089.8.camel@localhost.localdomain \
    --to=benh@kernel.crashing.org \
    --cc=debian-powerpc@lists.debian.org \
    --cc=johannes@sipsolutions.net \
    --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).