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: Sun, 27 Jun 2010 10:42:47 +0100 [thread overview]
Message-ID: <20100627094246.GA2845@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:
> 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).
Actually, re-reading the page I'm not sure it really captures my
understanding of the discussion (and all the previous discussions we've
had on the lists and so on) at all. Reading the page the idea that a
machine specific driver is normal and expected doesn't come over at all
well, especially in the design section which doesn't make any mention at
all of machine specific drivers.
As I keep saying the main thing I'm looking for from any device tree
binding is something that I can point people at so we don't need to go
through the rehashings of this subject which come up every time someone
decides they want to use device trees.
next prev parent reply other threads:[~2010-06-27 9:42 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 [this message]
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=20100627094246.GA2845@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