From: Liam Girdwood <lrg@ti.com>
To: "Shilimkar, Santosh" <santosh.shilimkar@ti.com>
Cc: Russell King - ARM Linux <linux@arm.linux.org.uk>,
linux-omap@vger.kernel.org,
Peter Ujfalusi <peter.ujfalusi@ti.com>
Subject: Re: Audio support on OMAP 3430LDP or 4430SDP boards
Date: Fri, 27 Apr 2012 15:56:42 +0100 [thread overview]
Message-ID: <1335538602.4150.12.camel@odin> (raw)
In-Reply-To: <CAMQu2gw0pYcb5SoVLbWPL4rfda24EZVPPUUziU8gxZxviDBLZg@mail.gmail.com>
On Fri, 2012-04-27 at 19:45 +0530, Shilimkar, Santosh wrote:
> + Peter and Liam to comment
>
> On Fri, Apr 27, 2012 at 7:28 PM, Russell King - ARM Linux
> <linux@arm.linux.org.uk> wrote:
> > Can someone please hint on what audio is supported on these two OMAP
> > boards? From what I can tell, the answer is either "nothing" or "hdmi",
> > both of which are useless to me if someone wants me to convert the OMAP
> > ASoC driver to DMA engine.
> >
> > From what I can see on the 4430SDP, there's a 3.5mm headset jack,
> > microphones and speakers on the board, so the board does have audio
> > hardware. However, it seems (as, I'm afraid to say, seems to be pretty
> > much standard practice with OMAP) there's a total lack of software
> > support in mainline.
> >
> > This kind'a prevents me testing changes to the DMA support for OMAP
> > ASoC...
> >
> > What can be done to remedy this situation?
> >
Peter now has has the final patches for Legacy mode (i.e. without ABE)
now upstream in 3.4-rc. Legacy mode gives a direct SDMA -> McPDM ->
twl6040 audio path so would be a good starting point for DMA testing.
Regards
Liam
next prev parent reply other threads:[~2012-04-27 14:56 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-27 13:58 Audio support on OMAP 3430LDP or 4430SDP boards Russell King - ARM Linux
2012-04-27 14:15 ` Shilimkar, Santosh
2012-04-27 14:56 ` Liam Girdwood [this message]
2012-04-27 15:09 ` Russell King - ARM Linux
2012-04-27 15:53 ` Ujfalusi, Peter
2012-04-27 16:04 ` Russell King - ARM Linux
2012-04-27 16:32 ` Ujfalusi, Peter
2012-04-27 16:50 ` Russell King - ARM Linux
2012-04-27 17:04 ` Ujfalusi, Peter
2012-04-27 17:19 ` Russell King - ARM Linux
2012-04-27 18:14 ` Ujfalusi, Peter
2012-04-27 18:31 ` Russell King - ARM Linux
2012-04-27 19:17 ` Ujfalusi, Peter
2012-04-27 19:31 ` Russell King - ARM Linux
2012-04-29 20:35 ` Russell King - ARM Linux
2012-04-30 7:26 ` Peter Ujfalusi
2012-05-01 11:14 ` Russell King - ARM Linux
2012-06-21 12:59 ` Russell King - ARM Linux
2012-06-21 13:16 ` Russell King - ARM Linux
2012-06-21 13:22 ` Russell King - ARM Linux
2012-06-21 18:36 ` Ujfalusi, Peter
2012-06-21 18:58 ` Russell King - ARM Linux
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=1335538602.4150.12.camel@odin \
--to=lrg@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=peter.ujfalusi@ti.com \
--cc=santosh.shilimkar@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox