From: Johannes Berg <johannes@sipsolutions.net>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
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 09:28:04 +0200 [thread overview]
Message-ID: <1148628484.16989.3.camel@johannes.berg> (raw)
In-Reply-To: <1148606268.8089.12.camel@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 584 bytes --]
On Fri, 2006-05-26 at 11:17 +1000, Benjamin Herrenschmidt wrote:
> I think we need to be careful about a couple other things:
>
> - We need non-pmf GPIO. Some layout-id based machines do need that,
> like the mac mini
Yeah, I saw that, but I need more insight into how that should work with
a feature call or so...
> - I'm tempted to rename soundbus/i2sbus to snd-aoa-soundbus and
> snd-aoa-i2sbus (at least the module names) for now.
Yeah, I guess that ought to be done. Not just the module names, also the
sysfs visible part (though that's easy).
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 793 bytes --]
next prev parent reply other threads:[~2006-05-26 7:28 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
2006-05-26 1:17 ` Benjamin Herrenschmidt
2006-05-26 7:28 ` Johannes Berg [this message]
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=1148628484.16989.3.camel@johannes.berg \
--to=johannes@sipsolutions.net \
--cc=benh@kernel.crashing.org \
--cc=debian-powerpc@lists.debian.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).