[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140807094527.GC17528@sirena.org.uk>
Date: Thu, 7 Aug 2014 10:45:27 +0100
From: Mark Brown <broonie@...nel.org>
To: Nicolin Chen <nicoleotsuka@...il.com>
Cc: linux-kernel@...r.kernel.org, linuxppc-dev@...ts.ozlabs.org,
alsa-devel@...a-project.org, timur@...i.org,
Li.Xiubo@...escale.com, devicetree@...r.kernel.org,
galak@...eaurora.org, ijc+devicetree@...lion.org.uk,
mark.rutland@....com, pawel.moll@....com, robh+dt@...nel.org,
b42378@...escale.com, b02247@...escale.com
Subject: Re: [PATCH] ASoC: fsl_sai: Add asynchronous mode support
On Tue, Aug 05, 2014 at 03:32:05PM +0800, Nicolin Chen wrote:
> From: Nicolin Chen <Guangyu.Chen@...escale.com>
>
> SAI supports these operation modes:
> 1) asynchronous mode
> Both Tx and Rx are set to be asynchronous.
> 2) synchronous mode (Rx sync with Tx)
> Tx is set to be asynchronous, Rx is set to be synchronous.
> 3) synchronous mode (Tx sync with Rx)
> Rx is set to be asynchronous, Tx is set to be synchronous.
> 4) synchronous mode (Tx/Rx sync with another SAI's Tx)
> 5) synchronous mode (Tx/Rx sync with another SAI's Rx)
This seems to conflict with something else on my branch - not checked
what. Can you take a look please?
> +Note:
> +- If both fsl,sai-asynchronous and fsl,sai-synchronous-rx are absent, the
> + default synchronous mode (sync Rx with Tx) will be used, which means both
> + transimitter and receiver will send and receive data by following clocks
> + of transimitter.
> +- fsl,sai-asynchronous will be ignored if fsl,sai-synchronous-rx property is
> + already present.
Might be worth printing an error here.
Download attachment "signature.asc" of type "application/pgp-signature" (820 bytes)
Powered by blists - more mailing lists