From: Segher Boessenkool <segher@kernel•crashing.org>
To: "Jon Smirl" <jonsmirl@gmail•com>
Cc: PowerPC dev list <Linuxppc-dev@ozlabs•org>
Subject: Re: Device trees and audio codecs
Date: Sun, 21 Oct 2007 21:14:44 +0200 [thread overview]
Message-ID: <a76a128145ec8a8f779727a7e11925ac@kernel.crashing.org> (raw)
In-Reply-To: <9e4733910710200833x5d1c55b5l2cd400f77c13ec87@mail.gmail.com>
> I'm working on ALSA ASoC support for a codec chip on my mpc5200 based
> target hardware.
What is ASoC?
> Under ASoC the device drivers for the codec chips are platform
> independent. In the current ASoC model there are three device
> drivers: i2s (or spi, etc), the generic codec, and a platform specific
> 'fabric' driver. Some codecs are linked to both i2c and i2s.
The i2s driver is simply for data transport, the codec driver does,
well, what codecs do; and what is the fabric driver for? Just to
know which output ports are which, etc.?
> The fabric driver corresponds to the 'layout-id' in the Apple model.
> It tells how to configure the generic codec driver for the specific
> configuration needed by the actual platform hardware.
The apple layout-id selects one of several tables with *lots* of info.
I think you want a subset of that only.
> My target hardware has a codec that is linked to both i2s and i2c. How
> should it be represented?
Since the codec is addressable on i2c, and not on i2s, it should be
a child node of the i2c bus it sits on; and then you put a property
in the codec node pointing to the i2s bus node it is connected to.
Multiple of those (or multiple entries) if it is connected to more
than one i2s bus. "i2s-parent" might be a good name for such a prop.
> Apple has three entries. One for i2s, one for the codec, and one for
> soundchip. What is the soundchip entry, does it correspond to real
> hardware?
>
> /proc/device-tree/pci@f2000000/mac-io@17/i2s@0/i2s-a@10000:
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.
> /proc/device-tree/pci@f2000000/mac-io@17/i2s@0/i2s-a@10000/sound:
The codec. I guess Apple puts this here for their weirdo platform-do
stuff; don't imitate this :-)
> /proc/device-tree/pci@f2000000/mac-io@17/i2c@18000/i2c-bus@0/codec@6a:
The codec. _Do_ put it here in your tree :-)
Segher
next prev parent reply other threads:[~2007-10-21 19:14 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 [this message]
2007-10-21 21:33 ` Jon Smirl
2007-10-21 22:06 ` Benjamin Herrenschmidt
2007-10-21 22:12 ` Jon Smirl
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=a76a128145ec8a8f779727a7e11925ac@kernel.crashing.org \
--to=segher@kernel$(echo .)crashing.org \
--cc=Linuxppc-dev@ozlabs$(echo .)org \
--cc=jonsmirl@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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