alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: John Graham <johngavingraham@googlemail.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: Access to bytes from the raw audio stream? (AC'97)
Date: Wed, 3 Feb 2010 16:27:05 +0000	[thread overview]
Message-ID: <94cf76f1002030827p6b420c17wae026b19cd077e60@mail.gmail.com> (raw)
In-Reply-To: <20100203161737.GC12034@sirena.org.uk>

> With a lot of AC97 controllers the hardware won't allow you direct
> access to the cooked wire data, you'll only be able to see decoded audio
> streams.  What is it that you're actually trying to do?

Basically, we've got a problem where we think our processor is
bit-shifting the sample for some reason, and I was going to see if I
could either (i) un-bit-shift it (it looks like we're not actually
losing any data, the sound's just being multiplied by 2^4), or (ii)
reproduce the problem we see by bit-shifting the samples on a
known-good platform.


> For embedded platforms you mostly want to look under sound/soc though
> there are a few platforms outside of there.

I know the drivers for our particular setup (UBC1400 codec/i.MX25
processor) are under sound/arm, but I'm not sure if there's anything
in there that actually sees the samples as they come through.


Would I be able to access samples quite early on in the generic AC'97
code (I don't know where that is, either, but it would be interesting
to see, at least :p)

Thanks,

John G

  reply	other threads:[~2010-02-03 16:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-03 16:08 Access to bytes from the raw audio stream? (AC'97) John Graham
2010-02-03 16:17 ` Mark Brown
2010-02-03 16:27   ` John Graham [this message]
2010-02-03 16:59     ` Mark Brown

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=94cf76f1002030827p6b420c17wae026b19cd077e60@mail.gmail.com \
    --to=johngavingraham@googlemail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.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).