Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751967AbbBEUMg (ORCPT ); Thu, 5 Feb 2015 15:12:36 -0500 Received: from mga09.intel.com ([134.134.136.24]:17567 "EHLO mga09.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751428AbbBEUMe (ORCPT ); Thu, 5 Feb 2015 15:12:34 -0500 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.09,525,1418112000"; d="scan'208";a="647964914" From: Kevin Strasser To: alsa-devel@alsa-project.org Cc: Liam Girdwood , Mark Brown , Vinod Koul , Mengdong Lin , linux-kernel@vger.kernel.org, Yang Fang Subject: [PATCH v2] ASoC: Intel: fix sst firmware path for cht-bsw-rt5672 Date: Thu, 5 Feb 2015 12:12:07 -0800 Message-Id: <1423167127-16029-1-git-send-email-kevin.strasser@linux.intel.com> X-Mailer: git-send-email 1.9.1 In-Reply-To: <1423078507-30032-1-git-send-email-kevin.strasser@linux.intel.com> References: <1423078507-30032-1-git-send-email-kevin.strasser@linux.intel.com> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1180 Lines: 30 All sst firmware is provided under the intel directory of the linux-firmware tree. By default this directory structure is kept when installing on a target system. Change the path to expect a default linux-firmware installation. Signed-off-by: Kevin Strasser --- sound/soc/intel/sst/sst_acpi.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sound/soc/intel/sst/sst_acpi.c b/sound/soc/intel/sst/sst_acpi.c index 2ac72eb..b336013 100644 --- a/sound/soc/intel/sst/sst_acpi.c +++ b/sound/soc/intel/sst/sst_acpi.c @@ -350,7 +350,7 @@ static struct sst_machines sst_acpi_bytcr[] = { /* Cherryview-based platforms: CherryTrail and Braswell */ static struct sst_machines sst_acpi_chv[] = { - {"10EC5670", "cht-bsw", "cht-bsw-rt5672", NULL, "fw_sst_22a8.bin", + {"10EC5670", "cht-bsw", "cht-bsw-rt5672", NULL, "intel/fw_sst_22a8.bin", &chv_platform_data }, {}, }; -- 1.9.1 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/