From: Nicolin Chen <nicoleotsuka@gmail.com>
To: Arnaud Mouiche <arnaud.mouiche@invoxia.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
Sascha Hauer <kernel@pengutronix.de>, Timur Tabi <timur@tabi.org>,
Caleb Crome <caleb@crome.org>, Mark Brown <broonie@kernel.org>,
Max Krummenacher <max.krummenacher@toradex.com>,
Fabio Estevam <fabio.estevam@nxp.com>,
Fabio Estevam <festevam@gmail.com>
Subject: Re: [PATCH v2] ASoC: fsl_ssi: Fix channel swap on playback start
Date: Mon, 3 Apr 2017 15:20:14 -0700 [thread overview]
Message-ID: <20170403222013.GB21156@Asurada-Nvidia> (raw)
In-Reply-To: <a572220b-5bbd-9e47-31c4-ba272c5d28e7@invoxia.com>
On Tue, Apr 04, 2017 at 12:05:57AM +0200, Arnaud Mouiche wrote:
> The Patch break something. I'm not even able to to make two
> consecutives 'aplay' in order to generate something correct on the
> external SSI bus.
> - boot
> - aplay -D hw:1,0 -r 48000 -c 2 -f S16_LE /dev/urandom
> Playing raw data '/dev/urandom' : Signed 16 bit Little Endian, Rate
> 48000 Hz, Stereo
> ^CAborted by signal Interrupt...
>
> => ok
>
> - aplay -D hw:1,0 -r 48000 -c 2 -f S16_LE /dev/urandom
> Playing raw data '/dev/urandom' : Signed 16 bit Little Endian, Rate
> 48000 Hz, Stereo
> aplay: pcm_write:1702: write error: Input/output error
>
> => no clock on external bus.
It's probably because of the nr_active_streams and keep_active in
the fsl_ssi_config() are not working correctly any more since the
TE abd RE are always set -- wondering why Fabio and Max don't see
any problem; is there any diff between vanilla and -next?
next prev parent reply other threads:[~2017-04-03 22:20 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-01 14:48 [PATCH v2] ASoC: fsl_ssi: Fix channel swap on playback start 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 [this message]
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
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=20170403222013.GB21156@Asurada-Nvidia \
--to=nicoleotsuka@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=arnaud.mouiche@invoxia.com \
--cc=broonie@kernel.org \
--cc=caleb@crome.org \
--cc=fabio.estevam@nxp.com \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=max.krummenacher@toradex.com \
--cc=timur@tabi.org \
/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 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.