From: Timur Tabi <timur@freescale.com>
To: Jon Smirl <jonsmirl@gmail.com>,
Grant Likely <grant.likely@secretlab.ca>,
linuxppc-dev@ozlabs.org, alsa-devel@alsa-project.org,
liam.girdwood@wolfsonmicro.com
Subject: Re: [PATCH v2 1/3] ALSA SoC: Add OpenFirmware helper for matching bus and codec drivers
Date: Mon, 14 Jul 2008 11:14:41 -0500 [thread overview]
Message-ID: <487B7B71.9060606@freescale.com> (raw)
In-Reply-To: <20080714150527.GD25448@sirena.org.uk>
Mark Brown wrote:
>> The PowerPC side isn't without fault too. PowerPC still doesn't have a
>> good way to load the fabric/machine driver.
>
> I'm finding it difficult to square these two statements - from an ASoC
> point of view the main thing this patch is doing is adding a machine
> driver and that's not something that's going to go away.
Jon's concern is that there is no straightforward way to build a kernel with
multiple fabric drivers and have the right one chosen via the device tree. This
is just a limitation of the device tree model, and no one has come up with a
good solution yet.
The problem still exists in ASoC V2. However, it's not anything that ASoC
itself needs to be concerned with. It's purely a PowerPC problem.
>> Which are we going to call it, fabric or machine? I had been working
>> on the Apple code in sound/aoa. It is called fabric in that code. The
>> equivalent driver is called machine in ASoC v1.
>
> ASoC has always called it a machine driver.
Wait, I thought it's supposed to be called a fabric driver now? On PowerPC, it
should be called a fabric driver because we already have machine drivers.
--
Timur Tabi
Linux kernel developer at Freescale
WARNING: multiple messages have this Message-ID (diff)
From: Timur Tabi <timur@freescale.com>
To: Jon Smirl <jonsmirl@gmail.com>,
Grant Likely <grant.likely@secretlab.ca>,
linuxppc-dev@ozlabs.org, alsa-devel@alsa-project.org,
liam.girdwood@wolfsonmicro.com
Subject: Re: [alsa-devel] [PATCH v2 1/3] ALSA SoC: Add OpenFirmware helper for matching bus and codec drivers
Date: Mon, 14 Jul 2008 11:14:41 -0500 [thread overview]
Message-ID: <487B7B71.9060606@freescale.com> (raw)
In-Reply-To: <20080714150527.GD25448@sirena.org.uk>
Mark Brown wrote:
>> The PowerPC side isn't without fault too. PowerPC still doesn't have a
>> good way to load the fabric/machine driver.
>
> I'm finding it difficult to square these two statements - from an ASoC
> point of view the main thing this patch is doing is adding a machine
> driver and that's not something that's going to go away.
Jon's concern is that there is no straightforward way to build a kernel with
multiple fabric drivers and have the right one chosen via the device tree. This
is just a limitation of the device tree model, and no one has come up with a
good solution yet.
The problem still exists in ASoC V2. However, it's not anything that ASoC
itself needs to be concerned with. It's purely a PowerPC problem.
>> Which are we going to call it, fabric or machine? I had been working
>> on the Apple code in sound/aoa. It is called fabric in that code. The
>> equivalent driver is called machine in ASoC v1.
>
> ASoC has always called it a machine driver.
Wait, I thought it's supposed to be called a fabric driver now? On PowerPC, it
should be called a fabric driver because we already have machine drivers.
--
Timur Tabi
Linux kernel developer at Freescale
next prev parent reply other threads:[~2008-07-14 16:14 UTC|newest]
Thread overview: 89+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-12 8:39 [PATCH v2 1/3] ALSA SoC: Add OpenFirmware helper for matching bus and codec drivers Grant Likely
2008-07-12 8:39 ` Grant Likely
2008-07-12 8:39 ` [PATCH v2 2/3] ALSA SoC: Add mpc5200-psc I2S driver Grant Likely
2008-07-14 12:10 ` Mark Brown
2008-07-14 12:10 ` [alsa-devel] " Mark Brown
2008-07-12 8:39 ` [PATCH v2 3/3] ALSA SoC: Add Texas Instruments TLV320AIC26 codec driver Grant Likely
2008-07-12 8:39 ` Grant Likely
2008-07-12 18:10 ` Mark Brown
2008-07-12 18:10 ` [alsa-devel] " Mark Brown
2008-07-12 18:14 ` Grant Likely
2008-07-12 18:14 ` [alsa-devel] " Grant Likely
2008-07-14 11:45 ` Mark Brown
2008-07-14 11:45 ` [alsa-devel] " Mark Brown
2008-07-18 6:29 ` Grant Likely
2008-07-18 6:29 ` [alsa-devel] " Grant Likely
2008-07-18 10:39 ` Mark Brown
2008-07-18 10:39 ` [alsa-devel] " Mark Brown
2008-07-15 7:57 ` dinesh
2008-07-15 7:57 ` [alsa-devel] " dinesh
2008-07-15 10:33 ` Mark Brown
2008-07-15 10:33 ` [alsa-devel] " Mark Brown
2008-07-15 12:38 ` dinesh
2008-07-15 12:38 ` [alsa-devel] " dinesh
2008-07-15 12:46 ` Mark Brown
2008-07-15 12:46 ` [alsa-devel] " Mark Brown
2008-07-16 9:05 ` WRITING AN SOC DRIVER WITHOUT DMA dinesh
2008-07-16 9:05 ` dinesh
2008-07-16 10:07 ` Nobin Mathew
2008-07-16 10:07 ` [alsa-devel] " Nobin Mathew
2008-07-16 10:13 ` dinesh
2008-07-16 10:13 ` [alsa-devel] " dinesh
2008-07-17 6:03 ` dinesh
2008-07-17 6:03 ` [alsa-devel] " dinesh
2008-07-17 10:56 ` Mark Brown
2008-07-17 10:56 ` [alsa-devel] " Mark Brown
2008-07-17 11:26 ` Nobin Mathew
2008-07-17 11:26 ` [alsa-devel] " Nobin Mathew
2008-07-17 12:05 ` Jon Smirl
2008-07-17 12:05 ` [alsa-devel] " Jon Smirl
2008-07-17 16:02 ` [PATCH v2 3/3] ALSA SoC: Add Texas Instruments TLV320AIC26 codec driver Timur Tabi
2008-07-14 13:49 ` [PATCH v2 1/3] ALSA SoC: Add OpenFirmware helper for matching bus and codec drivers Mark Brown
2008-07-14 13:49 ` [alsa-devel] " Mark Brown
2008-07-14 14:13 ` Jon Smirl
2008-07-14 14:13 ` [alsa-devel] " Jon Smirl
2008-07-14 15:05 ` Mark Brown
2008-07-14 15:05 ` [alsa-devel] " Mark Brown
2008-07-14 16:14 ` Timur Tabi [this message]
2008-07-14 16:14 ` Timur Tabi
2008-07-14 16:27 ` Grant Likely
2008-07-14 16:27 ` [alsa-devel] " Grant Likely
2008-07-14 16:53 ` Mark Brown
2008-07-14 16:53 ` [alsa-devel] " Mark Brown
2008-07-14 17:21 ` Grant Likely
2008-07-14 17:21 ` [alsa-devel] " Grant Likely
2008-07-14 18:36 ` Mark Brown
2008-07-14 18:36 ` [alsa-devel] " Mark Brown
2008-07-14 18:40 ` Timur Tabi
2008-07-14 18:40 ` [alsa-devel] " Timur Tabi
2008-07-14 18:49 ` Mark Brown
2008-07-14 18:49 ` [alsa-devel] " Mark Brown
2008-07-14 18:53 ` Timur Tabi
2008-07-14 18:53 ` [alsa-devel] " Timur Tabi
2008-07-14 22:28 ` Grant Likely
2008-07-14 22:28 ` [alsa-devel] " Grant Likely
2008-07-14 23:45 ` Jon Smirl
2008-07-14 23:45 ` [alsa-devel] " Jon Smirl
2008-07-15 10:13 ` Mark Brown
2008-07-15 10:13 ` [alsa-devel] " Mark Brown
2008-07-15 13:08 ` Jon Smirl
2008-07-15 13:08 ` [alsa-devel] " Jon Smirl
2008-07-15 14:04 ` Mark Brown
2008-07-15 14:04 ` [alsa-devel] " Mark Brown
2008-07-14 15:51 ` Timur Tabi
2008-07-14 15:51 ` [alsa-devel] " Timur Tabi
2008-07-14 17:06 ` Grant Likely
2008-07-14 17:06 ` [alsa-devel] " Grant Likely
2008-07-14 17:16 ` Mark Brown
2008-07-14 17:16 ` [alsa-devel] " Mark Brown
2008-07-14 17:22 ` Grant Likely
2008-07-14 17:22 ` [alsa-devel] " Grant Likely
2008-07-18 7:17 ` Grant Likely
2008-07-18 7:17 ` [alsa-devel] " Grant Likely
2008-07-18 10:00 ` Mark Brown
2008-07-18 10:00 ` [alsa-devel] " Mark Brown
2008-07-18 14:59 ` Timur Tabi
2008-07-18 14:59 ` [alsa-devel] " Timur Tabi
2008-07-14 14:16 ` Anton Vorontsov
2008-07-14 14:16 ` Anton Vorontsov
2008-07-14 17:11 ` 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=487B7B71.9060606@freescale.com \
--to=timur@freescale.com \
--cc=alsa-devel@alsa-project.org \
--cc=grant.likely@secretlab.ca \
--cc=jonsmirl@gmail.com \
--cc=liam.girdwood@wolfsonmicro.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.