From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm/dt: tegra devicetree support
Date: Wed, 20 Jul 2011 17:03:55 +0100 [thread overview]
Message-ID: <20110720160355.GB2406@sirena.org.uk> (raw)
In-Reply-To: <74CDBE0F657A3D45AFBB94109FB122FF049EBDEE27@HQMAIL01.nvidia.com>
On Wed, Jul 20, 2011 at 08:37:19AM -0700, Stephen Warren wrote:
> Grant Likely wrote at Tuesday, July 19, 2011 5:43 PM:
> > + sound {
> > + compatible = "nvidia,harmony-sound", "nvidia,tegra-wm8903";
> I thought the sound bindings were still somewhat experimental and not
> completely agreed upon. One issue I see is that Device Tree is
> supposed to represent pure HW, rather than driver-required abstractions,
> and at least the compatible name here is pretty Linux-driver-specific.
The current decision is that the schematic for embedded audio hardware
is sufficiently interesting to be considered hardware in its own right
separately to the chips contained within it.
> > + spkr-en-gpios = <&codec 2 0>;
> Should that be "gpio" not "gpios", since there is only one?
There's only one in this board but one does see designs with separate
left and right channel enables sometimes, or separate front and back
speaker enables for phones.
next prev parent reply other threads:[~2011-07-20 16:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-19 23:43 [PATCH] arm/dt: tegra devicetree support Grant Likely
2011-07-19 23:56 ` Olof Johansson
2011-07-20 18:56 ` Grant Likely
2011-07-20 15:37 ` Stephen Warren
2011-07-20 16:03 ` Mark Brown [this message]
2011-07-20 18:31 ` Grant Likely
2011-07-20 18:40 ` Stephen Warren
2011-07-20 18:47 ` Grant Likely
2011-07-20 19:49 ` Mark Brown
2011-07-20 18:28 ` Grant Likely
2011-07-20 18:33 ` Stephen Warren
2011-07-20 18:45 ` Grant Likely
2011-07-20 22:49 ` Shawn Guo
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=20110720160355.GB2406@sirena.org.uk \
--to=broonie@opensource.wolfsonmicro.com \
--cc=linux-arm-kernel@lists.infradead.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