From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: ZH Tu <tuzhihe@pcasl.com>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: Re: Intel Cherry Trail -- No sound in linux
Date: Mon, 14 Dec 2015 16:54:36 -0600 [thread overview]
Message-ID: <566F48AC.7010801@linux.intel.com> (raw)
In-Reply-To: <2015121216254115203520@pcasl.com>
On 12/12/15 2:25 AM, ZH Tu wrote:
> As Pierre suggestions:
>
> try to enable a DSP loopback to see if the data isn't garbled by the driver
> amixer cset "name='pcm1_out mix 0 pcm0_in" on
>
> But we all know that the stream path is power on automaticlly, so even I do the mixer setting, the pcm1_out wighet still is in power off state.
>
> So is there way to do the loopback?
You need to do this on top of regular playback/capture settings
otherwise yes DAPM will not power anything.
You can also try to do a loopback inside of the codec, i used this
recently to create a mic-to-speaker loopback/larsen and show that the
speakers were functional.
>
> Now every time I do the test:
> aplay test.wav
>
> I get the error message:
> [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe C (start=46633 end=46634)
>
> And there're no more errors.
>
> From the message I guess the pipe used by intel drm is blocked, so as to the pipe used by SST firmware, that's why I cannot get data from DACDAT pin.
>
> This bug confused me for a long time, can anyone give some suggestions?
Apart from a bad configuration related to HDMI, this seems mostly
unrelated to codec link issues.
next prev parent reply other threads:[~2015-12-14 22:54 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
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 [this message]
-- 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=566F48AC.7010801@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 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.