From: Mark Brown <broonie@kernel.org>
To: Rob Herring <robh@kernel.org>
Cc: Felipe Ferreri Tonello <eu@felipetonello.com>,
Linux-ALSA <alsa-devel@alsa-project.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Takashi Iwai <tiwai@suse.com>
Subject: Re: [PATCH] ASoC: fsl: add imx-cs427x machine driver
Date: Tue, 26 Jan 2016 16:03:33 +0000 [thread overview]
Message-ID: <20160126160333.GD6042@sirena.org.uk> (raw)
In-Reply-To: <CAL_JsqJxQjw5yWmnUAev4e+pa601stcH-W-srbDCeRYOabJrOg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 802 bytes --]
On Tue, Jan 26, 2016 at 09:50:46AM -0600, Rob Herring wrote:
> On Tue, Jan 26, 2016 at 3:43 AM, Felipe Ferreri Tonello
> >> This should be an exact list of possible strings and valid combinations.
No, there is no sense in trying to document all possible combinations as
this would result in so many combinations that it would dominate the
documentation. The restrictions should all come from the physical
limitations of what you can connect and should therefore be sufficiently
obvious from their definition.
> > This is the exact list for this version of this driver. At least that is
> > what I can verify on my hardware (custom build).
> What are AINA, AINB, etc. then?
These are CODEC pins and should be documented in the CODEC binding
rather than repeated for every machine using the CODEC.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
prev parent reply other threads:[~2016-01-26 16:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-25 17:53 [PATCH] ASoC: fsl: add imx-cs427x machine driver Felipe F. Tonello
[not found] ` <1453744403-12268-1-git-send-email-eu-NLnRV5p3vwDxYxTyqlRmvgC/G2K4zDHf@public.gmane.org>
2016-01-26 2:29 ` Rob Herring
2016-01-26 9:43 ` Felipe Ferreri Tonello
[not found] ` <56A73FDE.2060607-NLnRV5p3vwDxYxTyqlRmvgC/G2K4zDHf@public.gmane.org>
2016-01-26 9:47 ` Fabio Estevam
[not found] ` <CAOMZO5BjeDMqNgf-=tE7=pByJi+jJVA=G2bbtp+XJeYbpev6KA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-01-26 11:01 ` Felipe Ferreri Tonello
[not found] ` <56A75205.8060000-NLnRV5p3vwDxYxTyqlRmvgC/G2K4zDHf@public.gmane.org>
2016-01-26 11:05 ` Fabio Estevam
[not found] ` <CAOMZO5CjVxAHOJSywveK7dYvdz8PSMADJd1F7TdO+asEQ89XTg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-01-26 17:42 ` Nicolin Chen
2016-01-31 13:28 ` Fabio Estevam
2016-01-26 11:50 ` Mark Brown
2016-01-26 15:50 ` Rob Herring
2016-01-26 16:03 ` Mark Brown [this message]
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=20160126160333.GD6042@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=devicetree@vger.kernel.org \
--cc=eu@felipetonello.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=tiwai@suse.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).