Received: by 2002:a05:6a10:206:0:0:0:0 with SMTP id 6csp840758pxj; Fri, 28 May 2021 17:53:25 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyV2W/3nQf+LtEeFS8PzctZYnOCvw2EO+jnxUT1qvbC2g3Ke3LhAy7oCybx5io0K3Qx7sUS X-Received: by 2002:a05:6e02:dce:: with SMTP id l14mr9587019ilj.153.1622249605359; Fri, 28 May 2021 17:53:25 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1622249605; cv=none; d=google.com; s=arc-20160816; b=aszPPra2/syxdbd1PBBDFoQSXvhAFSe6nhBjiCNSRI3WPqRL6CPqAsrFuCrkd9wCN3 USL2Uo13y2wYMeda315bB1WE2ZYycxxw/cUQJaZSpX3U9a7EHDZnLE/ujtfpmM+RqOfj EessOrO4cggGu72uR/JdJ7fKgvkcfBHyh2xWqyXSGvyOOGI3WeGHh7jnGpj+L0VyON8t Pd+fJ9CdLus129w7uwg/dLtf9y3dJk73TgybOzvVK07lZRUkgo/LNMCN4E6MgZrtXHwq i9Pyz41eparriLuwXp6zU/c108Mv6JJ4rUK7gqjhQxRyulAGUwrBGVoPwAaQEGsxpt3s mvPQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:mime-version:message-id:subject:cc:to:reply-to :from:date:dkim-signature; bh=WoKgEn2IyxLjdF8NtKOrVUYCJwcw/twhZ+cvmhP9ag0=; b=x5nfFYmBBbjl3omyZ9HNhg1Thgt7tLenRXDhTl7AJlBvuTbiLc/5uTIcoWJ+VPtXzj TY9qm0d1EYo37gaTwryA6XaoWYwmN6ZiLC9lr9b/FRtnVVXuG/dW+1r/FFMqPgzWmid0 UtxAmHAQWhAAOHcg6qZ1x4/4aNL9GonB6FGO/7iItCvJQryJi0tOiB0RI45tZ+EnJDz9 4/HVE21dv+d2jdlOytZJf6s/CwW0hQ8ox77UQe1Z2at+RinkJgMDWdEyPlLQ6SKO/NME lQxQMEE/LVnKAvqhDda6iv4F9JVBa86GVame8/mFx5Qt+1KHjVkyhHcCE6QlWQueAyeI g2pw== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@panix.com header.s=panix header.b=bzKaMsj6; 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id a13si7010541ilf.41.2021.05.28.17.52.53; Fri, 28 May 2021 17:53:25 -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=fail header.i=@panix.com header.s=panix header.b=bzKaMsj6; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229635AbhE2AxX (ORCPT + 99 others); Fri, 28 May 2021 20:53:23 -0400 Received: from l2mail1.panix.com ([166.84.1.75]:50771 "EHLO l2mail1.panix.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229597AbhE2AxX (ORCPT ); Fri, 28 May 2021 20:53:23 -0400 X-Greylist: delayed 917 seconds by postgrey-1.27 at vger.kernel.org; Fri, 28 May 2021 20:53:23 EDT Received: from mailbackend.panix.com (mailbackend.panix.com [166.84.1.89]) by l2mail1.panix.com (Postfix) with ESMTPS id 4FsN0G4hLLzDRZ for ; Fri, 28 May 2021 20:36:30 -0400 (EDT) Received: from xps-7390 (ip70-164-222-119.oc.oc.cox.net [70.164.222.119]) by mailbackend.panix.com (Postfix) with ESMTPSA id 4FsN0F186HzQ5C; Fri, 28 May 2021 20:36:29 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=panix.com; s=panix; t=1622248589; bh=JxdsPoOCRZs6f++m4Uh0jQn1jfP+LVG6TVWbtOFL3oM=; h=Date:From:Reply-To:To:cc:Subject; b=bzKaMsj6FzV2cowVEABgOuxggSLrvDwh5QDrGq2TjZgLLCXl2bqDpQfgo92WJmTDC rvDJFWDSus6S3hFUu8CpoRagcIB6+RH6SbjDlYXiKvNi5zpLKEnwQux14ZVgCthXj1 RMdAzgLX8vE4mNqzDECLpcEGYHVKkkQoqV84baUU= Date: Fri, 28 May 2021 17:36:28 -0700 (PDT) From: "Kenneth R. Crudup" Reply-To: "Kenneth R. Crudup" To: luiz.von.dentz@intel.com cc: tedd.an@intel.com, marcel@holtmann.org, linux-bluetooth@vger.kernel.org Subject: Commit 9b16bfbf41 ("Bluetooth: btintel: Move operational checks after version check") causing BT FW loading problems Message-ID: <42d9c52a-bcc9-13e6-9b1d-d9a94ff2889f@panix.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Precedence: bulk List-ID: X-Mailing-List: linux-bluetooth@vger.kernel.org My BT device is (apparently a Jefferson Peak device): >> Bus 003 Device 003: ID 8087:0026 Intel Corp. With this commit in place, loading the BT firmware after a cold start fails attempting to load the wrong(?) firmware: ---- Bluetooth: hci0: Firmware revision 0.0 build 118 week 15 2021 bluetooth hci0: Direct firmware load for intel/ibt-19-16-0.sfi failed with error -2 Bluetooth: hci0: Failed to load Intel firmware file intel/ibt-19-16-0.sfi (-2) ---- ... and a "git log" in the linux-firmware repo shows this file "ibt-19-16-0.sfi" never existed. Before this commit it was trying to load: ---- Bluetooth: hci0: Bootloader revision 0.4 build 0 week 11 2017 Bluetooth: hci0: Device revision is 2 Bluetooth: hci0: Secure boot is enabled Bluetooth: hci0: OTP lock is enabled Bluetooth: hci0: API lock is enabled Bluetooth: hci0: Debug lock is disabled Bluetooth: hci0: Minimum firmware build 1 week 10 2014 Bluetooth: hci0: Found device firmware: intel/ibt-19-32-4.sfi Bluetooth: hci0: Waiting for firmware download to complete Bluetooth: hci0: Firmware loaded in 1642369 usecs Bluetooth: hci0: Waiting for device to boot Bluetooth: hci0: Device booted in 17881 usecs Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-19-32-4.ddc Bluetooth: hci0: Applying Intel DDC parameters completed Bluetooth: hci0: Firmware revision 0.0 build 121 week 7 2021 Bluetooth: hci0: MSFT filter_enable is already on ---- Let me know if anyone needs more info. -Kenny -- Kenneth R. Crudup Sr. SW Engineer, Scott County Consulting, Orange County CA