From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Timur Tabi <timur@freescale.com>
Cc: Fabio Estevam <fabio.estevam@freescale.com>,
alsa-devel@alsa-project.org, Fabio Estevam <festevam@gmail.com>,
javier.martin@vista-silicon.com,
Sascha Hauer <kernel@pengutronix.de>
Subject: Re: [PATCH 1/2] ASoC: fsl_ssi: Let it understand mono
Date: Sat, 22 Sep 2012 10:56:20 -0400 [thread overview]
Message-ID: <20120922145619.GB4495@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <505A3DDB.4060208@freescale.com>
On Wed, Sep 19, 2012 at 04:49:15PM -0500, Timur Tabi wrote:
> I still have seen no explanation as to how mono audio can work on an I2S
> device. The I2S standard calls for a left and right channel in every
> sample, and the playback frequency is based on that sample rate.
In I2S mono just means ignoring the right channel or duplicating the
left channel into the right channel at one end of the link or the other.
As you say the clocking always has to be for an even number of channels.
next prev parent reply other threads:[~2012-09-22 14:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-18 16:03 [PATCH 1/2] ASoC: fsl_ssi: Let it understand mono Fabio Estevam
2012-09-18 16:03 ` [PATCH 2/2] ASoC: cs4270: Remove mono support Fabio Estevam
2012-09-24 13:49 ` Timur Tabi
2012-09-25 12:53 ` Mark Brown
2012-09-25 17:22 ` UAC2 device recognized during boot but won't output sound Joao Bonina
2012-09-18 16:14 ` [PATCH 1/2] ASoC: fsl_ssi: Let it understand mono Timur Tabi
2012-09-19 14:07 ` Fabio Estevam
2012-09-19 21:49 ` Timur Tabi
2012-09-22 14:56 ` Mark Brown [this message]
2012-09-24 13:50 ` Timur Tabi
2012-09-25 12:53 ` Mark Brown
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=20120922145619.GB4495@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=fabio.estevam@freescale.com \
--cc=festevam@gmail.com \
--cc=javier.martin@vista-silicon.com \
--cc=kernel@pengutronix.de \
--cc=timur@freescale.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).