From: Jeremy Kerr <jeremy.kerr-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org>
To: kernel-team-nLRlyDuq1AZFpShjVBNYrg@public.gmane.org,
linaro-dev-cunTk1MwBs8s++Sfvej+rw@public.gmane.org,
alsa-devel-K7yf7f+aM1XWsZ/bQMPhNw@public.gmane.org,
devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org
Subject: ALSA SoC device tree bindings
Date: Wed, 23 Jun 2010 20:30:13 +0800 [thread overview]
Message-ID: <201006232030.14138.jeremy.kerr@canonical.com> (raw)
Hi all,
>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.
At this stage, we're just looking at how to structure device in the device
tree. The bindings for specific devices will come as required (ie, as we add
device tree support for them).
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
- if you have any comments or suggestions, please let me know, or add to the
page (or the discussion for the page). I intend for this document to become a
more formal specification, but we still have a way to go before that happens.
If you'd like an introduction to device trees, Grant has a good walkthrough-
style document at:
http://devicetree.org/Device_Tree_Usage
Cheers,
Jeremy
next reply other threads:[~2010-06-23 12:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-23 12:30 Jeremy Kerr [this message]
2010-06-25 11:25 ` ALSA SoC device tree bindings 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
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=201006232030.14138.jeremy.kerr@canonical.com \
--to=jeremy.kerr-z7wlfzj8ewms+fvcfc7uqw@public.gmane.org \
--cc=alsa-devel-K7yf7f+aM1XWsZ/bQMPhNw@public.gmane.org \
--cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
--cc=kernel-team-nLRlyDuq1AZFpShjVBNYrg@public.gmane.org \
--cc=linaro-dev-cunTk1MwBs8s++Sfvej+rw@public.gmane.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox