Received: by 2002:ac0:a582:0:0:0:0:0 with SMTP id m2-v6csp2248690imm; Wed, 3 Oct 2018 00:28:12 -0700 (PDT) X-Google-Smtp-Source: ACcGV61kTfSP8LjATMN7yp3CYh8s5BkSuAPhlQ/PLVqR9skxNvhHc++AzAXUwdwmWj98Q9Fhvdhp X-Received: by 2002:a65:5188:: with SMTP id h8-v6mr184486pgq.288.1538551692135; Wed, 03 Oct 2018 00:28:12 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1538551692; cv=none; d=google.com; s=arc-20160816; b=w0NxiKckYaokyFsQIugpjOxfAdaUFR/vpcCqS9G9hTjQin0k7GnTpUf7dOsO6X7wXb yQGOF6KZWGo3U3u2qLVmU5dfaNPq21lRXi1PBWePkgmlnAXeV8fW2U7xVIxcSrZzbVHB e868c4HXgxAvkRrjhFaIflyVQlChrBNdXeuz8JyfvhMhPp3i/MHwN7N6YVmuYPFqjjs+ BlGW44yaBBp14KXuhYgm3nk/R4rtWYSjFoCzPqqStJT9U5g0FtM20oPOYqFsfsHL2fTX ZG0Oci7M9DKkLk3Zif0aVIQzuD277hbINMbgo41B4Qzyx9fRD26gg9y8YTUEA2YPY+cq gReA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:to:references:message-id :content-transfer-encoding:cc:date:in-reply-to:from:subject :mime-version; bh=VgiUulaKWv/yAHidVeuSvTEm/ORp66PC6rVdi3MSMvY=; b=xXoeczRPA5JTHiP+anu7E7ZmlwvG7/7My+Np+azNL2ieiw4oYyqyt+F5W4a1eWOZip pFBQAIe5nk53/lWtI2he9Qe3ahlZHNemrvw3BDteup7bNTv4JdedB+RT42dE1QJ3Xhk4 Ds6DqfAEUo0UDa4a7o3OVizBhjO2HW/YjBhJ23CwAVgHZmf+8l7N7xHPEHxoI61xSVnM ASmMas/ViXF1LR6RMj9/+knRiPp2WaYdKcMBEPJbX6z1L9tFH85+e/HJBE6zEqaR/Xu+ iuFFdWRiPyMMJF5pYlP0i6Z5IQVFqo2H1TEMLcwKHfzBA/9Y3qV4ktl8hpWuud8DFnSU SUqw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=canonical.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id i21-v6si648704pgj.51.2018.10.03.00.27.56; Wed, 03 Oct 2018 00:28:12 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=canonical.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726769AbeJCOOz convert rfc822-to-8bit (ORCPT + 99 others); Wed, 3 Oct 2018 10:14:55 -0400 Received: from youngberry.canonical.com ([91.189.89.112]:56031 "EHLO youngberry.canonical.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726672AbeJCOOz (ORCPT ); Wed, 3 Oct 2018 10:14:55 -0400 Received: from mail-pf1-f198.google.com ([209.85.210.198]) by youngberry.canonical.com with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.76) (envelope-from ) id 1g7bZQ-0007hM-Hw for linux-kernel@vger.kernel.org; Wed, 03 Oct 2018 07:27:44 +0000 Received: by mail-pf1-f198.google.com with SMTP id b22-v6so2242413pfc.18 for ; Wed, 03 Oct 2018 00:27:44 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=rwvN3xFgqX8djnx4/f40EwH2bHf5qGLUn3YQ6V1KyAY=; b=MOZiIjY3tIdviwXYo8UqGf5faHcJObagZlWHpM0lzGkgwaorXCcZVHlyqvmNyB/KOy XKQ4qLDUcmQxNGkMVbXwU7S9hXkbzs2Cwu6nGw037o5TpC1w9LiOsj/jRKjf4JaMnDxJ KE+sGCuuboesGTNauEnRpb4U2SqBtf4+dG79zZpQUFvrOWbmb7wb3AWmLSI+znrFrz2c J4DgNeVKDk8VG8N9uGjOpNOW6LXBYoSsQWten10Wi2gfRcomqOMuWob1OQ0/D1wPsNmH NY9xPIAVGJCAohmKhAcNvq/fokjoGzrKWZpN3ASZzM7U1yE+4UW/Y4FLHj0QGBajlHOJ C4CA== X-Gm-Message-State: ABuFfogU0H1T4bfTp0JUeYGNn4aB74RPylcKzlfxs+APx49nram2n7OI OfEeeAmfQBROJH20TopwopIGM8Vc5L9k3SxieGDcmiMY0JDRVY/Z78AlkYVly0UfJJwE4ttqvkr aUhlIekgj+DfGAAIej8n2qu2+tjjPkTCEnrabcR2mGw== X-Received: by 2002:a63:cc04:: with SMTP id x4-v6mr169293pgf.33.1538551663150; Wed, 03 Oct 2018 00:27:43 -0700 (PDT) X-Received: by 2002:a63:cc04:: with SMTP id x4-v6mr169278pgf.33.1538551662779; Wed, 03 Oct 2018 00:27:42 -0700 (PDT) Received: from [10.101.46.95] (61-220-137-37.HINET-IP.hinet.net. [61.220.137.37]) by smtp.gmail.com with ESMTPSA id f13-v6sm792454pgq.63.2018.10.03.00.27.40 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 03 Oct 2018 00:27:42 -0700 (PDT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 12.0 \(3445.100.39\)) Subject: Re: [PATCH 3/3] iwlwifi: Load firmware exclusively for Intel WiFi From: Kai Heng Feng In-Reply-To: <2787bccf20b6f647de9f4cafae5fd223e771b167.camel@intel.com> Date: Wed, 3 Oct 2018 15:27:32 +0800 Cc: lkml , Johannes Berg , Emmanuel Grumbach , Intel Linux Wireless , Kalle Valo , "David S. Miller" , linux-wireless@vger.kernel.org, netdev@vger.kernel.org Content-Transfer-Encoding: 8BIT Message-Id: <81B978A9-270E-4C0B-BE67-D05899B1BC3B@canonical.com> References: <20181003071513.13004-3-kai.heng.feng@canonical.com> <2787bccf20b6f647de9f4cafae5fd223e771b167.camel@intel.com> To: Luciano Coelho X-Mailer: Apple Mail (2.3445.100.39) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > On Oct 3, 2018, at 3:24 PM, Luciano Coelho wrote: > > On Wed, 2018-10-03 at 15:15 +0800, Kai-Heng Feng wrote: >> To avoid the firmware loading race between Bluetooth and WiFi on Intel >> 8260, load firmware exclusively when BT_INTEL is enabled. >> >> Signed-off-by: Kai-Heng Feng >> --- > > Where is this coming from? Can you explain what "the firmware loading > race" is? Looks like the patch is not correctly threaded. I’ll resend the series. > > >> .../net/wireless/intel/iwlwifi/pcie/trans.c | 37 ++++++++++++++++++- >> 1 file changed, 36 insertions(+), 1 deletion(-) >> >> diff --git a/drivers/net/wireless/intel/iwlwifi/pcie/trans.c b/drivers/net/wireless/intel/iwlwifi/pcie/trans.c >> index cc8c53dc0ab6..c30d3989e2a8 100644 >> --- a/drivers/net/wireless/intel/iwlwifi/pcie/trans.c >> +++ b/drivers/net/wireless/intel/iwlwifi/pcie/trans.c >> @@ -71,6 +71,7 @@ >> #include >> #include >> #include >> +#include > > I don't see this upstream. Is it something that was recently added? > Looks odd... > > Regardless, this should also be protected on CONFIG_BT_INTEL. Thanks, I’ll update this one. > > >> #include "iwl-drv.h" >> #include "iwl-trans.h" >> @@ -1335,6 +1336,10 @@ static int iwl_trans_pcie_start_fw(struct iwl_trans *trans, >> bool hw_rfkill; >> int ret; >> >> +#if IS_ENABLED(CONFIG_BT_INTEL) >> + void (*firmware_lock_func)(void); >> + void (*firmware_unlock_func)(void); >> +#endif >> /* This may fail if AMT took ownership of the device */ >> if (iwl_pcie_prepare_card_hw(trans)) { >> IWL_WARN(trans, "Exit HW not ready\n"); >> @@ -1394,6 +1399,7 @@ static int iwl_trans_pcie_start_fw(struct iwl_trans *trans, >> * RF-Kill switch is toggled, we will find out after having loaded >> * the firmware and return the proper value to the caller. >> */ >> + > > Stray empty line. > >> iwl_enable_fw_load_int(trans); >> >> /* really make sure rfkill handshake bits are cleared */ >> @@ -1401,8 +1407,37 @@ static int iwl_trans_pcie_start_fw(struct iwl_trans *trans, >> iwl_write32(trans, CSR_UCODE_DRV_GP1_CLR, CSR_UCODE_SW_BIT_RFKILL); >> >> /* Load the given image to the HW */ >> - if (trans->cfg->device_family >= IWL_DEVICE_FAMILY_8000) >> + if (trans->cfg->device_family >= IWL_DEVICE_FAMILY_8000) { >> +#if IS_ENABLED(CONFIG_BT_INTEL) >> + firmware_lock_func = symbol_request(btintel_firmware_lock); >> + firmware_unlock_func = symbol_request(btintel_firmware_unlock); >> + if (!firmware_lock_func || !firmware_unlock_func) { >> + if (firmware_lock_func) { >> + symbol_put(btintel_firmware_lock); >> + firmware_lock_func = NULL; >> + } >> + >> + if (firmware_unlock_func) { >> + symbol_put(btintel_firmware_unlock); >> + firmware_unlock_func = NULL; >> + } >> + } >> + >> + if (firmware_lock_func) >> + firmware_lock_func(); >> +#endif >> ret = iwl_pcie_load_given_ucode_8000(trans, fw); >> + >> +#if IS_ENABLED(CONFIG_BT_INTEL) >> + if (firmware_unlock_func) { >> + firmware_unlock_func(); >> + symbol_put(btintel_firmware_lock); >> + firmware_lock_func = NULL; >> + symbol_put(btintel_firmware_unlock); >> + firmware_unlock_func = NULL; >> + } >> +#endif >> + } >> else >> ret = iwl_pcie_load_given_ucode(trans, fw); >> > > I'm not sure I like adding this BT-specific stuff here, especially not > without a detailed explanation. > > Did you also send the other patches in this series to linux-wireless? I > can't see them… I’ll resend one soon. Thanks! Kai-Heng > > -- > Cheers, > Luca.