All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benny Sjostrand <gorm@cucumelo.org>
To: Peter Heatwole <peter599@gotnet.net>, alsa-devel@lists.sourceforge.net
Subject: Re: SPDIF output finally working properly with CS4630
Date: Fri, 26 Jul 2002 08:40:51 +0200	[thread overview]
Message-ID: <3D40EEF3.3050502@cucumelo.org> (raw)
In-Reply-To: 20020725222328.GA2919@porky

>    I can watch what you're saying as I mute and unmute "IEC 958" in
> alsamixer. Muted, the 9th dword is 00a0, unmuted it's 00e0. Side 
> question:
> you referenced AsynchFGTxSCB. What's the FGT acronym stand for?) 


I believe it stands for "Asynchronous Foreground transfer", it's the task
in DSP that's responsible to tranfer samples from Foreground to
Hyperforeground.

>
>    Here's a strange one. With "IEC 958" muted, I view dsp_scb, and the
> first dword of SPDIFOSCB is 00000000. I unmute "IEC 958", and I can watch
> the first dword of SPDIFOSCB change each time I view dsp_scb. Here's a 
> list
> of each individual number I get (duplicates have been removed):

The SPDIFOSCB task runs in Hyperforeground on DSP, it's responsible
to transfer samples to the HW FIFO.

>
> 80005001
> 80001001
> 80000001
> 80002001
> 00001001
> 80003001
> 80006001
> 00006001
> 00003001
> 00004001
> 80003001
> 80004001
> 00000001
> 00007001
> 80005001
> 00005001
> 80007001
> 00002001
> 00005001

If you want to find out more details about this, the CS4630 design spec.
Page 228. the SPDOUT_STATUS register.

>
>    I tried this with and without sounds playing (though I still can't 
> hear
> them). Do you have any information regarding what each bit stands for in
> the first dword of SPDIFOSCB? (if you do, could you point me to where you
> obtained this information so I can try to educate myself?)  I'm writing
> this because it seems strange; I don't understand why the status bits 
> would
> keep changing for no (apparent) reason.

We dont have any documentaion about the SCB's. The references I got are 
DSP assembler
sources of some tasks some examples about how to setup the SCB's.
Some hints from Cirrus, and analyzing the assembler sources (and 
binaries) is where i've been
token this conlusions, what probes that i'm right is that it seems to 
work, but I can be wrong in
some points.

Hopefully the code I wrote helps uncovers some internals of the DSP, 
before you
start reading the assembler sources by "the hard way" take a look at 
alsa-kernel/include/cs46xx_dsp_scb_types.h
and alsa-kernel/include/cs46xx_dsp_task_types.h first.

/Benny




-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

  reply	other threads:[~2002-07-26  6:40 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-23 20:33 SPDIF output finally working properly with CS4630 Benny Sjostrand
2002-07-24  1:34 ` Peter Heatwole
2002-07-24  4:28   ` Benny Sjostrand
2002-07-24  6:29     ` Peter Heatwole
2002-07-24 18:19     ` Peter Heatwole
2002-07-24 18:41       ` Benny Sjostrand
2002-07-24 20:12         ` Peter Heatwole
2002-07-24 19:59           ` Benny Sjostrand
2002-07-24 21:23             ` Peter Heatwole
2002-07-24 21:53               ` Benny Sjostrand
2002-07-24 23:37                 ` Peter Heatwole
2002-07-24 23:53                   ` Peter Heatwole
2002-07-25 22:23                 ` Peter Heatwole
2002-07-26  6:40                   ` Benny Sjostrand [this message]
2002-07-24  9:52 ` Takashi Iwai

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=3D40EEF3.3050502@cucumelo.org \
    --to=gorm@cucumelo.org \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=peter599@gotnet.net \
    /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.