alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Joseph Wang <joequant@gmail.com>, KCHSU0@nuvoton.com
Cc: alsa-devel@alsa-project.org, CTLIN0@nuvoton.com
Subject: Re: Cherry trail and Nau 88l24 codec
Date: Mon, 5 Dec 2016 12:10:09 -0600	[thread overview]
Message-ID: <30f62f0d-1e3e-0839-8d85-df9e209b5cf9@linux.intel.com> (raw)
In-Reply-To: <CAPoeEY8=A949-cuVwfyov2GfpQc=hAjPsDG-suXmT_TDytOKBQ@mail.gmail.com>

On 12/5/16 12:45 AM, Joseph Wang wrote:
>>
>> [    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

The only thing that comes to my mind and that might tie firmware with 
the machine driver is the use of this:

fmt = SND_SOC_DAIFMT_LEFT_J | SND_SOC_DAIFMT_NB_NF
				| SND_SOC_DAIFMT_CBS_CFS;

I am not aware of any other drivers using LEFT_J, why can't you use I2S 
for 2ch links?

>
> 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.
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@alsa-project.org
> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
>

  parent reply	other threads:[~2016-12-05 18:10 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
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 [this message]
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=30f62f0d-1e3e-0839-8d85-df9e209b5cf9@linux.intel.com \
    --to=pierre-louis.bossart@linux.intel.com \
    --cc=CTLIN0@nuvoton.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).