From: Stephen Warren <swarren@wwwdotorg.org>
To: Mark Brown <broonie@kernel.org>
Cc: devicetree@vger.kernel.org, alsa-devel@alsa-project.org,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@linaro.org>
Subject: Re: [PATCH] ASoC: dt: Move WM8903 pin list from Tegra board binding to CODEC binding
Date: Wed, 07 Aug 2013 10:02:12 -0600 [thread overview]
Message-ID: <52026F84.5030204@wwwdotorg.org> (raw)
In-Reply-To: <1375866978-14726-1-git-send-email-broonie@kernel.org>
On 08/07/2013 03:16 AM, Mark Brown wrote:
> From: Mark Brown <broonie@linaro.org>
>
> The pin list is the same for any board using the CODEC.
> diff --git a/Documentation/devicetree/bindings/sound/nvidia,tegra-audio-wm8903.txt b/Documentation/devicetree/bindings/sound/nvidia,tegra-audio-wm8903.txt
> the second being the connection's source. Valid names for sources and
...
> + sinks are the WM8903's pins (documented in the WM8903 binding document),
> + and the jacks on the board:
>
> Board connectors:
Probably want to remove the line "Board connectors:" ?
> diff --git a/Documentation/devicetree/bindings/sound/wm8903.txt b/Documentation/devicetree/bindings/sound/wm8903.txt
> +Pins on the device (for linking into audio routes):
> +
> + * IN1L
> + * IN1R
I thought all the pins were going to be assigned numbers too so that
bindings could use either?
next prev parent reply other threads:[~2013-08-07 16:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-07 9:16 [PATCH] ASoC: dt: Move WM8903 pin list from Tegra board binding to CODEC binding Mark Brown
2013-08-07 16:02 ` Stephen Warren [this message]
2013-08-07 16:30 ` Mark Brown
2013-08-07 17:02 ` Stephen Warren
2013-08-07 17:47 ` Mark Brown
2013-08-07 18:16 Mark Brown
2013-08-07 18:48 ` Stephen Warren
2013-08-08 8:30 ` Mark Rutland
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=52026F84.5030204@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=broonie@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=lgirdwood@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.