From: nsekhar@ti•com (Sekhar Nori)
To: linux-arm-kernel@lists•infradead.org
Subject: [alsa-devel] DT support for Davinci ASoC platform
Date: Fri, 6 Jul 2012 18:42:36 +0530 [thread overview]
Message-ID: <4FF6E444.1050901@ti.com> (raw)
In-Reply-To: <4FF5BB34.9070002@gmail.com>
Hi Daniel,
On 7/5/2012 9:35 PM, Daniel Mack wrote:
> On 05.07.2012 17:36, Arnd Bergmann wrote:
>> On Thursday 05 July 2012, Daniel Mack wrote:
>>> On 04.07.2012 14:48, Hebbar, Gururaja wrote:
>>>> All,
>>>>
>>>> Are there any plans or work going on for providing Device Tree Support for Davinci
>>>> ASoC?
>>>>
>>>> I am planning to add DT support for TI AM335x (McASP) and I don't want to do duplicate
>>>> task.
>>>
>>> That's good to know. But isn't there a dependency on the EDMA engine? Is
>>> that part ported yet?
>>
>> None of the dma engines are ported yet, because the generic binding for dma
>> engines is still under debate. So far, all DMA channels are described using
>> auxdata on platforms that use DT, with the exception of exynos, but that one
>> will have to change once we have the common code.
>
> You're talking about the DT bindings here, right? But the code itself is
> also only present in TI's BSP kernel sources, and not in mainline.
AM335x uses TI EDMA which is present in mainline under mach-davinci.
Matt Porter from TI is working on moving this to DMA engine. Once that's
done the driver should be usable on AM335x too. Have a look at the wiki
page Vaibhav posted under the thread "Current state of AM33xx patches"
Thanks,
Sekhar
next prev parent reply other threads:[~2012-07-06 13:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-04 12:48 DT support for Davinci ASoC platform Hebbar, Gururaja
2012-07-05 10:58 ` [alsa-devel] " Daniel Mack
2012-07-05 15:36 ` Arnd Bergmann
2012-07-05 16:05 ` Daniel Mack
2012-07-06 13:12 ` Sekhar Nori [this message]
2012-07-06 15:01 ` Arnd Bergmann
2012-08-02 20:32 ` Daniel Mack
2012-08-03 9:09 ` Sekhar Nori
2012-08-08 13:36 ` Daniel Mack
2012-08-08 14:48 ` Porter, Matt
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=4FF6E444.1050901@ti.com \
--to=nsekhar@ti$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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