linux-kernel - Re: [PATCH v5 1/2] ASoC: qcom: document apq8016 sbc machine driver bindings

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 09 Jun 2015 18:08:24 +0100
From:	Srinivas Kandagatla <srinivas.kandagatla@...aro.org>
To:	Mark Brown <broonie@...nel.org>
CC:	alsa-devel@...a-project.org, Rob Herring <robh+dt@...nel.org>,
	Patrick Lai <plai@...eaurora.org>,
	Banajit Goswami <bgoswami@...eaurora.org>,
	Liam Girdwood <lgirdwood@...il.com>,
	Jaroslav Kysela <perex@...ex.cz>, Takashi Iwai <tiwai@...e.de>,
	devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
	kwestfie@...eaurora.org, linux-arm-msm@...r.kernel.org
Subject: Re: [PATCH v5 1/2] ASoC: qcom: document apq8016 sbc machine driver
 bindings



On 09/06/15 17:57, Mark Brown wrote:
> On Tue, Jun 09, 2015 at 01:59:29PM +0100, Srinivas Kandagatla wrote:
>
>> >+Optional CPU/CODEC subnodes properties:
>> >+- external	: flag to indicate if the I2S is connected to external codec
>> >+Example:
> Missing blank line between the property and the "Example:".  I'm still
I will fix it in next version.
> not sure I understand why we need a boolean property indicating if an
> external CODEC is in use - what is the consequence of setting this
> property?
As of today, the consequence of setting this flag is to setup correct 
dai_link names.
Also there are some limitations on which MI2S can be configured to 
external or internal codecs, this flag can be used in future to validate 
such configurations, if required.

--srini
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/