From: "arnaud.mouiche@invoxia.com" <arnaud.mouiche@invoxia.com>
To: Anatol Pomozov <anatol.pomozov@gmail.com>, alsa-devel@alsa-project.org
Cc: liam.r.girdwood@linux.intel.com, albertchen@realtek.com,
broonie@kernel.org, lars@metafoo.de
Subject: Re: [PATCH] ASoC: Document DAI signal polarity
Date: Tue, 1 Sep 2015 09:20:31 +0200 [thread overview]
Message-ID: <55E551BF.9000304@invoxia.com> (raw)
In-Reply-To: <1441054258-33200-1-git-send-email-anatol.pomozov@gmail.com>
So, this example is a "normal" FSYNC, "normal" BCLK, DSP-B mode, 16
bits/sample, isn't it (just to have something visual).
regards,
arnaud
--+ +--+ +--+ +--+ +--+ +--+ +--+ +--
| | | | | | | | | | | | | | ...
+--+ +--+ +--+ +--+ +--+ +--+ +--+
+-----+
| |
--------------+ +------------------------ ...
| b1 | b0 | b15 | b14 | b13 | b12 | b11 | ...
--frame N-1--> <----- frame N ---------
Le 31/08/2015 22:50, Anatol Pomozov a écrit :
> Per discussion at [1] currently there is no clear definition of what is FSYNC polarity.
> Different drivers use its own definition of what is "normal" and what is "inverted"
> fsync in different modes. This leads to compatibility problems between drivers.
>
> Explicitly specify meaning of BCLK/FSYNC polarity.
>
> [1] http://mailman.alsa-project.org/pipermail/alsa-devel/2015-August/097121.html
>
> Signed-off-by: Anatol Pomozov <anatol.pomozov@gmail.com>
> ---
> include/sound/soc-dai.h | 11 ++++++++---
> 1 file changed, 8 insertions(+), 3 deletions(-)
>
> diff --git a/include/sound/soc-dai.h b/include/sound/soc-dai.h
> index 2df96b1..c8170c4 100644
> --- a/include/sound/soc-dai.h
> +++ b/include/sound/soc-dai.h
> @@ -48,10 +48,15 @@ struct snd_compr_stream;
> #define SND_SOC_DAIFMT_GATED (0 << 4) /* clock is gated */
>
> /*
> - * DAI hardware signal inversions.
> + * DAI hardware signal polarity.
> *
> - * Specifies whether the DAI can also support inverted clocks for the specified
> - * format.
> + * For BCLK:
> + * - "normal" polarity means signal sensing happens at rising edge of BCLK
> + * - "inverted" polarity means signal sensing happens at falling edge of BCLK
> + *
> + * For FSYNC:
> + * - "normal" polarity means frame starts at rising edge of FSYNC
> + * - "inverted" polarity means frame starts at falling edge of FSYNC
> */
> #define SND_SOC_DAIFMT_NB_NF (0 << 8) /* normal bit clock + frame */
> #define SND_SOC_DAIFMT_NB_IF (2 << 8) /* normal BCLK + inv FRM */
next prev parent reply other threads:[~2015-09-01 7:20 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-31 20:50 [PATCH] ASoC: Document DAI signal polarity Anatol Pomozov
2015-09-01 1:27 ` Albert Chen
2015-09-01 7:20 ` arnaud.mouiche [this message]
2015-09-18 13:54 ` Mark Brown
2015-09-29 21:34 ` Anatol Pomozov
2015-09-30 18:10 ` Mark Brown
2015-09-30 19:08 ` Anatol Pomozov
2015-09-30 19:22 ` Benoît Thébaudeau
2015-09-30 22:33 ` Mark Brown
2015-09-30 19:28 ` Mark Brown
2015-09-30 19:34 ` Lars-Peter Clausen
-- strict thread matches above, loose matches on Subject: below --
2015-10-01 18:09 Anatol Pomozov
2015-10-01 19:18 ` Benoît Thébaudeau
2015-10-05 15:12 ` Mark Brown
2015-10-05 19:20 ` Benoît Thébaudeau
2015-10-06 9:33 ` Mark Brown
2015-10-02 15:33 Anatol Pomozov
2015-10-02 17:01 ` Benoît Thébaudeau
2015-10-08 16:37 Anatol Pomozov
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=55E551BF.9000304@invoxia.com \
--to=arnaud.mouiche@invoxia.com \
--cc=albertchen@realtek.com \
--cc=alsa-devel@alsa-project.org \
--cc=anatol.pomozov@gmail.com \
--cc=broonie@kernel.org \
--cc=lars@metafoo.de \
--cc=liam.r.girdwood@linux.intel.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