From: <Codrin.Ciubotariu@microchip.com>
To: <mirq-linux@rere.qmqm.pl>, <alsa-devel@alsa-project.org>,
<devicetree@vger.kernel.org>
Cc: <alexandre.belloni@bootlin.com>, <arnd@arndb.de>,
<3chas3@gmail.com>, <gregkh@linuxfoundation.org>,
<perex@perex.cz>, <lgirdwood@gmail.com>,
<Ludovic.Desroches@microchip.com>, <broonie@kernel.org>,
<mark.rutland@arm.com>, <Nicolas.Ferre@microchip.com>,
<robh-dt@kernel.org>, <tiwai@suse.com>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 6/6] ASoC: atmel_ssc_dai: Enable shared FSYNC source in frame-slave mode
Date: Mon, 26 Aug 2019 15:05:06 +0000 [thread overview]
Message-ID: <a42ede6e-4cc9-6dbf-4c58-71d2298fd3d5@microchip.com> (raw)
In-Reply-To: <b56ebac96ad232e2d9871067b13654eb9223f28f.1566677788.git.mirq-linux@rere.qmqm.pl>
On 24.08.2019 23:26, Michał Mirosław wrote:
> SSC driver allows only synchronous TX and RX. In slave mode for BCLK
> it uses only one of TK or RK pin, but for LRCLK it configured separate
> inputs from TF and RF pins. Allow configuration with common FS signal.
>
> Signed-off-by: Michał Mirosław <mirq-linux@rere.qmqm.pl>
>
> ---
> v2: use alternate DT binding
> split DT and drivers/misc changes
>
> ---
> sound/soc/atmel/atmel_ssc_dai.c | 26 ++++++++++++++++++++++----
> 1 file changed, 22 insertions(+), 4 deletions(-)
>
> diff --git a/sound/soc/atmel/atmel_ssc_dai.c b/sound/soc/atmel/atmel_ssc_dai.c
> index 48e9eef34c0f..035d4da58f2b 100644
> --- a/sound/soc/atmel/atmel_ssc_dai.c
> +++ b/sound/soc/atmel/atmel_ssc_dai.c
> @@ -605,14 +605,32 @@ static int atmel_ssc_hw_params(struct snd_pcm_substream *substream,
> return -EINVAL;
> }
>
> - if (!atmel_ssc_cfs(ssc_p)) {
> + if (atmel_ssc_cfs(ssc_p)) {
> + /*
> + * SSC provides LRCLK
> + *
> + * Both TF and RF are generated, so use them directly.
> + */
> + rcmr |= SSC_BF(RCMR_START, fs_edge);
> + tcmr |= SSC_BF(TCMR_START, fs_edge);
Hmm, how would this work if capture and playback start/run at the same time?
> + } else {
> fslen = fslen_ext = 0;
> rcmr_period = tcmr_period = 0;
> fs_osync = SSC_FSOS_NONE;
> - }
>
> - rcmr |= SSC_BF(RCMR_START, fs_edge);
> - tcmr |= SSC_BF(TCMR_START, fs_edge);
> + if (ssc->lrclk_from_tf_pin) {
> + rcmr |= SSC_BF(RCMR_START, SSC_START_TX_RX);
> + tcmr |= SSC_BF(TCMR_START, fs_edge);
> + } else if (ssc->lrclk_from_rf_pin) {
> + /* assume RF is to be used when RK is used as BCLK input */
This comment is not longer true...
> + /* Note: won't work correctly on SAMA5D2 due to errata */
> + rcmr |= SSC_BF(RCMR_START, fs_edge);
> + tcmr |= SSC_BF(TCMR_START, SSC_START_TX_RX);
> + } else {
> + rcmr |= SSC_BF(RCMR_START, fs_edge);
> + tcmr |= SSC_BF(TCMR_START, fs_edge);
> + }
> + }
>
> if (atmel_ssc_cbs(ssc_p)) {
> /*
>
Thanks and best regards,
Codrin
next prev parent reply other threads:[~2019-08-26 15:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-24 20:26 [PATCH v2 0/6] ] ASoC: atmel: extend SSC support Michał Mirosław
2019-08-24 20:26 ` [PATCH v2 1/6] ASoC: atmel: enable SOC_SSC_PDC and SOC_SSC_DMA in Kconfig Michał Mirosław
2019-08-26 13:45 ` Codrin.Ciubotariu
2019-08-26 14:23 ` Alexandre Belloni
2019-08-24 20:26 ` [PATCH v2 2/6] ASoC: atmel_ssc_dai: rework DAI format configuration Michał Mirosław
2019-08-26 14:04 ` Codrin.Ciubotariu
2019-08-24 20:26 ` [PATCH v2 3/6] ASoC: atmel_ssc_dai: implement left-justified data mode Michał Mirosław
2019-08-26 14:10 ` Codrin.Ciubotariu
2019-08-24 20:26 ` [PATCH v2 4/6] dt-bindings: misc: atmel-ssc: LRCLK from TF/RF pin option Michał Mirosław
2019-08-27 22:37 ` Rob Herring
2019-08-28 13:02 ` Michał Mirosław
2019-08-28 18:34 ` Rob Herring
2019-08-24 20:26 ` [PATCH v2 5/6] misc: atmel-ssc: get LRCLK pin selection from DT Michał Mirosław
2019-08-26 14:38 ` Codrin.Ciubotariu
2019-08-24 20:26 ` [PATCH v2 6/6] ASoC: atmel_ssc_dai: Enable shared FSYNC source in frame-slave mode Michał Mirosław
2019-08-26 15:05 ` Codrin.Ciubotariu [this message]
2019-09-08 13:39 ` mirq-linux
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=a42ede6e-4cc9-6dbf-4c58-71d2298fd3d5@microchip.com \
--to=codrin.ciubotariu@microchip.com \
--cc=3chas3@gmail.com \
--cc=Ludovic.Desroches@microchip.com \
--cc=Nicolas.Ferre@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=alsa-devel@alsa-project.org \
--cc=arnd@arndb.de \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mirq-linux@rere.qmqm.pl \
--cc=perex@perex.cz \
--cc=robh-dt@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).