From: Mark Brown <broonie@kernel.org>
To: Bo Shen <voice.shen@atmel.com>
Cc: nicolas.ferre@atmel.com, linux-sound@vger.kernel.org,
alsa-devel@alsa-project.org,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v2 2/4] ASoC: atmel_ssc_dai: enable fslen extension feature
Date: Sat, 21 Jun 2014 10:37:56 +0000 [thread overview]
Message-ID: <20140621103756.GA5099@sirena.org.uk> (raw)
In-Reply-To: <1402481682-9811-3-git-send-email-voice.shen@atmel.com>
[-- Attachment #1: Type: text/plain, Size: 395 bytes --]
On Wed, Jun 11, 2014 at 06:14:40PM +0800, Bo Shen wrote:
> When SSC work as master, it will generate the frame sync signal.
> On old SoCs, it only supports frame sync length less or equal to
> 16bits, on newer SoCs, it supports frame sync length extension,
> which can support frame size larger than 16 bits.
> So, add this to make it supports playback 24/32 bits audio clips.
Applied, thanks.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-06-21 10:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-11 10:14 [PATCH v2 0/4] ASoC: atmel_ssc: enable fslen extension feature Bo Shen
2014-06-11 10:14 ` [PATCH v2 1/4] ASoC: atmel-ssc: distinguish whether SSC supports fslen ext Bo Shen
2014-06-11 10:25 ` Nicolas Ferre
2014-06-21 10:37 ` Mark Brown
2014-06-11 10:14 ` [PATCH v2 2/4] ASoC: atmel_ssc_dai: enable fslen extension feature Bo Shen
2014-06-21 10:37 ` Mark Brown [this message]
2014-06-11 10:14 ` [PATCH v2 3/4] dts: atmel: at91sam9rl: switch ssc compatible string Bo Shen
2014-09-02 9:15 ` Nicolas Ferre
2014-06-11 10:14 ` [PATCH v2 4/4] dts: atmel: at91sam9g20: " Bo Shen
2014-09-02 9:14 ` Nicolas Ferre
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=20140621103756.GA5099@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-sound@vger.kernel.org \
--cc=nicolas.ferre@atmel.com \
--cc=voice.shen@atmel.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