From: Peter Ujfalusi <peter.ujfalusi@ti.com>
To: Enric Balletbo Serra <eballetbo@gmail.com>
Cc: alsa-devel@alsa-project.org, Lars-Peter Clausen <lars@metafoo.de>,
Takashi Iwai <tiwai@suse.de>, Liam Girdwood <lgirdwood@gmail.com>,
Jyri Sarha <jsarha@ti.com>, Mark Brown <broonie@kernel.org>
Subject: Re: Audio play problem with tlv320aic3106 in mainline.
Date: Fri, 29 May 2015 15:16:45 +0300 [thread overview]
Message-ID: <556858AD.1030609@ti.com> (raw)
In-Reply-To: <CAFqH_511rLmDPEBLmXou6_iqNTj9t2uFNVvaW=+RmpumM9GmyA@mail.gmail.com>
On 05/29/2015 12:24 PM, Enric Balletbo Serra wrote:
>> It might be really 24MHz.
>> If the MCLK in your board is wired like am335x-evmsk or how BeagleBone's audio
>> capes are wired (MCLK is coming from AM335x's EVENT_INTR0/1 pin as CLKOUT1/2)
>> then 24MHz is correct. On the am335x-evm there is a dedicated crystal
>> providing the 12MHz.
>>
> Well, in my board there is also a dedicated crystal providing the
> 12MHz, so I expect that the correct value for clock-frequency is 12MHz
> not 24MHz.
I was wrong with the BBW audio cape.. At least the RevA which I have does have
12MHz crystal connected to aic3106 MCLK, but there is a line to the SoC's
CLKOUT2. By default the codec runs using the 12MHz.
I have checked with a scope and yep, I have 12MHz for MCLK.
>
> clocks {
> compatible = "simple-bus";
> #address-cells = <1>;
> #size-cells = <0>;
>
> /* audio external oscillator */
> tlv320aic3x_mclk: oscillator@0 {
> compatible = "fixed-clock";
> #clock-cells = <0>;
> clock-frequency = <12000000>; /* 12MHz */
> };
> };
>
> sound {
> compatible = "ti,da830-evm-audio";
> ti,model = "AM335x-SL50";
> ti,audio-codec = <&audio_codec>;
> ti,mcasp-controller = <&mcasp0>;
>
> clocks = <&tlv320aic3x_mclk>;
> clock-names = "mclk";
>
> ti,audio-routing =
> "Headphone Jack", "HPLOUT",
> "Headphone Jack", "HPROUT",
> "LINE1R", "Line In",
> "LINE1L", "Line In";
> };
If I use this with my BBW+Audio cape: audio is fine.
>
> For me it's really odd have to set the clock-frequency to 24MHz to make it work
>
> clock-frequency = <24000000>;
If I change it to this, I will have slow motion playback, as expected.
> For that reason I'm wondering if there is a bug in the driver, did
> anyone test with an am335x-evm board ?
I'm using linux-next.
Not sure what could be the issue.
>
>>>
>>> [1] https://patchwork.kernel.org/patch/6480071/
>>>
>>> Thanks in advance,
>>> Enric
>>>
>>
>> --
>> Péter
>
> Thanks,
> Enric
>
--
Péter
_______________________________________________
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-05-29 12:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-28 11:36 Audio play problem with tlv320aic3106 in mainline Enric Balletbo Serra
2015-05-29 7:20 ` Peter Ujfalusi
2015-05-29 9:24 ` Enric Balletbo Serra
2015-05-29 12:16 ` Peter Ujfalusi [this message]
2015-06-01 9:16 ` Enric Balletbo Serra
2015-06-01 12:10 ` Peter Ujfalusi
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=556858AD.1030609@ti.com \
--to=peter.ujfalusi@ti.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=eballetbo@gmail.com \
--cc=jsarha@ti.com \
--cc=lars@metafoo.de \
--cc=lgirdwood@gmail.com \
--cc=tiwai@suse.de \
/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).