From: Mark Brown <broonie@kernel.org>
To: Nicolin Chen <nicoleotsuka@gmail.com>
Cc: alsa-devel@alsa-project.org, scerveau@voxtok.com,
linuxppc-dev@lists.ozlabs.org, timur@tabi.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ASoC: fsl_ssi: Fix the incorrect limitation of the bit clock rate
Date: Wed, 11 Feb 2015 13:46:16 +0800 [thread overview]
Message-ID: <20150211054616.GR2593@finisterre.sirena.org.uk> (raw)
In-Reply-To: <1423632703-3683-1-git-send-email-nicoleotsuka@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 227 bytes --]
On Tue, Feb 10, 2015 at 09:31:43PM -0800, Nicolin Chen wrote:
> According to i.MX Reference Manual, the bit-clock frequency generated
> by SSI must be never greater than 1/5 of the peripheral clock frequency.
Applied, thanks.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
prev parent reply other threads:[~2015-02-11 6:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-11 5:31 [PATCH] ASoC: fsl_ssi: Fix the incorrect limitation of the bit clock rate Nicolin Chen
2015-02-11 5:46 ` Mark Brown [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=20150211054616.GR2593@finisterre.sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=nicoleotsuka@gmail.com \
--cc=scerveau@voxtok.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox