public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Ujfalusi <peter.ujfalusi@ti.com>
To: abhijit naik <abhijitnaik27@gmail.com>,
	<alsa-devel@alsa-project.org>, <linux-kernel@vger.kernel.org>
Subject: Re: Support for ASP DM6446 in main-line Linux Kernel
Date: Tue, 15 Jul 2014 08:49:30 +0300	[thread overview]
Message-ID: <53C4C0EA.4070401@ti.com> (raw)
In-Reply-To: <CANaY3hMvw6W0+KsdCKLbXELxjv8Dka1Drvoe3AMHmD0v1oF-cw@mail.gmail.com>

On 07/14/2014 06:58 PM, abhijit naik wrote:
> Hi,
> 
> I am studying ASP driver of DM6446 EVM in main line kernel 3.14. 
> I referred to both sound/soc/davinci/davinci-mcasp.c
> and sound/soc/davinci/davinci-i2s.c

For DM6446 the correct driver would be the davinci-i2s. The audio interface is
named as ASP in DM6446 which is an early version of McBSP - really basic IP
(according to the TRMs).
AFAIK there is no users of davinci-i2s in mainline and I do not have and I do
not have HW where I can test it.
Because of this lack of users there is no DT bindings for davinci-i2s - which
should be renamed as davinci-asp IMHO.
But the code looks like something which might work so at least w/o DT boot
should be trivial to enable.

If you look at arch/arm/mach-davinci/dm644x.c and board-dm644x-evm.c it is
setting up davinci-mcbsp (which is implemented within davinci-i2s driver).

So at least non DT boot should work with audio.

> Which one among the two is correct for DM6446 ASP and I am seeing that there
> is a device tree code in sound/soc/davinci/davinci-evm.c but corresponding
> support code is not present in sound/soc/davinci/davinci-mcasp.c
> 
> Please let me know whether this support is complete or can some one guide me
> to working code for DM6446 ASP

For what I see is that mainline should work with audio on dm644x-evm.

-- 
Péter

           reply	other threads:[~2014-07-15  5:49 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <CANaY3hMvw6W0+KsdCKLbXELxjv8Dka1Drvoe3AMHmD0v1oF-cw@mail.gmail.com>]

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=53C4C0EA.4070401@ti.com \
    --to=peter.ujfalusi@ti.com \
    --cc=abhijitnaik27@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=linux-kernel@vger.kernel.org \
    /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