From: Tyler Yeomans <tyeo098@gmail.com>
To: Vinod Koul <vinod.koul@intel.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: Tue, 07 Jul 2015 10:00:31 -0400 [thread overview]
Message-ID: <559BDB7F.9010105@gmail.com> (raw)
In-Reply-To: <20150707031950.GD11002@localhost>
Vinod,
I am using the ssp0 firmware from:
https://git.kernel.org/cgit/linux/kernel/git/vkoul/firmware.git/tree/intel?h=byt.
Thanks-
Tyler
On 07/06/2015 11:19 PM, Vinod Koul wrote:
> On Mon, Jul 06, 2015 at 10:29:34AM -0400, Tyler Yeomans wrote:
>> Hello all,
>>
>> Apparently I'm in the same boat as Nicolas is.
>> I've attached my dmesg output.
>> Everything seems to be generating but I am not able to get any sound
>> output.
>> Between the 37 second mark and the 617 second mark I had routed the
>> FE to BE via the commands:
>>
>> amixer -c0 sset 'codec_out0 mix 0 pcm0_in' on
>> amixer -c0 sset 'media0_out mix 0 media1_in' on
> ok that seems fine
>> Although it appears that did not work:
>> [ 719.834922] intel_sst_acpi 80860F28:00: Wait timed-out
>> condition:0x0, msg_id:0x1 fw_state 0x3
>> [ 719.834932] intel_sst_acpi 80860F28:00: fw returned err -16
> I don't think so, since you were able to start the card, that part worked :)
>
> The error is coming from FW here and seems unresponsive.
>
> Which firmware are you using?
>
> Second suspicion is for interrupts, if they are not mapped well we might see
> these.
>
> Jarkko I remember that some board have to be configured properly for
> interrupts, can you explaian the subtleties involved here
>
> --
> ~Vinod
next prev parent reply other threads:[~2015-07-07 14:00 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 [this message]
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
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=559BDB7F.9010105@gmail.com \
--to=tyeo098@gmail.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=vinod.koul@intel.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