From: Vinod Koul <vinod.koul@intel.com>
To: Tyler Yeomans <tyeo098@gmail.com>,
"Girdwood, Liam R" <liam.r.girdwood@intel.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
Antonio Ospite <ao2@ao2.it>, Nicolas George <george@nsup.org>,
"Nikula, Jarkko" <jarkko.nikula@intel.com>
Subject: Re: Intel Baytrail Linux Audio
Date: Wed, 8 Jul 2015 09:06:04 +0530 [thread overview]
Message-ID: <20150708033604.GM11002@localhost> (raw)
In-Reply-To: <559C3F4A.5030307@gmail.com>
On Tue, Jul 07, 2015 at 05:06:18PM -0400, Tyler Yeomans wrote:
> Vinod,
>
> I have attached ... what I think is what you're looking for with
> regards to the dynamic debug output.
Sorry I should have been clearer. The dynamic debug allows you to enbale
debug logs without recompiling
So after boot:
echo -n 'module snd_soc_sst_mfld_platform +p' > /sys/kernel/debug/dynamic_debug/control
this will enable prints, so when you start audio, the firmware would be
downloaded, and please grab the dmesg ouput and send...
>
> Additionally, the interrupts report as follows... none:
> $ cat /proc/interrupts | grep sst
> 7: 0 0 0 0 IO-APIC
> 28-fasteoi intel_sst_driver
So this makes me suspect interrupts, we should have seen something here
Liam, do you know how whats different in BYT devices from interrupts. I
recall Jarkko saying some issues with the way interrupts are exposed..?
--
~Vinod
>
> Tyler
>
> On 07/07/2015 01:08 PM, Vinod Koul wrote:
> >On Tue, Jul 07, 2015 at 10:00:31AM -0400, Tyler Yeomans wrote:
> >>Vinod,
> >>
> >>I am using the ssp0 firmware from:
> >>https://git.kernel.org/cgit/linux/kernel/git/vkoul/firmware.git/tree/intel?h=byt.
> >Hi Tyler,
> >
> >Can you enable logs (dynamic debug should help), I want to see if FW
> >download was success or not
> >
> >Also cat /proc/interrupts to see if we are getting interrupts
> >
> >Thanks
>
next prev parent reply other threads:[~2015-07-08 3:34 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 [this message]
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=20150708033604.GM11002@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.