Hi Joseph,
The initiation is different from windows. It is fine as I think because the codec driver is different between two systems. The machine driver is only to bring up the sound device. If you can see the sound card in your platform, the machine driver has worked as well. Could you check the following information in your platform now?
1. Can register dump work? Try the command. Ex.
# cat /sys/kernel/debug/regmap/i2c-10508824:00/registers
2. Can you see sound card info.? There are some virtual files in the folder and you can cat the info..
/sys/devices/platform/cht-bsw-nau8824/SSP2-Codec
/proc/asound/
Besides, I think the timeout is nothing with the machine and codec. Maybe you can consult with Intel about the issue.
BR. John Hsu AC30, Nuvoton Technology Corp. +886 3 5770066 Ext. 37111 KCHSU0@nuvoton.commailto:KCHSU0@nuvoton.com
From: Joseph Wang [mailto:joequant@gmail.com] Sent: Monday, December 05, 2016 2:46 PM To: AC30 KCHsu0 Cc: AP MS30 Linux ALSA; Pierre-Louis Bossart; AC30 CTLin0 Subject: Re: Cherry trail and Nau 88l24 codec
[ 2.681633] snd_intel_sst: Requesting FW fw_sst_22a8.bin now...
Hi, This is the firmware that I am using. Right now the problem is that I'm getting timeouts. I've confirmed that the device runs fine under the Windows WDM Audio drivers and the Windows NAUL88 codec. So what appears to be happening is that machine driver is doing something incorrectly. If you can look at
https://github.com/joequant/nau8824/blob/master/linux-4.8/cht_bsw_nau8824.c And check to see how the initialization is different than the Windows driver, this would be very useful. I don't know how the device is wired, but I do know that it appears to work with the Cherry Trail windows drivers. That being the case, I think the issue is my misinitialization rather than device quirk. Also to answer your other question. I am no longer getting kernel errors in the codec. I believe that at one point I was loading old versions of the codec, but once I did a clean build with the sources that you've provided me, I get no issues with the codec, and I've removed the workaround code. The problems that I'm having with the firmware appear to arise from the machine drivers. One other thing, I was wondering if you have a Cherry Trail dev environment that you can test to see if you can load in my machine driver and replicate the firmware time outs.
=========================================================================================== The privileged confidential information contained in this email is intended for use only by the addressees as indicated by the original sender of this email. If you are not the addressee indicated in this email or are not responsible for delivery of the email to such a person, please kindly reply to the sender indicating this fact and delete all copies of it from your computer and network server immediately. Your cooperation is highly appreciated. It is advised that any unauthorized use of confidential information of Nuvoton is strictly prohibited; and any information in this email irrelevant to the official business of Nuvoton shall be deemed as neither given nor endorsed by Nuvoton.