From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Jon Smirl <jonsmirl@gmail.com>
Cc: alsa-devel@alsa-project.org, linaro-dev@lists.linaro.org,
devicetree-discuss@lists.ozlabs.org,
kernel-team@lists.ubuntu.com,
Jeremy Kerr <jeremy.kerr@canonical.com>,
lrg@slimlogic.co.uk
Subject: Re: ALSA SoC device tree bindings
Date: Sun, 27 Jun 2010 21:53:29 +0100 [thread overview]
Message-ID: <ED586769-8F80-4548-8CDE-9E4FBB0F58F7@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <AANLkTimIv99spub4iYnMFKTcNKIzcaPTmDE_b7ygmLJ-@mail.gmail.com> (sfid-20100627_134001_594020_7513B7E6)
On 27 Jun 2010, at 13:39, Jon Smirl wrote:
> On Sun, Jun 27, 2010 at 5:42 AM, Mark Brown
>> well, especially in the design section which doesn't make any mention at
>> all of machine specific drivers.
> Do we really want to call them machine drivers? Machine drivers
> already exist in the basic non-audio platform code. Calling the audio
> drivers machine drivers overloads the term. In the Apple audio code
> they are called fabric drivers.
They've been called machine drivers for years. If you find this confusing
I'd suggest qualifying the name ("ASoC machine drivers"), I don't think
renaming them would be worthwhile just for PowerPC. Given the similarity
of their role I'm having a hard time seeing the overlap as a bad thing even
for the people who have difficulty with this.
prev parent reply other threads:[~2010-06-27 20:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-23 12:30 ALSA SoC device tree bindings Jeremy Kerr
2010-06-25 11:25 ` Mark Brown
2010-06-25 13:21 ` Timur Tabi
2010-06-27 9:42 ` Mark Brown
2010-06-27 12:39 ` Jon Smirl
2010-06-27 20:53 ` Mark Brown [this message]
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=ED586769-8F80-4548-8CDE-9E4FBB0F58F7@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=jeremy.kerr@canonical.com \
--cc=jonsmirl@gmail.com \
--cc=kernel-team@lists.ubuntu.com \
--cc=linaro-dev@lists.linaro.org \
--cc=lrg@slimlogic.co.uk \
/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