From: Kalle Valo <kvalo@qca.qualcomm.com> To: <ath10k@lists.infradead.org> Cc: <linux-wireless@vger.kernel.org> Subject: [PATCH v7 09/10] ath10k: different fw file name for sdio Date: Thu, 13 Apr 2017 11:30:46 +0300 [thread overview] Message-ID: <149207224665.4590.10421467367917959312.stgit@potku.adurom.net> (raw) In-Reply-To: <149207201649.4590.5821794186383265138.stgit@potku.adurom.net> From: Erik Stromdahl <erik.stromdahl@gmail.com> Since both SDIO based chipsets will use different firmware from the PCIe and AHB chipsets, the fw file name must be different depending on bus type. The new firmware names are: For PCIe and AHB: firmware-<api_version>.bin (same as before) For SDIO: firmware-sdio-<api_version>.bin Signed-off-by: Erik Stromdahl <erik.stromdahl@gmail.com> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> --- drivers/net/wireless/ath/ath10k/core.c | 13 ++++++++++++- 1 file changed, 12 insertions(+), 1 deletion(-) diff --git a/drivers/net/wireless/ath/ath10k/core.c b/drivers/net/wireless/ath/ath10k/core.c index 23cf6b191770..9ae20680bcb6 100644 --- a/drivers/net/wireless/ath/ath10k/core.c +++ b/drivers/net/wireless/ath/ath10k/core.c @@ -1398,7 +1398,18 @@ int ath10k_core_fetch_firmware_api_n(struct ath10k *ar, const char *name, static void ath10k_core_get_fw_name(struct ath10k *ar, char *fw_name, size_t fw_name_len, int fw_api) { - scnprintf(fw_name, fw_name_len, "%s-%d.bin", ATH10K_FW_FILE_BASE, fw_api); + switch (ar->hif.bus) { + case ATH10K_BUS_SDIO: + scnprintf(fw_name, fw_name_len, "%s-%s-%d.bin", + ATH10K_FW_FILE_BASE, ath10k_bus_str(ar->hif.bus), + fw_api); + break; + case ATH10K_BUS_PCI: + case ATH10K_BUS_AHB: + scnprintf(fw_name, fw_name_len, "%s-%d.bin", + ATH10K_FW_FILE_BASE, fw_api); + break; + } } static int ath10k_core_fetch_firmware_files(struct ath10k *ar)
WARNING: multiple messages have this Message-ID (diff)
From: Kalle Valo <kvalo@qca.qualcomm.com> To: ath10k@lists.infradead.org Cc: linux-wireless@vger.kernel.org Subject: [PATCH v7 09/10] ath10k: different fw file name for sdio Date: Thu, 13 Apr 2017 11:30:46 +0300 [thread overview] Message-ID: <149207224665.4590.10421467367917959312.stgit@potku.adurom.net> (raw) In-Reply-To: <149207201649.4590.5821794186383265138.stgit@potku.adurom.net> From: Erik Stromdahl <erik.stromdahl@gmail.com> Since both SDIO based chipsets will use different firmware from the PCIe and AHB chipsets, the fw file name must be different depending on bus type. The new firmware names are: For PCIe and AHB: firmware-<api_version>.bin (same as before) For SDIO: firmware-sdio-<api_version>.bin Signed-off-by: Erik Stromdahl <erik.stromdahl@gmail.com> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> --- drivers/net/wireless/ath/ath10k/core.c | 13 ++++++++++++- 1 file changed, 12 insertions(+), 1 deletion(-) diff --git a/drivers/net/wireless/ath/ath10k/core.c b/drivers/net/wireless/ath/ath10k/core.c index 23cf6b191770..9ae20680bcb6 100644 --- a/drivers/net/wireless/ath/ath10k/core.c +++ b/drivers/net/wireless/ath/ath10k/core.c @@ -1398,7 +1398,18 @@ int ath10k_core_fetch_firmware_api_n(struct ath10k *ar, const char *name, static void ath10k_core_get_fw_name(struct ath10k *ar, char *fw_name, size_t fw_name_len, int fw_api) { - scnprintf(fw_name, fw_name_len, "%s-%d.bin", ATH10K_FW_FILE_BASE, fw_api); + switch (ar->hif.bus) { + case ATH10K_BUS_SDIO: + scnprintf(fw_name, fw_name_len, "%s-%s-%d.bin", + ATH10K_FW_FILE_BASE, ath10k_bus_str(ar->hif.bus), + fw_api); + break; + case ATH10K_BUS_PCI: + case ATH10K_BUS_AHB: + scnprintf(fw_name, fw_name_len, "%s-%d.bin", + ATH10K_FW_FILE_BASE, fw_api); + break; + } } static int ath10k_core_fetch_firmware_files(struct ath10k *ar) _______________________________________________ ath10k mailing list ath10k@lists.infradead.org http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2017-04-13 8:30 UTC|newest] Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-04-13 8:28 [PATCH v7 00/10] ath10k: sdio support Kalle Valo 2017-04-13 8:28 ` Kalle Valo 2017-04-13 8:28 ` [PATCH v7 01/10] ath10k: htc: made static function public Kalle Valo 2017-04-13 8:28 ` Kalle Valo 2017-05-04 12:57 ` [v7,01/10] " Kalle Valo 2017-05-04 12:57 ` Kalle Valo 2017-04-13 8:29 ` [PATCH v7 02/10] ath10k: htc: rx trailer lookahead support Kalle Valo 2017-04-13 8:29 ` Kalle Valo 2017-04-13 8:29 ` [PATCH v7 03/10] ath10k: htc: move htc ctrl ep connect to htc_init Kalle Valo 2017-04-13 8:29 ` Kalle Valo 2017-04-13 8:29 ` [PATCH v7 04/10] ath10k: htc: refactorization Kalle Valo 2017-04-13 8:29 ` Kalle Valo 2017-04-13 8:29 ` [PATCH v7 05/10] ath10k: various sdio related definitions Kalle Valo 2017-04-13 8:29 ` Kalle Valo 2017-04-13 8:30 ` [PATCH v7 06/10] ath10k: add sdio extra initializations Kalle Valo 2017-04-13 8:30 ` Kalle Valo 2017-04-13 8:30 ` [PATCH v7 07/10] ath10k: sdio get target info Kalle Valo 2017-04-13 8:30 ` Kalle Valo 2017-04-13 8:30 ` [PATCH v7 08/10] ath10k: htc: ready_ext msg support Kalle Valo 2017-04-13 8:30 ` Kalle Valo 2017-04-13 8:30 ` Kalle Valo [this message] 2017-04-13 8:30 ` [PATCH v7 09/10] ath10k: different fw file name for sdio Kalle Valo 2017-04-13 8:31 ` [PATCH v7 10/10] ath10k: add initial SDIO support Kalle Valo 2017-04-13 8:31 ` Kalle Valo 2017-04-22 19:35 ` [PATCH v7 00/10] ath10k: sdio support Erik Stromdahl 2017-04-22 19:35 ` Erik Stromdahl
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=149207224665.4590.10421467367917959312.stgit@potku.adurom.net \ --to=kvalo@qca.qualcomm.com \ --cc=ath10k@lists.infradead.org \ --cc=linux-wireless@vger.kernel.org \ /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: linkBe 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.