From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Pietro <pxpert@gmail.com>, alsa-devel@alsa-project.org
Subject: Re: Applied "ASoC: Intel: add bytct-rt5651 machine driver" to the asoc tree
Date: Tue, 31 May 2016 07:29:19 -0500 [thread overview]
Message-ID: <bd2f5937-39bf-5892-959e-ec11cf2c5dba@linux.intel.com> (raw)
In-Reply-To: <1851514.XmzcdsvJt0@wks-pdc-gentoo>
On 5/31/16 3:43 AM, Pietro wrote:
> Hi,
>
> I'm an owner of a 2 in 1 Netbook with an Atom X5 Z8300 SoC with rt5651 codec (Cube iWork 11).
>
> To get audio working I Added these lines of code to the ./soc/intel/atom/sst/sst_acpi.c file:
>
> --- ./soc/intel/atom/sst/sst_acpi.c.old 2016-05-31 09:05:40.045682194 +0200
> +++ ./soc/intel/atom/sst/sst_acpi.c 2016-05-31 09:07:26.829324148 +0200
> @@ -342,9 +342,12 @@
> &chv_platform_data },
> {"193C9890", "cht-bsw-max98090", "intel/fw_sst_22a8.bin", "cht-bsw", NULL,
> &chv_platform_data },
> + {"10EC5651", "bytcr_rt5651", "intel/fw_sst_0f28.bin", "bytcr_rt5651", NULL,
> + &byt_rvp_platform_data },
> {},
> };
use the same as for rt5640 on cht:
/* some CHT-T platforms rely on RT5640, use Baytrail machine driver */
{"10EC5640", "bytcr_rt5640", "intel/fw_sst_22a8.bin", "bytcr_rt5640",
NULL, &chv_platform_data },
>
> +
> static const struct acpi_device_id sst_acpi_ids[] = {
> { "80860F28", (unsigned long)&sst_acpi_bytcr},
> { "808622A8", (unsigned long) &sst_acpi_chv},
>
>
>
>
> Then i added the UCM files linked in these archive:
> https://github.com/plbossart/UCM/tree/master/bytcr-rt5651
>
>
>
> With this configuration, audio seems to work, but is 'slow': Playback speed is at slow motion, and seconds move slowly (Tried with aplay and audacious with many sound files, using directly Alsa and Pulseaudio with no differencies).
>
> This seems to be a DSP Clock problem. Have you got any suggestions to solve this problem?
we've had this report before with rt5640 but it's unclear what might
cause this. the codec is configured as slave and uses the bit clock as
source for its PLL.
the easiest fix in this case would be to use the 19.2 MCLK which is
enabled by default on CHT, see examples in cht-bsw-rt5645 (look at
platform clock control and everything with set_sys_clk, but keep the 2
slots). We will add this on baytrail as well at some point when we have
a clock framework driver for the MCLK control.
next prev parent reply other threads:[~2016-05-31 12:29 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 [this message]
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
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=bd2f5937-39bf-5892-959e-ec11cf2c5dba@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).