On Wed, 08 Jul 2015 12:32:17 -0400 Tyler Yeomans tyeo098@gmail.com wrote:
Antonio,
Hmm... I have been running the driver like so: (from sound/soc/intel/common/sst-acpi.c) static struct sst_acpi_desc sst_acpi_baytrail_desc = { .drv_name = "baytrail-pcm-audio", .machines = baytrail_machines, .resindex_lpe_base = 0, .resindex_pcicfg_base = 1, .resindex_fw_base = 2,
- .irqindex_host_ipc = 0,* .sst_id = SST_DEV_ID_BYT, .resindex_dma_base = -1,
};
Which is what the patch at https://bugzilla.kernel.org/attachment.cgi?id=155341 says to do.
Ah, sorry, the info from that bug report is outdated, for the snd-intel-sst-acpi you have to change sound/soc/intel/atom/sst/sst_acpi.c:
diff --git a/sound/soc/intel/atom/sst/sst_acpi.c b/sound/soc/intel/atom/sst/sst_acpi.c index bb19b58..0badfa3 100644 --- a/sound/soc/intel/atom/sst/sst_acpi.c +++ b/sound/soc/intel/atom/sst/sst_acpi.c @@ -118,7 +118,7 @@ static const struct sst_res_info byt_rvp_res_info = { .mbox_size = 0x1000, .acpi_lpe_res_index = 0, .acpi_ddr_index = 2, - .acpi_ipc_irq_index = 5, + .acpi_ipc_irq_index = 0, };
static struct sst_platform_info byt_rvp_platform_data = {
I didn't have to do that because I fixed the DSDT.
However I also noticed in this file that its looking for the wrong firmware: static struct sst_acpi_mach baytrail_machines[] = { *{ "10EC5640", "byt-rt5640", "intel/fw_sst_0f28.bin-48kHz_i2s_master" },* { "193C9890", "byt-max98090", "intel/fw_sst_0f28.bin-48kHz_i2s_master" }, {} };
Which will not point to the SSP0 firmware uploaded by Vinod.
Just to recap: make sure to use the snd-intel-sst-acpi driver instead of snd-soc-sst-acpi as explained earlier in this thread: http://mailman.alsa-project.org/pipermail/alsa-devel/2015-July/094418.html
As a quick and dirty way to do it you can remove snd-soc-sst-acpi.ko from the modules installation dir.
A more robust solution would be to blacklist snd-soc-sst-acpi.
Ciao, Antonio