From: "Jon Smirl" <jonsmirl@gmail.com>
To: benh@kernel.crashing.org
Cc: PowerPC dev list <Linuxppc-dev@ozlabs.org>
Subject: Re: Device trees and audio codecs
Date: Sun, 21 Oct 2007 18:12:41 -0400 [thread overview]
Message-ID: <9e4733910710211512v238fbc89m35783d5eb5b82bf6@mail.gmail.com> (raw)
In-Reply-To: <1193004399.6745.39.camel@pasglop>
On 10/21/07, Benjamin Herrenschmidt <benh@kernel.crashing.org> wrote:
>
> On Sun, 2007-10-21 at 17:33 -0400, Jon Smirl wrote:
> > > This is one of the i2s channels on the macio. Dunno why they put
> > > all those platform-XXX entries in here, (most of) these don't
> > > logically belong here.
> >
> > Actually those platform-XXX entries may be the solution I am looking
> > for. I can use the generic i2s driver to load a fabric driver as an
> > ALSA module.
>
> Yuck.
And your alternative is?
I can use the DTC to load the I2S and codec drivers.
How do I get the platform specific fabric driver loaded? There is no
way to load a driver matching on the platform name.
--
Jon Smirl
jonsmirl@gmail.com
next prev parent reply other threads:[~2007-10-21 22:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-20 15:33 Device trees and audio codecs Jon Smirl
2007-10-21 13:33 ` Timur Tabi
2007-10-21 14:01 ` Jon Smirl
2007-10-22 13:07 ` Timur Tabi
2007-10-23 19:12 ` Scott Wood
2007-10-21 19:14 ` Segher Boessenkool
2007-10-21 21:33 ` Jon Smirl
2007-10-21 22:06 ` Benjamin Herrenschmidt
2007-10-21 22:12 ` Jon Smirl [this message]
2007-10-21 22:19 ` Benjamin Herrenschmidt
2007-10-21 23:33 ` Segher Boessenkool
2007-10-22 0:29 ` Jon Smirl
2007-10-22 15:40 ` Timur Tabi
2007-10-22 18:43 ` Segher Boessenkool
2007-10-23 3:24 ` Grant Likely
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=9e4733910710211512v238fbc89m35783d5eb5b82bf6@mail.gmail.com \
--to=jonsmirl@gmail.com \
--cc=Linuxppc-dev@ozlabs.org \
--cc=benh@kernel.crashing.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).