Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Vinod Koul <vinod.koul@intel.com>
To: Tyler Yeomans <tyeo098@gmail.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	Antonio Ospite <ao2@ao2.it>, Nicolas George <george@nsup.org>,
	"Girdwood, Liam R" <liam.r.girdwood@intel.com>,
	"Nikula, Jarkko" <jarkko.nikula@intel.com>
Subject: Re: Intel Baytrail Linux Audio
Date: Fri, 10 Jul 2015 09:36:23 +0530	[thread overview]
Message-ID: <20150710040623.GY836@localhost> (raw)
In-Reply-To: <559EC436.30900@gmail.com>

On Thu, Jul 09, 2015 at 02:57:58PM -0400, Tyler Yeomans wrote:
> Antonio/Vinod,
> 
> I have made the change in the sst-acpi.c file for the atom specific boards.
> I've attached the dmesg output here with dynamic debug enabled.
> 
> To clarify-
> 
> snd-intel-sst-core is loaded
> FE-BE fix has been applied
> I'm using the ssp0 firmware.
> 
> Interrupts are still 0
> 
> Still no sound.
> 
> Would leaving the device on and providing remote access (i.e though
> teamviewer) assist in any way?

The fw download seems to fail on your device, which can also be due to
incorrect interrupt mapping...

[   20.386850] intel_sst_acpi 80860F28:00: Wait timed-out condition:0x0,
msg_id:0x1 fw_state 0x3
[   20.386862] intel_sst_acpi 80860F28:00: fw returned err -16
[   20.386873] sst-mfld-platform sst-mfld-platform: Enter: enable=1
port_name=ssp2-port
[   20.752559] intel_sst_acpi 80860F28:00: Wait timed-out condition:0x0,
msg_id:0x1 fw_state 0x3
[   20.752570] intel_sst_acpi 80860F28:00: fw returned err -16
[   21.163378] intel_sst_acpi 80860F28:00: Wait timed-out condition:0x0,
msg_id:0x0 fw_state 0x1
[   21.163388] intel_sst_acpi 80860F28:00: fw download failed -16

Can you tell me which device you have, what was preinstalled on it

-- 
~Vinod

  parent reply	other threads:[~2015-07-10  4:04 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-03 12:10 Intel Baytrail Linux Audio Koul, Vinod
2015-07-03 12:36 ` Antonio Ospite
2015-07-03 13:06   ` Nicolas George
     [not found]     ` <559A90CE.2030105@gmail.com>
     [not found]       ` <20150707031950.GD11002@localhost>
2015-07-07 14:00         ` Tyler Yeomans
2015-07-07 17:08           ` Vinod Koul
2015-07-07 21:06             ` Tyler Yeomans
2015-07-08  3:36               ` Vinod Koul
2015-07-08  8:23                 ` Antonio Ospite
2015-07-08 14:30                   ` Tyler Yeomans
2015-07-08 16:21                     ` Antonio Ospite
2015-07-08 16:32                       ` Tyler Yeomans
2015-07-08 20:17                         ` Antonio Ospite
2015-07-08 20:24                           ` tyeo098
     [not found]                           ` <559EC436.30900@gmail.com>
2015-07-10  4:06                             ` Vinod Koul [this message]
2015-07-10 12:41                               ` Tyler Yeomans
2015-07-13 17:06                               ` Tyler Yeomans
2015-07-14  8:47                                 ` Vinod Koul
2015-07-23 15:24                                   ` Tyler Yeomans
2015-07-10  4:03                     ` Vinod Koul
2015-07-08 20:57                   ` Luka Karinja
     [not found]                   ` <559D88C1.3010504@bazdara.com>
2015-07-10  4:00                     ` Vinod Koul
2015-07-10 15:24                       ` Luka Karinja
  -- strict thread matches above, loose matches on Subject: below --
2015-07-03 13:43 Koul, Vinod
     [not found] <5589D025.7090700@gmail.com>
2015-06-24 10:11 ` Vinod Koul
2015-06-24 14:24   ` Tyler Yeomans
2015-06-24 16:03     ` Vinod Koul
2015-06-24 17:40       ` Tyler Yeomans
2015-06-25  6:38       ` Jarkko Nikula
2015-06-30 18:24         ` Tyler Yeomans
2015-06-30 22:57         ` Tyler Yeomans
2015-07-02 18:40           ` Nicolas George
2015-07-03  8:51             ` Liam Girdwood
2015-07-03  9:08               ` Antonio Ospite
2015-07-03  9:46                 ` Nicolas George
2015-07-03 10:32                   ` Antonio Ospite
2015-07-03 11:12                     ` Nicolas George

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=20150710040623.GY836@localhost \
    --to=vinod.koul@intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=ao2@ao2.it \
    --cc=george@nsup.org \
    --cc=jarkko.nikula@intel.com \
    --cc=liam.r.girdwood@intel.com \
    --cc=tyeo098@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