From: Qiao Zhou <zhouqiao@marvell.com>
To: Mark Brown <broonie@kernel.org>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
Eric Miao <eric.y.miao@gmail.com>, Takashi Iwai <tiwai@suse.de>,
Liam Girdwood <lgirdwood@gmail.com>,
Haojian Zhuang <haojian.zhuang@gmail.com>,
"trinity.qiao.zhou@gmail.com" <trinity.qiao.zhou@gmail.com>,
Chao Xie <cxie4@marvell.com>
Subject: Re: [PATCH V0] ASoC: pxa-ssp: add TISSP mode support
Date: Sun, 10 Nov 2013 09:50:21 +0800 [thread overview]
Message-ID: <527EE65D.3070804@marvell.com> (raw)
In-Reply-To: <20131108101948.GD2493@sirena.org.uk>
On 11/08/2013 06:19 PM, Mark Brown wrote:
> On Fri, Nov 08, 2013 at 09:52:16AM +0800, Qiao Zhou wrote:
>> On 11/06/2013 07:24 PM, Mark Brown wrote:
>
>>> What is TISSP mode in an audio context?
>
>> It's normal SSP mode, and it has a pulse of one bit clock width,
>
> OK, what is SSP mode?
SSP mode is just one frame format defined in sscr0 register, and there
are 3 other mode, such as SPI mode, National Semiconductor
Microwire(NSM) mode, Programmable Serial Protocol(PSP) mode.
The SPI/NSM are not used for audio usage, and currently only PSP mode is
used pxa-ssp driver. We have the requirement now to support this SSP
mode. The benefit is that we don't need to configure detailed timing in
transmit/receiving since HW handles it automatically.
The SSP mode is something like the PCM format for mono stream for voice
related scenario. In current audio format definition and pxa-ssp driver
implementation, I don't find suitable way to handle it. so I add such
SSP-format to differentiate it from PSP mode. Do I make a confusion of
SSP mode and audio frame format? please help comment. thanks.
>
--
Best Regards
Qiao
next prev parent reply other threads:[~2013-11-10 1:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-05 8:30 [PATCH V0] ASoC: pxa-ssp: add TISSP mode support Qiao Zhou
2013-11-06 11:24 ` Mark Brown
2013-11-08 1:52 ` Qiao Zhou
2013-11-08 10:19 ` Mark Brown
2013-11-10 1:50 ` Qiao Zhou [this message]
2013-11-10 11:10 ` Mark Brown
2013-11-11 2:03 ` Qiao Zhou
2013-11-11 11:21 ` Mark Brown
2013-11-15 8:57 ` Qiao Zhou
2013-11-10 9:29 ` Daniel Mack
2013-11-11 1:59 ` Qiao Zhou
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=527EE65D.3070804@marvell.com \
--to=zhouqiao@marvell.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=cxie4@marvell.com \
--cc=eric.y.miao@gmail.com \
--cc=haojian.zhuang@gmail.com \
--cc=lgirdwood@gmail.com \
--cc=tiwai@suse.de \
--cc=trinity.qiao.zhou@gmail.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 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.