From: Pavel Hofman <pavel.hofman@ivitera.com>
To: Jaroslav Kysela <perex@perex.cz>
Cc: alsa-devel <alsa-devel@alsa-project.org>,
Jonas Petersen <jnsptrsn1@gmail.com>
Subject: Re: M-Audio Audiophile 192 (ice1724)'s broken spdif capture
Date: Mon, 28 Jan 2013 13:52:10 +0100 [thread overview]
Message-ID: <5106747A.5070803@ivitera.com> (raw)
In-Reply-To: <510644E5.1040505@perex.cz>
On 28.1.2013 10:29, Jaroslav Kysela wrote:
> Date 27.1.2013 16:49, Jonas Petersen wrote:
>> in ap192_ak4114_init() of revo.c I see this:
>>
>> ---- static const unsigned char ak4114_init_vals[] = { AK4114_RST |
>> AK4114_PWN | AK4114_OCKS0 | AK4114_OCKS1, AK4114_DIF_I24I2S,
>> AK4114_TX1E, AK4114_EFH_1024 | AK4114_DIT | AK4114_IPS(1), 0, 0 };
>> static const unsigned char ak4114_init_txcsb[] = { 0x41, 0x02,
>> 0x2c, 0x00, 0x00 }; ----
>>
>> Something wrong here maybe?
>>
>> I noticed that the ak4114_init_vals array has 6 values but in
>> ap192_ak4114_init() 7 values get written to ak4114.regmap.
>
> Looking to the AK4114 datasheet. I would try the clock mode 2
> (CM1=1,CM0=0) and also, check if there is a 11.2896Mhz crystal used
> for the reference clock (XTL1, XTL0). Also, the note in revo.c that
> the input rate reported by AK4114 is unstable, clearly shows that the
> clock logic is screwed (misconfigured).
The crystal is not used
http://www.nix.ru/autocatalog/m_audio_midiman_sound/34397_2245_draft.jpg
. IME ak411x cards without the auxiliary Xiling fpga do not provide the
independent clock from ak411X and thus cannot report the input rate
correctly. That is why I do not make use of the value in the driver
(ak->check_flags = AK4114_CHECK_NO_RATE)
Jonas, please could you check if ak4114 pins XTL0/1 (10, 11) are
connected to logical high? They should be :)
Regards,
Pavel.
next prev parent reply other threads:[~2013-01-28 12:52 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 [this message]
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
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=5106747A.5070803@ivitera.com \
--to=pavel.hofman@ivitera.com \
--cc=alsa-devel@alsa-project.org \
--cc=jnsptrsn1@gmail.com \
--cc=perex@perex.cz \
/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.