From: Nicolin Chen <firstname.lastname@example.org> To: Fabio Estevam <email@example.com> Cc: "firstname.lastname@example.org" <email@example.com>, Arnaud Mouiche <firstname.lastname@example.org>, Timur Tabi <email@example.com>, Caleb Crome <firstname.lastname@example.org>, Mark Brown <email@example.com>, Max Krummenacher <firstname.lastname@example.org>, Fabio Estevam <email@example.com>, Sascha Hauer <firstname.lastname@example.org> Subject: Re: [PATCH v2] ASoC: fsl_ssi: Fix channel swap on playback start Date: Mon, 3 Apr 2017 17:08:23 -0700 [thread overview] Message-ID: <20170404000823.GB23047@Asurada-Nvidia> (raw) In-Reply-To: <CAOMZO5AZm5w69033PKd+PTQARZaujO9H_n7YtQ7hnGESefvd4A@mail.gmail.com> On Mon, Apr 03, 2017 at 07:54:26PM -0300, Fabio Estevam wrote: > Hi Nicolin, > > On Mon, Apr 3, 2017 at 7:36 PM, Nicolin Chen <email@example.com> wrote: > > > My extra concern for this change is that ENGcm06222 suggests to > > set TE and SSIEN together. However, we are still not setting the > > SSIEN and TE together -- SSIEN is set already before this line > > in the "ssi_private->use_dma && (vals->scr & CCSR_SSI_SCR_TE)". > > > > On the other hand, ENGcm06222 doesn't mention anything related > > to the RE bit. Although ENGcm06474 suggests to set TE and RE > > together, yet it's for another bug (when TE is set after RE, the > > TX channels might be swapped.) > > The idea for this patch came from commit f8fdf5375e2005 ("ASoC: > fsl-ssi: add SSIEN errata work around"). I understand what's this patch doing. > In this commit SSIEN, TE and RE are written at the same time as a > workaround to ENGcm06222 and ENGcm06532 from the errata document. Are you sure? Because there is a line of code set SSIEN separately right before the line that this patch applies to. So this patch actually only applies the workaround for ENGcm06532 (the bug when setting RX prior to TX.) > Seems to cause other issues though as reported by Caleb and Arnaud, so > we need to find other way to solve this. > > Then, the test case: aplay swap_test.wav& sleep 1; killall aplay > > > > It doesn't involve RE at all. So I don't get why setting RE and > > TE together after setting SSIEN (three bits are not set together > > here.) could solve the channel swapping problem for a test case > > which has never involved RE at all. Am I missing something? > > Your understanding is correct. In my usecase there is no audio capture > involved at all, just stereo audio playback. > > The only explanation I can give is the same one from commit > f8fdf5375e2005 ("ASoC: fsl-ssi: add SSIEN errata work around"). I don't think that's an explanation. For non-AC97 cases, we are not setting SSIEN and TE together at all, even by applying this change. > Do you have access to any imx board with SSI? I do. Will try to test it later.
prev parent reply other threads:[~2017-04-04 0:08 UTC|newest] Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-04-01 14:48 Fabio Estevam 2017-04-01 15:13 ` Arnaud Mouiche 2017-04-01 16:03 ` Fabio Estevam 2017-04-03 8:19 ` Max Krummenacher 2017-04-03 20:32 ` Caleb Crome 2017-04-03 20:50 ` Caleb Crome 2017-04-03 21:53 ` Fabio Estevam 2017-04-03 22:05 ` Arnaud Mouiche 2017-04-03 22:20 ` Nicolin Chen 2017-04-03 23:22 ` Caleb Crome 2017-04-03 23:40 ` Fabio Estevam 2017-04-03 23:42 ` Caleb Crome 2017-04-04 8:59 ` Arnaud Mouiche 2017-04-04 9:03 ` Arnaud Mouiche 2017-04-04 11:38 ` Fabio Estevam 2017-04-04 17:12 ` Fabio Estevam 2017-04-04 20:09 ` Arnaud Mouiche 2017-04-04 20:28 ` Fabio Estevam 2017-04-05 7:54 ` Arnaud Mouiche 2017-04-05 13:43 ` Fabio Estevam 2017-04-05 14:04 ` Max Krummenacher 2017-04-03 22:08 ` Nicolin Chen 2017-04-03 23:31 ` Caleb Crome 2017-04-03 23:55 ` Nicolin Chen 2017-04-04 0:07 ` Timur Tabi 2017-04-04 0:39 ` Caleb Crome 2017-04-04 1:25 ` Nicolin Chen 2017-04-03 22:36 ` Nicolin Chen 2017-04-03 22:54 ` Fabio Estevam 2017-04-04 0:08 ` Nicolin Chen [this message]
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=20170404000823.GB23047@Asurada-Nvidia \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: [PATCH v2] ASoC: fsl_ssi: Fix channel swap on playback start' \ /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
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.