On Mon, Oct 22, 2007 at 08:07:14AM -0500, Timur Tabi wrote:
Either you do it at driver __init time, or via a probe. The probe
actually occurs at __init time, anyway, so they're kinda the same thing.
The only thing the probe gets you is that you're called multiple times
for each instance
Jon Smirl wrote:
Doing it that way will make the kernel specific to the target device.
Currently I can load the same mpc5200 kernel on several different
target devices since the platform specific code is triggered in the
probe machine phase.
Maybe I need to take a look at your code, but the
Jon Smirl wrote:
I meant an ac97 bus. ac97 is conceptually the same as i2s with the
control signals also routed over it. ac97 and i2s are handled in the
same PSC on the 5200.
I have received conflicting opinions as to whether a codec hooked to
an ac97 bus should get a chip specific codec
It seems to me there are four issues here:
1) How to describe the audio transport controller;
2) How to describe the codecs;
3) How the various parts are connected together in the device tree;
4) How to describe the layout.
How do we want to be consistent with the Efika which uses an AC97
On 10/21/07, Jon Smirl [EMAIL PROTECTED] wrote:
I have received conflicting opinions as to whether a codec hooked to
an ac97 bus should get a chip specific codec entry in the device tree.
Without the codec specific entry only generic ac97 features can be
used. The Efika has a STA9766. Looking
Jon Smirl wrote:
I'm working on ALSA ASoC support for a codec chip on my mpc5200 based
target hardware. How should the codec be represented in the device
tree?
I'm also working on an ASoC driver, but for the 8610. I have a similar problem.
Under ASoC the device drivers for the codec chips
On 10/21/07, Timur Tabi [EMAIL PROTECTED] wrote:
For development purposes I'm using an Efika as a target platform. It
is easy enough to load the i2s driver using the device tree. I can add
entries to the i2s node to trigger loading of the generic sta9766
codec driver. How do I trigger
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
On 10/21/07, Segher Boessenkool [EMAIL PROTECTED] wrote:
I'm working on ALSA ASoC support for a codec chip on my mpc5200 based
target hardware.
What is ASoC?
asoc = ALSA System on a Chip. It is in sound/soc
Under ASoC the device drivers for the codec chips are platform
independent. In
On 10/21/07, Benjamin Herrenschmidt [EMAIL PROTECTED] 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
On Sun, 2007-10-21 at 18:12 -0400, Jon Smirl wrote:
On 10/21/07, Benjamin Herrenschmidt [EMAIL PROTECTED] 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)
Fabric driver tells how the generic codec is hooked up on the specific
board. Some of the codecs are extremely flexible and can be hooked up
hundreds of different ways. It is like GPIO pins, they are wired in
however is convenient for the design.
Gotcha. *Very* much like GPIOs, indeed.
The
On 10/21/07, Segher Boessenkool [EMAIL PROTECTED] wrote:
How do we want to be consistent with the Efika which uses an AC97
codec that only connects to i2s?
Huh? AC'97 isn't I2S. Yeah you probably could hook it up to some I2S
device if you do all the interleaving and whatever stuff by hand
I'm working on ALSA ASoC support for a codec chip on my mpc5200 based
target hardware. How should the codec be represented in the device
tree?
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),
14 matches
Mail list logo
