From: Jonas Petersen <jnsptrsn1@gmail.com>
To: Pavel Hofman <pavel.hofman@ivitera.com>
Cc: alsa-devel <alsa-devel@alsa-project.org>
Subject: Re: M-Audio Audiophile 192 (ice1724)'s broken spdif capture
Date: Sat, 02 Feb 2013 02:22:04 +0100 [thread overview]
Message-ID: <510C6A3C.1000501@gmail.com> (raw)
In-Reply-To: <510AEF46.1080608@gmail.com>
:-)
I've got some progress here. The AK4114_ADDR was wrong. I changed it
from 0x02 to 0x00 (according to datasheet).
Now I had some meat in the ak4114 file, but no signal was coming in.
Then I found that the wrong spdif receiver channel was selected (the
AK4114 has 4). After selecting the right one (0 instead of 1) I got the
signal!
Its at the right level (-12dB) and the L/R channels match. But it's
somehow capturing twice the rate. The 1 kHz come in as 2 kHz. There must
still be something wrong.
Here is some content of the ak4114:
/proc/asound/Audiophile192/ak4114
0x00 = 0x0f
0x01 = 0x70
0x02 = 0x80
0x03 = 0x49
0x04 = 0x00
0x05 = 0x00
0x06 = 0x10
0x07 = 0x10
0x08 = 0x45
0x09 = 0x02
0x0a = 0x2c
0x0b = 0x00
0x0c = 0x00
0x0d = 0x41
0x0e = 0x02
0x0f = 0x2c
0x10 = 0x00
0x11 = 0x00
0x12 = 0x00
0x13 = 0x00
0x14 = 0x00
0x15 = 0x00
0x16 = 0x00
0x17 = 0x00
0x18 = 0x00
0x19 = 0x00
0x1a = 0x00
0x1b = 0x00
0x1c = 0x00
0x1d = 0x00
0x1e = 0x00
0x1f = 0x00
Regarding the sample rate detection. It seems it's the channel status
bits that get interpreted by the windows driver. The fs bits from the
AK4114 seem to be unused. But the channel status definitely changes some
bits on sample rate changes.
The Clock Source seems to be PLL (CM1-0 = 0,0).
I'll keep on debugging.
- Jonas
next prev parent reply other threads:[~2013-02-02 1:22 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-26 16:35 M-Audio Audiophile 192 (ice1724)'s broken spdif capture Jonas Petersen
2013-01-26 19:30 ` Jaroslav Kysela
2013-01-26 21:20 ` Pavel Hofman
2013-01-26 22:37 ` Jonas Petersen
2013-01-27 15:49 ` Jonas Petersen
2013-01-28 9:29 ` Jaroslav Kysela
2013-01-28 12:52 ` Pavel Hofman
2013-01-28 21:25 ` Jonas Petersen
2013-01-29 9:44 ` Pavel Hofman
2013-01-31 1:19 ` Jonas Petersen
2013-01-31 9:04 ` Pavel Hofman
2013-01-31 20:56 ` Jonas Petersen
2013-01-28 12:36 ` Pavel Hofman
2013-01-29 0:32 ` Jonas Petersen
2013-01-29 9:39 ` Pavel Hofman
2013-01-29 13:10 ` Jonas Petersen
2013-01-30 10:30 ` Pavel Hofman
2013-01-29 19:14 ` Jonas Petersen
2013-01-30 10:26 ` Pavel Hofman
2013-01-30 15:34 ` Pavel Hofman
2013-01-31 0:29 ` Jonas Petersen
2013-01-31 10:33 ` Pavel Hofman
2013-01-31 22:25 ` Jonas Petersen
2013-02-02 1:22 ` Jonas Petersen [this message]
2013-02-02 10:44 ` Pavel Hofman
2013-02-02 22:47 ` Jonas Petersen
2013-02-04 16:56 ` Pavel Hofman
2013-02-23 22:13 ` Jonas Petersen
2013-02-25 11:47 ` Pavel Hofman
2013-01-26 21:29 ` Jonas Petersen
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=510C6A3C.1000501@gmail.com \
--to=jnsptrsn1@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=pavel.hofman@ivitera.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).