Received: by 2002:a05:6a10:206:0:0:0:0 with SMTP id 6csp778563pxj; Thu, 13 May 2021 17:16:14 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyjv6Nj5S10C+uqBLAyjxikMSXkL3wilKoTZ+EBgmrgeU3RGh5i4LgSd+LvNXkcVAjpYMIs X-Received: by 2002:a17:906:28d4:: with SMTP id p20mr46444994ejd.552.1620951373919; Thu, 13 May 2021 17:16:13 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1620951373; cv=none; d=google.com; s=arc-20160816; b=bxXjpq/elhsXvq3oLBtBxCFav7WSAKjnsNPdHctgu3DzDPWvj65BkDPkqA6IprNrD8 lqhtiLkXkxGM6XbmIbYERrfhDh/n2wiVaJj57/Nbp3L2JAYYNIizlerYgaYjSKqXn7je kayHDUdzKDRaNvdinrwz9P5OSjTp0FL+Cu/qOmW4uH3l04tqV6nPahUPpEDeyzDdGG/v d0VehAbzjBzhCX7J/gYVY7NvTGQns8OOTqe/lTywsodHBq2YYfSWCFQDybIZsIX6pUI4 T7qOqZqQVKelHBtw2/VhJ8AgyrP/KQqC3UFxuL3BPh+2fkf70Q6kEhbp5iwYv4Gmj4m0 H0/Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:cc:to:subject :message-id:date:from:in-reply-to:references:mime-version :dkim-signature; bh=zN/lAFX1fKcTkEtnGlN/FwvIbQ//6AFIM7RPilCCdXk=; b=m02hamm8fXS8DMhILuNQpbdBiQQqZ2liBv0FRIfm+1lt42QaFdMqDNTUgo+qKtna0f neE4R9FSDGx85Yq9MRFCHRQAqCKgtVv1kPE1IXIbvgNBEnuwHGljWqxmagtYC6NfwQVh mK1Oi3W7TA2sfdqZ8UC/Z+xmVEo4amyZlEZG+zCIzvzrIZonTuXyj7KSD0bFsbwkhaVt aKfpso8E/1jgt/xQLLXvY2o5Bt/6iFk+UifmGlq47Fni/Sk3Y4LV58C4K1SSvwIKCUtE RZJNzUK4SLVy5GrkZsUXKYHOSyPIcfeJHk7WeEIVB+hu57a0wV5hyost4xCd6REjCaU1 qCvA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=sFkrwCOU; spf=pass (google.com: domain of linux-bluetooth-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-bluetooth-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id e20si4232412eds.560.2021.05.13.17.15.48; Thu, 13 May 2021 17:16:13 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-bluetooth-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=sFkrwCOU; spf=pass (google.com: domain of linux-bluetooth-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-bluetooth-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231920AbhEMUaz (ORCPT + 99 others); Thu, 13 May 2021 16:30:55 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:39204 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232375AbhEMUar (ORCPT ); Thu, 13 May 2021 16:30:47 -0400 Received: from mail-yb1-xb2d.google.com (mail-yb1-xb2d.google.com [IPv6:2607:f8b0:4864:20::b2d]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 10464C061763 for ; Thu, 13 May 2021 13:29:28 -0700 (PDT) Received: by mail-yb1-xb2d.google.com with SMTP id e128so637878ybf.6 for ; Thu, 13 May 2021 13:29:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=zN/lAFX1fKcTkEtnGlN/FwvIbQ//6AFIM7RPilCCdXk=; b=sFkrwCOURCuAfEWOGxZq3EGizPEaB9fvaIy9AJ/v240GzvfNlInrfGS5t6r/RrEbf6 MVGzLW0hZYatGZLaP2sGJgy7/KuHz84ZuTLu1rj4sIYq5dMVBAoF78UCgH1DLLTK/ByX B/5x5nE5BO43aL/L1rVxjYolvX69urKYUL4kJrdilWdGi6kQ7MANbzmV/4MQhoxKhzCc FTNq8Xeg5zIkpg/9VbkC/2MXJ/JUQaXjw2Wmz56UCqDoDVc1VqppjttACteUr6JuUACm fdza/v7f/s+7rTVYSa3A7ImlXLa0Dj1kh8+622FUailOJ7sVvo4/sGTE1r9/Wc2g3n/H pLDQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=zN/lAFX1fKcTkEtnGlN/FwvIbQ//6AFIM7RPilCCdXk=; b=Cc445WFpM8SMCY6kDFACNCOzFfE5pbaECkKQfKLKWHIgAf8xl59oTBagXJ93kKPfte uGGxut8A8hcUDwU/rdKRccr53Tq26GUAfQVxV0H6516Db8o21HBoFttXbW+PWpiypSvM LppJX+ARi68AlomuCR5jc1AInTJjFrbbJCBAOSnI7yuu5nwrEhyHvo+3ROxPxhohOQvK fshfJlRhvSH4yxi76P3uXN6NpML6LcwUAbMrR/eUtWKrpB29QVnh74F4QUhVS792HnsQ a06MUC+damXolE3LKLuX7qngjSir3pd+M61stgzV/TwiiThUvs/275mZbcdx5IdTMxor nVXg== X-Gm-Message-State: AOAM533h0jt3CsRI9ga4jX/9g+Ne6mtkthrB1YaqHqo0Oqa0IfLPqHQw 1Ek+QK33NdlZVrcXSjCEVXthhWAd50sCEnLRcBcVYmGs X-Received: by 2002:a25:ad8b:: with SMTP id z11mr30899557ybi.91.1620937767218; Thu, 13 May 2021 13:29:27 -0700 (PDT) MIME-Version: 1.0 References: <20210430230501.603111-1-luiz.dentz@gmail.com> <20210511042654.8549-1-youling257@gmail.com> In-Reply-To: From: Luiz Augusto von Dentz Date: Thu, 13 May 2021 13:29:14 -0700 Message-ID: Subject: Re: [PATCH] Bluetooth: btusb: Fix failing to init controllers with operation firmware To: Marcel Holtmann Cc: youling257 , "linux-bluetooth@vger.kernel.org" Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Precedence: bulk List-ID: X-Mailing-List: linux-bluetooth@vger.kernel.org Hi Marcel, On Thu, May 13, 2021 at 8:16 AM Marcel Holtmann wrote= : > > Hi Luiz, > > >> I test this patch no help. rmmod btusb, modprobe btusb. > >> > >> > >> [ 7.661739] Bluetooth: Core ver 2.22 > >> [ 7.661762] NET: Registered protocol family 31 > >> [ 7.661763] Bluetooth: HCI device and connection manager initialize= d > >> [ 7.661767] Bluetooth: HCI socket layer initialized > >> [ 7.661768] Bluetooth: L2CAP socket layer initialized > >> [ 7.661772] Bluetooth: SCO socket layer initialized > >> [ 7.686106] usbcore: registered new interface driver btusb > >> [ 7.689317] iwlwifi 0000:07:00.0: Detected Intel(R) Wi-Fi 6 AX200 1= 60MHz, REV=3D0x340 > >> [ 7.689789] Bluetooth: hci0: Firmware revision 0.0 build 118 week 1= 5 2021 > >> [ 7.694911] bluetooth hci0: Direct firmware load for intel/ibt-20-0= -0.sfi failed with error -2 > >> > >> [ 230.746397] usbcore: registered new interface driver btusb > >> [ 230.750827] Bluetooth: hci0: Firmware revision 0.0 build 118 week 1= 5 2021 > >> [ 230.756450] bluetooth hci0: Direct firmware load for intel/ibt-20-0= -0.sfi failed with error -2 > > > > The error shall be ignored in this case since it comes from > > request_firmware we can't prevent it, if you don't see another error > > after that means it can be ignored, that said perhaps we detect it > > sooner by either attempting to stat the file or perhaps check if > > revision comes back as all 0. > > any reason you don=E2=80=99t use firmware_request_nowarn()? Yep, totally missed that one exists, I will send a patch making use of it. --=20 Luiz Augusto von Dentz