From: Vinod Koul <vinod.koul@intel.com>
To: Tyler Yeomans <tyeo098@gmail.com>,
liam.r.girdwood@intel.com, jarkko.nikula@intel.com
Cc: alsa-devel@alsa-project.org
Subject: Re: Intel Baytrail Linux Audio
Date: Wed, 24 Jun 2015 15:41:15 +0530 [thread overview]
Message-ID: <20150624101115.GI19530@localhost> (raw)
In-Reply-To: <5589D025.7090700@gmail.com>
On Tue, Jun 23, 2015 at 05:31:17PM -0400, Tyler Yeomans wrote:
> Hello Vinod,
Pls cc relevant mailing list, in this case alsa. I have cced Liam and Jarrko
as well
>
> I am writing to you because unfortunately I have exhausted my search
> and I am unable to get ALSA sound working on my Baytrail minipc.
> My dmesg only reports that: byt-rt5640 byt-rt5640: ASoC: CPU DAI
> baytrail-pcm-audio not registered
> aplay -l rightfully says there are no sound cards as the driver is
> not registered.
Can you give more details of your, does this enable HDA audio or I2S audio?
> I have acquired the firmware file from the chromium repo here (https://kernel.googlesource.com/pub/scm/linux/kernel/git/firmware/linux-firmware/+/refs/heads/master/intel/fw_sst_0f28.bin-48kHz_i2s_master)
> as was directed by the OP in this forum post:
> http://ubuntuforums.org/showthread.php?t=2254631
>
> But unfortunately it seems the driver is still not loading
> correctly, even on Ubuntu 15.04 with ALSA 1.0.28
Do you have dmesg for us to look at so that we can see what might be going
wrong
> I see on gmane you are working on Skylake driver, could your work
> there possibly be backported to the Baytrail/RT5640 chipset?
No they are entirely different hw, so it will not work. We have uostream BYT
driver and they should work
--
~Vinod
next parent reply other threads:[~2015-06-24 10:09 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5589D025.7090700@gmail.com>
2015-06-24 10:11 ` Vinod Koul [this message]
2015-06-24 14:24 ` Intel Baytrail Linux Audio 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
2015-07-03 12:10 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
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
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=20150624101115.GI19530@localhost \
--to=vinod.koul@intel.com \
--cc=alsa-devel@alsa-project.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.