linux-kernel - Re: [PATCH 2/5] mfd: arizona: Add device tree binding for max_channels

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:	Mon, 23 Sep 2013 15:38:10 -0600
From:	Stephen Warren <swarren@...dotorg.org>
To:	Charles Keepax <ckeepax@...nsource.wolfsonmicro.com>
CC:	lee.jones@...aro.org, sameo@...ux.intel.com,
	rob.herring@...xeda.com, pawel.moll@....com, mark.rutland@....com,
	ijc+devicetree@...lion.org.uk, rob@...dley.net, broonie@...nel.org,
	patches@...nsource.wolfsonmicro.com, devicetree@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/5] mfd: arizona: Add device tree binding for max_channels_clocked

On 09/23/2013 12:30 PM, Charles Keepax wrote:
> Add device tree bindings for the pdata max_channels_clocked, that allows
> the user to limit the number of channels clocked on a single AIF.

> diff --git a/Documentation/devicetree/bindings/mfd/arizona.txt b/Documentation/devicetree/bindings/mfd/arizona.txt

> +  - wlf,max-channels-clocked : The maximum number of channels to be clocked on
> +    each AIF, useful for I2S systems with multiple data lines being mastered.
> +    If specified three cells must supplied one for each AIF, specify zero for
> +    AIFs that should be handled normally.

What determines the value of this property? Is it really a definition of
HW, or some kind of run-time configuration/limit? What goes into each of
the 3 cells?
--
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/