[alsa-devel] M-Audio Audiophile 192 (ice1724)'s broken spdif capture

Jonas Petersen jnsptrsn1 at gmail.com
Mon Jan 28 22:25:53 CET 2013


Am 28.01.2013 13:52, schrieb Pavel Hofman:
> 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 :)

Physically they're both on ground. I don't know what active state that 
chip has though.




More information about the Alsa-devel mailing list