public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Steve Poulsen <spoulsen@css-design.us>
To: Yuri Jaeger Monti <yurijm@gmail.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: OMAP5912 AIC23
Date: Mon, 25 Aug 2008 20:56:13 -0500	[thread overview]
Message-ID: <48B362BD.10009@css-design.us> (raw)
In-Reply-To: <65e025470808251011j42564e2g7a445558f9e82559@mail.gmail.com>

Yuri,

We have had good luck with ARM audio under this setup.  We did write our 
own AIC23 drivers which we used directly from our application.  We used 
a device entry (/dev/aic23) that hooked in our driver.  We were able to 
open those in any application and play/record or both.  The only 
possible problem was if we tried to do things like "cat file.pcm > 
/dev/aic23".  Although this would work, some cases would not work due to 
those applications buffering schemes.  For example, this was bad:  "cat 
/dev/aic23 > /dev/aic23".   It would work, but would be choppy. 

How are you playing audio?

Steve

Yuri Jaeger Monti wrote:
> Hi fellows,
>
> I tried everything I could to solve the buffer underrun error's while
> playing some audio in the OSK5912 with the AIC23, and I don't know
> what should I do anymore.
> I'm trying to simply output and audio file via the ARM, I think this
> should be ok but the audio is always choppy.
> Am I doing something wrong? Or perhaps should I use only the DSP
> processor to play the audio? (didn't tried this yet because I need the
> DSP to do other tasks).
>
> Cheers
>
> ---
> Yuri Jaeger Monti
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>
>   


  reply	other threads:[~2008-08-26  1:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <65e025470808251004w109cece7t9caeaa81b422554b@mail.gmail.com>
2008-08-25 17:11 ` OMAP5912 AIC23 Yuri Jaeger Monti
2008-08-26  1:56   ` Steve Poulsen [this message]
2008-08-26 14:22     ` Yuri Jaeger Monti
2008-08-28 17:02       ` Yuri Jaeger Monti

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=48B362BD.10009@css-design.us \
    --to=spoulsen@css-design.us \
    --cc=linux-omap@vger.kernel.org \
    --cc=yurijm@gmail.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