From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Jeremy Kerr <jeremy.kerr@canonical.com>
Cc: devicetree-discuss@lists.ozlabs.org,
kernel-team@lists.ubuntu.com, linaro-dev@lists.linaro.org,
alsa-devel@alsa-project.org, lrg@slimlogic.co.uk
Subject: Re: ALSA SoC device tree bindings
Date: Fri, 25 Jun 2010 12:25:07 +0100 [thread overview]
Message-ID: <20100625112506.GA2803@sirena.org.uk> (raw)
In-Reply-To: <201006232030.14138.jeremy.kerr@canonical.com>
On Wed, Jun 23, 2010 at 08:30:13PM +0800, Jeremy Kerr wrote:
> From some discussions at the previous Ubuntu Developer Summit, I've put up a
> page on the devicetree.org wiki with the ultimate goal of describing device
> tree bindings for ALSA System on Chip devices.
Please do remember to CC maintainers on e-mails if you're looking for a
response, this is standard practice for kernel stuff due to the number
of high volume mailing lists and busy maintainers. I've added Liam into
the CCs.
> So - if you're interested in the ALSA and/or device tree areas, please take a
> look at the notes from UDS:
> http://devicetree.org/SoC_Audio
A few comments:
- There's no mention of clocking in the page, which is one of the more
exciting bits of this stuff. Reading the page I'm not sure that
we've even fully captured the problem definition.
- I'm not sure what "ALSA quirking" is?
- "i2s" isn't the best thing to use in a property name, I2S is just one
of several different standards for interconn
- How does the way you're defining the audio links cope with multi-drop
links (eg, bluetooth and cellular modem on the same bus)?
next prev parent reply other threads:[~2010-06-25 11:25 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 [this message]
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
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=20100625112506.GA2803@sirena.org.uk \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=jeremy.kerr@canonical.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