[alsa-devel] Please help in adding ams-delta support to ASoC

[Arun K S]

On Fri, Jun 19, 2009 at 4:20 AM, Janusz
Krzysztofik<jkrzyszt at tis.icnet.pl> wrote:
> Tony Lindgren wrote:
>>
>> * Janusz Krzysztofik <jkrzyszt at tis.icnet.pl> [090618 14:52]:
>>>
>>> Tony Lindgren wrote:
>>>>
>>>> On omap1, DSP needs to be powered and idled before some mcbsp clocks can
>>>> be used. Or at least needs to be powered up.
>>>
>>> AFAICS there is no DSP code in mainline at all, so the answer is no, DSP
>>>  was likely not powered up at all. For several weeks I was trying to do
>>>  what was impossible :/. But fortunatelly, I have learned a lot ;).
>>
>> We at least used to have code to power and idle the DSP even without the
>> dspgateway compiled in.. Sorry I don't remember the details. But most
>> likely you need to have the dspgateway patch enabled.
>
> Tony,
> Thanks for clarifying things.
>
> Arun K S wrote:
>>
>> On Thu, Jun 18, 2009 at 4:40 AM, Janusz
>> Krzysztofik<jkrzyszt at tis.icnet.pl> wrote:
>>>
>>> ... I retried the new driver on commit
>>> 90e758af52ba803cba233fabee81176d99589f09 and confirmed the prevoiusly
>>> seen
>>> hangup. I found that it was omap_mcbsp_request() never returning back
>>> from.
>>
>> I faced the same issue while writing ASoC driver for tlv320aic23b codec.
>>
>> You can have a look at this thread:
>> http://www.mail-archive.com/linux-omap@vger.kernel.org/msg03852.html
>>
>> It may help.
>
> Arun,
> Thanks, it's good to hear not only me having this problem ;). So what is the
> current status of your osk driver? What tree do you use, what extra patches
> do you apply to make it actually working?

Currently osk driver works fine on 2.6.31. Initially i used to add the
omap_mcbsp_request()
at the boot time, other wise it hangs up. Audio in current mainline
tree works fine for osk5912
with out any such hacks. I believe there are some patches from Russel
for the DSP memory mapping during
2.6.29 kernel.

>
> ---------------------------
>
> After all, could someone please give me an advise, what tree, even with
> buggy omap1510 mcbsp/dsp support, should I base my work on for best results?
> Omap? Sound? Mainline? I mean not only easy getting the driver working, but
> also giving it the best possible path into the mainline.

You have to use current omap tree with the patches from current sound
tree(ASoC omap platform drivers changes) for
testing the driver.
Somebody correct me if i am wrong.

>
> Thanks,
> Janusz
>
--
To unsubscribe from this list: send the line "unsubscribe alsa-devel" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html