From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Zhihe Tu <tuzhihe@pcasl.com>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: Re: Intel Cherry Trail -- No sound in linux
Date: Thu, 12 Nov 2015 11:20:44 -0600 [thread overview]
Message-ID: <5644CA6C.5000302@linux.intel.com> (raw)
In-Reply-To: <201511121444557079740@pcasl.com>
> Yes，I got firmware fw_sst_22a8.bin from http://git.kernel.org/cgit/linux/kernel/git/firmware/linux-firmware.git -b BSW.
>
> From the source code of cht_bsw_rt5672.c and rt5672.c, the codec should support S24_LE format, but I found S16_LE is the only format that supported by the codec (from the hw_param).
>
> So the format S16_LE issue will influence the sst firmare ?
Probably not. look in cht_codec_init() the tdm slots are configured with
24 bit outputs.
So far it's not clear how far you've got with your series of emails. Did
you do past the firmware timeout? Did you get past the prepare step with
all mixers configured? Is there no sound despite the data streaming
normally?
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2015-11-12 17:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-10 8:38 Intel Cherry Trail -- No sound in linux Zhihe Tu
2015-11-10 19:00 ` Pierre-Louis Bossart
2015-11-12 6:45 ` Zhihe Tu
2015-11-12 17:20 ` Pierre-Louis Bossart [this message]
2015-11-16 7:43 ` ZH Tu
2015-11-17 1:54 ` Pierre-Louis Bossart
2015-12-12 8:25 ` ZH Tu
2015-12-14 22:54 ` Pierre-Louis Bossart
-- strict thread matches above, loose matches on Subject: below --
2015-11-09 3:21 Zhihe Tu
2015-11-11 16:04 ` Pierre-Louis Bossart
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=5644CA6C.5000302@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=tuzhihe@pcasl.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).