From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Joseph Wang <joequant@gmail.com>,
alsa-devel@alsa-project.org, KCHSU0@nuvoton.com
Subject: Re: Cherry trail and Nau 88l24 codec
Date: Sat, 3 Dec 2016 21:13:19 -0600 [thread overview]
Message-ID: <b9189409-fc01-ae32-538f-a7a03610263c@linux.intel.com> (raw)
In-Reply-To: <CAPoeEY_Tve2TAgBqY+MqPEUGnbadYHg9Z90DQ=YQumWebfW++A@mail.gmail.com>
On 12/2/16 7:16 PM, Joseph Wang wrote:
> Hi all,
>
> I've been trying to get sound working on my W9S pipo device. The people
> at Nuvoton have been extraordinarily helpful, but now the issue is
> writing the machine driver.
>
> My work is at
>
> https://github.com/joequant/nau8824
>
> I've gotten the drivers to load, but getting timeouts with the firmware....
>
> [ 102.447840] intel_sst_acpi 808622A8:00: Wait timed-out condition:0x0,
> msg_id:0x2 fw_state 0x3
> [ 102.447872] intel_sst_acpi 808622A8:00: fw returned err -16
> [ 103.471448] intel_sst_acpi 808622A8:00: Wait timed-out condition:0x0,
> msg_id:0x2 fw_state 0x3
>
> and then
>
> [ 116.820782] intel_sst_acpi 808622A8:00: fw returned err -16
> [ 116.938921] intel_sst_acpi 808622A8:00: FW sent error response 0x5000e
> [ 116.939065] intel_sst_acpi 808622A8:00: FW sent error response 0x5000e
> [ 116.939579] intel_sst_acpi 808622A8:00: FW sent async error msg:
> [ 116.939614] (null)00040021 00000000
> [ 116.939685] (null)00040021 00000000
> [ 116.953260] sst-mfld-platform sst-mfld-platform: Enter: enable=1
> port_name=ssp2-port
> [ 116.953704] intel_sst_acpi 808622A8:00: Alloc for str 3 pipe 0xe
> [ 116.954062] sst-mfld-sst-mfld-platform: SET_SWM cmd max inputs reached
Just a wild guess: this looks the communication with the DSP isn't
working and the messages look similar to what we saw with Baytrail-CR
where a BIOS genius decided to swap the order of interrupt resources.
Can you share the DSDT (on a pastebin, not as attachment) so that we can
compare the BIOS information for the DSP with known and working
configurations.
>
> One other path is that ICube has gotten this codec to work on their
> iwork8 Ultimate android device. They are required to release the source
> under GPL2, but haven't done so, so if all else fails, it will be a
> matter of tracking down someone in that company and explaining the
> issues to them. Since I'm in Hong Kong, I might just find where the
> things are manufactured, and just show up at their office.
>
> But it appears that there are some "magic bits" that are missing. One
> question that I have is what is the proper DAI to use (i.e. PCM or I2S)
> for cherry trail. The second question is that looking at the windows
> driver for nau88l24, there appears to be a test mode that runs the
> driver against a Realtek rt5645. Should I assume that this means that
> the initialization is similar?
>
> Also I'm quite interested in getting this to work. The W9S Pipo is a
> perfect netbook that has a big screen that is half the weight of my old
> laptop. The big thing is that someone realized that instead of putting
> in a SATA hard disk, that they can use an SD card as main storage, and
> that cuts down on the weight.
>
next prev parent reply other threads:[~2016-12-04 3:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-03 1:16 Cherry trail and Nau 88l24 codec Joseph Wang
2016-12-04 3:13 ` Pierre-Louis Bossart [this message]
2016-12-04 14:19 ` Joseph Wang
2016-12-05 7:29 ` KCHSU0
2016-12-05 3:43 ` KCHSU0
2016-12-05 6:45 ` Joseph Wang
2016-12-05 8:58 ` KCHSU0
2016-12-05 18:10 ` Pierre-Louis Bossart
2016-12-07 8:01 ` Joseph Wang
2016-12-07 9:21 ` Joseph Wang
2016-12-07 14:19 ` Pierre-Louis Bossart
-- strict thread matches above, loose matches on Subject: below --
2016-12-09 14:14 Joseph Wang
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=b9189409-fc01-ae32-538f-a7a03610263c@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=KCHSU0@nuvoton.com \
--cc=alsa-devel@alsa-project.org \
--cc=joequant@gmail.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).