From: Pascal Huerst <pascal.huerst@gmail.com>
To: Peter Ujfalusi <peter.ujfalusi@ti.com>, alsa-devel@alsa-project.org
Subject: Re: [PATCH] ASoC: davinci-mcasp: Correct rx format unit configuration
Date: Wed, 14 Jan 2015 16:05:45 +0100 [thread overview]
Message-ID: <54B685C9.70000@gmail.com> (raw)
In-Reply-To: <54B67A86.6080202@ti.com>
On 14.01.2015 15:17, Peter Ujfalusi wrote:
> On 01/14/2015 03:24 PM, Pascal Huerst wrote:
>> Yes, even this single line.
>>
>> - u32 rx_rotate = 0;
>> + u32 rx_rotate = (32 - word_length) / 4;
>>
>>>> Do you have any Idea, what might cause that behavior?
>>>
>>> No, I don't. I quickly checked on am335x, am437x and on J6 boards and the
>>> command you are using works w/o any issue or distortion in recorded audio.
>>
>>> what codec or codecs are you using? I see that you record from hw:0,1 and play
>>> it back to hw:0,0
>>> Can you check if the recorded sample alone is correct? Just record it to a
>>> file and look at it on the PC. I did the same and the recorded sample looks
>>> fine on my PC as well.
>>
>> if I record into a file, it behaves just the same. Noise if
>> rx_rotate == 0, correct otherwise. I guess it is a problem in the input
>> codec, then.
>>
>> input codec: AK5386
>> output codec: TAS5086
>>
>>> Looking at the patch again, I still think it is a valid fix.
>>
>> Yes, I agree, the patch looks right.
>>
>> I'll have a look into the ak5386 and see, what impact your change could
>> have there.
>
> Can you try S24_LE format as well? I think it should work.
If I record to a file everything works fine, no noise. But I can not map
to the output, since the output codec does not support S24_LE
> I assume you are running the AK5386 as master which would explain the
> symptoms. In this mode you have 64bclk per sample (32 per channel).
no I'm not. it's running in slave mode. CKS[0-2] = 0 (GND).
> I believe this should fix your capture in case of S16_LE:
> keep the (in linux-next):
> fe0a29e163a5d045c73faab682a8dac71c2f8012 : ASoC: davinci-mcasp: Correct rx
> format unit configuration
>
> make sure you have (as in linux-next):
> d742b925244ce91f16d380befdca473e4536359b : ASoC: davinci-mcasp: Fix rx format
> when more bclk is used on the bus
Yes. Although AK5386 is in slave mode, this fixed the issue!
> add the following to your machine driver's hw_params callback:
>
> ...
> snd_soc_dai_set_clkdiv(cpu_dai, 2, 64);
> ...
That line was there already.
> I think the issue with your setup is that McASP expects the you have 32bclk
> per sample, but AK5386 generates 64 for you, this will mess up the data you
> are receiving since in this case we need to shift the data with 16bits before
> we invert it.
Ok. I think I will have to look deeper into that, to really understand,
where these 64bclk came from in my case (assuming its set in the machine
driver).
But anyways, thanks a lot for your help!
pascal
prev parent reply other threads:[~2015-01-14 15:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-04 7:52 [alsa-devel] [PATCH] ASoC: davinci-mcasp: Correct rx format unit configuration Peter Ujfalusi
2014-09-04 11:45 ` Mark Brown
2015-01-14 11:11 ` Pascal Huerst
2015-01-14 12:33 ` Peter Ujfalusi
2015-01-14 13:24 ` Pascal Huerst
2015-01-14 14:17 ` Peter Ujfalusi
2015-01-14 15:05 ` Pascal Huerst [this message]
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=54B685C9.70000@gmail.com \
--to=pascal.huerst@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=peter.ujfalusi@ti.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.