From: Caesar Wang <wxt@rock-chips.com>
To: Heiko Stuebner <heiko@sntech.de>, Mark Brown <broonie@kernel.org>
Cc: kmixter@chromium.org, Sonny Rao <sonnyrao@chromium.org>,
Doug Anderson <dianders@chromium.org>,
linux-rockchip@lists.infradead.org,
Dylan Reid <dgreid@chromium.org>,
benchan@chromium.org, Cheng-Yi Chiang <cychiang@chromium.org>,
Caesar Wang <wxt@rock-chips.com>,
Jaroslav Kysela <perex@perex.cz>,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
Takashi Iwai <tiwai@suse.com>,
Liam Girdwood <lgirdwood@gmail.com>,
linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 3/3] ASoC: rockchip-rt5645: Allow more sample rates
Date: Fri, 6 Nov 2015 19:38:16 +0800 [thread overview]
Message-ID: <1446809896-11254-4-git-send-email-wxt@rock-chips.com> (raw)
In-Reply-To: <1446809896-11254-1-git-send-email-wxt@rock-chips.com>
The RT5645 audio codec support sample rates from 8 to 96 kHz
as the dai claim.
Signed-off-by: Caesar Wang <wxt@rock-chips.com>
---
Changes in v2:
- add the 64000 sample rate for rt5645.
sound/soc/rockchip/rockchip_rt5645.c | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/sound/soc/rockchip/rockchip_rt5645.c b/sound/soc/rockchip/rockchip_rt5645.c
index 68c62e4..440a802 100644
--- a/sound/soc/rockchip/rockchip_rt5645.c
+++ b/sound/soc/rockchip/rockchip_rt5645.c
@@ -79,11 +79,17 @@ static int rk_aif1_hw_params(struct snd_pcm_substream *substream,
switch (params_rate(params)) {
case 8000:
case 16000:
+ case 24000:
+ case 32000:
case 48000:
+ case 64000:
case 96000:
mclk = 12288000;
break;
+ case 11025:
+ case 22050:
case 44100:
+ case 88200:
mclk = 11289600;
break;
default:
--
1.9.1
prev parent reply other threads:[~2015-11-06 11:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-06 11:38 [PATCH v2 0/3] Support more sample rates, let the rates normal work Caesar Wang
2015-11-06 11:38 ` [PATCH v2 1/3] ASoC: rockchip: i2s: change bclk and lrck according to sample rates Caesar Wang
2015-11-06 11:38 ` [PATCH v2 2/3] ASoC: rockchip-max98090: Allow more " Caesar Wang
2015-11-06 11:38 ` Caesar Wang [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=1446809896-11254-4-git-send-email-wxt@rock-chips.com \
--to=wxt@rock-chips.com \
--cc=alsa-devel@alsa-project.org \
--cc=benchan@chromium.org \
--cc=broonie@kernel.org \
--cc=cychiang@chromium.org \
--cc=dgreid@chromium.org \
--cc=dianders@chromium.org \
--cc=heiko@sntech.de \
--cc=kmixter@chromium.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=perex@perex.cz \
--cc=sonnyrao@chromium.org \
--cc=tiwai@suse.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