From: Wolfram Sang <w.sang@pengutronix.de>
To: David Jander <david.jander@protonic.nl>
Cc: alsa-devel@alsa-project.org,
Mark Brown <broonie@opensource.wolfsonmicro.com>,
Liam Girdwood <lrg@ti.com>
Subject: Re: ASoC driver parts probing order (MPC5200/MPC5121)
Date: Thu, 20 Oct 2011 14:13:03 +0200 [thread overview]
Message-ID: <20111020121303.GE2379@pengutronix.de> (raw)
In-Reply-To: <20111020133758.27011ac7@archvile>
[-- Attachment #1.1: Type: text/plain, Size: 1162 bytes --]
> I think I was not clear enough. I meant sound/soc/fsl/mpc5200_dma.c, not the
> actual Bestcom DMA driver.
Ah, okay, sorry misunderstood that.
> Btw, I am writing a DMA-less driver for the MPC5121e for now. It uses the PSC
> FIFO and FIFO alarm interrupts. DMA support could be added later, when de
> MPC5121 DMA driver becomes capable of doing device IO.
OK, seems sensible for a start. MPC5121 does not get much love, so small
steps are definately a good idea.
> > > 1.- I can't test it on a MPC5200B, so therefor I need help.
> >
> > I can do tests.
>
> If you could try out latest mainline, to see if the driver still works,
> that would be great for a start. I am almost certain it either doesn't work
> anymore, or you have a 50% chance it crashes while booting.
OK, I will leave for Prague in the next hours, so until I return, I can
do only remote testing. But I should see OOPSes this way nonetheless.
Might take a few days, though...
Regards,
Wolfram
--
Pengutronix e.K. | Wolfram Sang |
Industrial Linux Solutions | http://www.pengutronix.de/ |
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2011-10-20 12:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-20 10:23 ASoC driver parts probing order (MPC5200/MPC5121) David Jander
2011-10-20 10:59 ` Wolfram Sang
2011-10-20 11:37 ` David Jander
2011-10-20 12:13 ` Wolfram Sang [this message]
2011-10-20 12:27 ` David Jander
2011-10-20 12:35 ` Mark Brown
2011-10-20 13:26 ` David Jander
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=20111020121303.GE2379@pengutronix.de \
--to=w.sang@pengutronix.de \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=david.jander@protonic.nl \
--cc=lrg@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;
as well as URLs for NNTP newsgroup(s).