From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Stephen Warren <swarren@nvidia.com>
Cc: Leon Romanovsky <leon@leon.nu>, "lrg@ti.com" <lrg@ti.com>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"olof@lixom.net" <olof@lixom.net>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"grant.likely@secretlab.ca" <grant.likely@secretlab.ca>,
"rob.herring@calxeda.com" <rob.herring@calxeda.com>,
"rdunlap@xenotime.net" <rdunlap@xenotime.net>,
"devicetree-discuss@lists.ozlabs.org"
<devicetree-discuss@lists.ozlabs.org>
Subject: Re: [PATCH 3/5] ASoC: Tegra+ALC5632 machine: Add device tree binding documentation
Date: Tue, 31 Jan 2012 19:38:14 +0000 [thread overview]
Message-ID: <20120131193810.GD3429@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <74CDBE0F657A3D45AFBB94109FB122FF178E124438@HQMAIL01.nvidia.com>
[-- Attachment #1: Type: text/plain, Size: 719 bytes --]
On Tue, Jan 31, 2012 at 09:52:42AM -0800, Stephen Warren wrote:
> Hmm, actually the block diagram and "pin assignment" diagram are
> inconsistent, e.g. AUX_OUTP+AUX_OUTN in the block diagram vs.
> AUX_OUT+AUX_OUTN in the pin assignment, or PHONE_N (block diagram) vs.
> PHONEN (pin assignments).
> Mark, do you care about this level of detail? I think we should use the
> names in the pin assignments section if we do change this patch, but I
> guess things are clear enough as it stands, so I'm not excessively
> bothered.
Not really, especially if the datasheet doesn't agree with itself. This
is the sort of thing that can vary between revisions of the datasheet
anyway, so long as it's clear we should be fine.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-01-31 19:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-31 7:30 [PATCH 3/5] ASoC: Tegra+ALC5632 machine: Add device tree binding documentation Leon Romanovsky
2012-01-31 17:52 ` Stephen Warren
2012-01-31 19:38 ` Mark Brown [this message]
[not found] ` <1327995040-27152-1-git-send-email-leon-2ukJVAZIZ/Y@public.gmane.org>
2012-01-31 11:27 ` Mark Brown
[not found] ` <20120131112706.GE18444-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
2012-01-31 11:51 ` Leon Romanovsky
[not found] ` <CALq1K=JbPspu2ShkfgcvQ_+cw6kxZNxe_zUdwrz3Sfn3YFv_rg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-01-31 11:53 ` Mark Brown
2012-01-31 19:39 ` 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=20120131193810.GD3429@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=leon@leon.nu \
--cc=linux-doc@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=lrg@ti.com \
--cc=olof@lixom.net \
--cc=rdunlap@xenotime.net \
--cc=rob.herring@calxeda.com \
--cc=swarren@nvidia.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).