All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Courtier-Dutton <James@superbug.co.uk>
To: ALSA development <alsa-devel@alsa-project.org>
Subject: Audigy 2 SPDIF rates.
Date: Sat, 12 Mar 2005 22:24:00 +0000	[thread overview]
Message-ID: <42336C00.5080105@superbug.co.uk> (raw)

I have found some more rates that the Audigy 2 SPDIF can run at:

Using the register 0x76 A_SPDIF_RATE.
00 => 48000
20 => 192000
40 => 96000
80 => 44100
No other rates are possible.

To detect the rate, loop the SPDIF output into an input and look at 
register 0x61 GPSRCS

Detected rate = ( ( GPSRCS & 0xFFFFF ) * 48000 ) / 0x40000
or
Detected rate = ( ( GPSRCS & 0xFFFFF ) * 48000 ) / 262144

The GPSRCS register is only valid if 0x51 != 0xffffffff
0x51 is GPSCS which is the SPDIF status register. containing details 
about non-audio bits etc.

Likewise, 0x50 and 0x60 for the CD SPDIF input.

So, the header file should be changed from:
#define A_SPDIF_SAMPLERATE      0x76            /* Set the sample rate 
of SPDIF output          */
#define A_SPDIF_RATE_MASK       0x000000c0
#define A_SPDIF_48000           0x00000000
#define A_SPDIF_44100           0x00000080
#define A_SPDIF_96000           0x00000040

To:
#define A_SPDIF_SAMPLERATE      0x76            /* Set the sample rate 
of SPDIF output          */
#define A_SPDIF_RATE_MASK       0x000000e0
#define A_SPDIF_48000           0x00000000
#define A_SPDIF_44100           0x00000080
#define A_SPDIF_96000           0x00000040
#define A_SPDIF_192000          0x00000020


James


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

                 reply	other threads:[~2005-03-12 22:24 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=42336C00.5080105@superbug.co.uk \
    --to=james@superbug.co.uk \
    --cc=alsa-devel@alsa-project.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.