From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Pietro <pxpert@gmail.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: Applied "ASoC: Intel: add bytct-rt5651 machine driver" to the asoc tree
Date: Tue, 31 May 2016 17:26:30 -0500 [thread overview]
Message-ID: <cba64f0e-9ca2-e4a6-5436-ea68cc1e9fcc@linux.intel.com> (raw)
In-Reply-To: <2387755.MGqpljUrLg@wks-pdc-gentoo>
On 5/31/16 3:56 PM, Pietro wrote:
> Hi,
> Here are the answers:
>
> - tracing to make sure you are actually on a CHT device
> The device should be CHT (The processor is an Atom X3-Z8300). Can it be that the processor is an X3 series, but the platform is BT and not a CHT? I know many manifacturers simply upgraded their notebooks series from BT to CHT by changing the CPU and mantaining all the other components the same (For example the Audio codec).
> How can I trace this?
you see a lot of references to cherrytrail-cr and 22A8, the right ID.
>
> - pastebin dmesg somewhere
> Here is it: http://pastebin.com/FnpAD1kg
You have lots of errors or warnings in there. Not sure why, i have
machines that don't behave as badly.
I am not sure why using the CHT firmware leads to an error, somehow you
probably have a combination of issues. I would really start there, if
the regular firmware doesn't work for you something is very wrong.
> - sudo cat /sys/bus/acpi/devices/10EC5651:01/status
> Here are the results:
> /sys/bus/acpi/devices/10EC5651:00/status
> Returns 15
this matches what the machine driver expects so that's good.
>
> /sys/bus/acpi/devices/10EC5651:01/status
> Returns 0
>
> - enabling DSP loopbacks to see if the DSP consumes data at the right rate. look at the UCM file and change cset "name='pcm1_out mix 0 pcm0_in Switch' off" to on if you record and loopback on USB output this should play at the right speed.
> I've changed the value in the HiFi file, but no changes.
> How can i enable DSP loopbacks? I'm not an alsa developer so I need some help here :)
you need to record to enable the loopback while you play...
>
> Please let me know if you need other informations.
can you extract the DSDT and pastebin it as well?
>
> On Tuesday 31 May 2016 15:27:45 Pierre-Louis Bossart wrote:
>> the changes look ok
>>>
>>> But I still have the same problem: Audio plays slowly.
>>>
>>>
>>>
>>> It seems the DSP is clocked at 19.2, but the system is still clocked for
>>> 25, and these changes doesn't seem to have effects...
>>
>> no, CHT doesn't have a 25 MHz clock at all so that's just not physically
>> possible.
>>
>> Can you try:
>> - tracing to make sure you are actually on a CHT device
>> - pastebin dmesg somewhere
>> - sudo cat /sys/bus/acpi/devices/10EC5651:01/status
>> - enabling DSP loopbacks to see if the DSP consumes data at the right
>> rate. look at the UCM file and change
>> cset "name='pcm1_out mix 0 pcm0_in Switch' off" to on
>> if you record and loopback on USB output this should play at the right
>> speed.
>>
>>
>>
>
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@alsa-project.org
> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
>
next prev parent reply other threads:[~2016-05-31 22:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-31 8:43 Applied "ASoC: Intel: add bytct-rt5651 machine driver" to the asoc tree Pietro
2016-05-31 12:29 ` Pierre-Louis Bossart
2016-05-31 20:11 ` Pietro
2016-05-31 20:27 ` Pierre-Louis Bossart
2016-05-31 20:56 ` Pietro
2016-05-31 22:26 ` Pierre-Louis Bossart [this message]
2016-06-01 8:38 ` Pietro
2016-06-01 15:13 ` Pierre-Louis Bossart
2016-06-01 21:43 ` Pietro
2016-06-01 21:58 ` Pierre-Louis Bossart
2016-06-02 8:58 ` Pietro
-- strict thread matches above, loose matches on Subject: below --
2016-01-04 23:20 [PATCH v2 2/8] ASoC: Intel: add bytct-rt5651 machine driver Pierre-Louis Bossart
2016-01-05 17:49 ` Applied "ASoC: Intel: add bytct-rt5651 machine driver" to the asoc tree Mark Brown
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=cba64f0e-9ca2-e4a6-5436-ea68cc1e9fcc@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=pxpert@gmail.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).