Return-path: Received: from sabertooth01.qualcomm.com ([65.197.215.72]:6931 "EHLO sabertooth01.qualcomm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750869AbaLBHJV (ORCPT ); Tue, 2 Dec 2014 02:09:21 -0500 From: Kalle Valo To: Michal Kazior CC: "ath10k@lists.infradead.org" , linux-wireless Subject: Re: [PATCH v3 1/7] ath10k: create ath10k_core_init_features() References: <20141201144400.18248.62714.stgit@potku.adurom.net> <20141201144458.18248.28568.stgit@potku.adurom.net> Date: Tue, 2 Dec 2014 09:09:06 +0200 In-Reply-To: (Michal Kazior's message of "Tue, 2 Dec 2014 07:58:09 +0100") Message-ID: <87a936plyl.fsf@kamboji.qca.qualcomm.com> (sfid-20141202_080931_684313_AF5904C3) MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: linux-wireless-owner@vger.kernel.org List-ID: Michal Kazior writes: > On 1 December 2014 at 15:44, Kalle Valo wrote: > [...] >> int ath10k_core_start(struct ath10k *ar, enum ath10k_firmware_mode mode) >> @@ -1046,7 +1047,12 @@ static int ath10k_core_probe_fw(struct ath10k *ar) >> return ret; >> } >> >> - ath10k_core_init_max_sta_count(ar); >> + ret = ath10k_core_init_firmware_features(ar); >> + if (ret) { >> + ath10k_err(ar, "fatal problem with firmware features: %d\n", >> + ret); >> + return ret; > > I think you should call ath10k_core_free_firmware_files() and > ath10k_hif_power_down() before returning (similar to how > ath10k_core_start() failure is handled). Indeed. I'll fix that in v4. -- Kalle Valo