All of lore.kernel.org
 help / color / mirror / Atom feed
From: ZH Tu <tuzhihe@pcasl.com>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
	"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: Re: Intel Cherry Trail -- No sound in linux
Date: Sat, 12 Dec 2015 16:25:46 +0800	[thread overview]
Message-ID: <2015121216254115203520@pcasl.com> (raw)
In-Reply-To: 564A88C9.7020008@linux.intel.com

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?


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?

Thanks


Zhihe Tu
 
From: Pierre-Louis Bossart
Date: 2015-11-17 09:54
To: alsa-devel@alsa-project.org; tuzhihe@pcasl.com
Subject: Re: [alsa-devel] Intel Cherry Trail -- No sound in linux
 
On 11/16/2015 01:43 AM, ZH Tu wrote:
> Hi Pierre-Louis, thanks for your reply.
> 
> Maybe I am not make myself clear. 
> 
> Actually I refer some configure from baytrail platform:
> amixer -c0 sset 'codec_out0 mix 0 pcm0_in' on
> amixer -c0 sset 'media0_out mix 0 media1_in' on
> amixer -c0 sset 'media1_in Gain 0' 80% 
> amixer -c0 sset 'media1_in Gain 0 Ramp Delay' 50
> amixer -c0 sset 'media1_in Gain 0' off
> amixer -c0 sset 'pcm0_in Gain 0' 80% 
> amixer -c0 sset 'pcm0_in Gain 0 Ramp Delay' 50
> amixer -c0 sset 'pcm0_in Gain 0' off
> amixer -c0 sset 'codec_out0 Gain 0' 80%
> amixer -c0 sset 'codec_out0 Gain 0 Ramp Delay' 50
> amixer -c0 sset 'codec_out0 Gain 0' off
> 
> Also there're some settings for the RT5672 codec, but I do not remember now.
 
it seems that the link is active with no data? Couple of suggestions:
 
1. 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
 
2. try a loopback from capture to playback to see if the data sampled by the codec can be played out.
amixer -c0 sset 'codec_out0 mix 0 codec_in0' on
amixer -c0 sset 'codec_out0 mix 0 codec_in1' on
 
3. replicate all the data on codec_out1 to make sure you have data on all 4 slots
 
amixer -c0 sset 'codec_out1 mix 0 pcm0_in' on
amixer -c0 sset 'codec_out1 Gain 0' 80%
amixer -c0 sset 'codec_out1 Gain 0 Ramp Delay' 50
amixer -c0 sset 'codec_out1 Gain 0' off
 
 
 
__________ Information from ESET Smart Security, version of virus signature database 4468 (20090929) __________
 
The message was checked by ESET Smart Security.
 
http://www.eset.com
 
 
 

  reply	other threads:[~2015-12-12  8:47 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 [this message]
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=2015121216254115203520@pcasl.com \
    --to=tuzhihe@pcasl.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=pierre-louis.bossart@linux.intel.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.