From: Amit K Bag <amit.k.bag@intel.com>
To: linux-firmware@kernel.org
Cc: linux-bluetooth@vger.kernel.org, ravishankar.srivatsa@intel.com,
chethan.tumkur.narayan@intel.com,
Sukumar Ghorai <sukumar.ghorai@intel.com>,
Amit K Bag <amit.k.bag@intel.com>
Subject: [PATCH v3] Bluetooth: print fw build version in power-on boot
Date: Fri, 13 Mar 2020 10:46:33 +0530 [thread overview]
Message-ID: <20200313051633.30724-1-amit.k.bag@intel.com> (raw)
From: Sukumar Ghorai <sukumar.ghorai@intel.com>
To determine the build version of Bluetooth firmware to ensure reported
issue related to a particular release. This is very helpful for every fw
downloaded to BT controller and issue reported from field test.
Signed-off-by: Amit K Bag <amit.k.bag@intel.com>
Signed-off-by: Sukumar Ghorai <sukumar.ghorai@intel.com>
---
drivers/bluetooth/btusb.c | 9 ++++++++-
1 file changed, 8 insertions(+), 1 deletion(-)
diff --git a/drivers/bluetooth/btusb.c b/drivers/bluetooth/btusb.c
index f5924f3e8b8d..c1e8b8d4931e 100644
--- a/drivers/bluetooth/btusb.c
+++ b/drivers/bluetooth/btusb.c
@@ -1930,7 +1930,14 @@ static int btusb_setup_intel(struct hci_dev *hdev)
if (err)
return err;
- bt_dev_info(hdev, "Intel firmware patch completed and activated");
+ /* Need build number for downloaded fw patches in
+ * every power-on boot
+ */
+ err = btintel_read_version(hdev, &ver);
+ if (err)
+ return err;
+ bt_dev_info(hdev, "Intel BT fw patch 0x%02x completed & activated",
+ hdev->name, ver.fw_patch_num);
goto complete;
--
2.17.1
next reply other threads:[~2020-03-13 5:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-13 5:16 Amit K Bag [this message]
2020-03-13 5:16 ` [PATCH v3] Bluetooth: print fw build version in power-on boot Amit K Bag
2020-03-13 5:19 Amit K Bag
2020-03-13 5:19 ` Amit K Bag
2020-03-13 18:50 ` Marcel Holtmann
2020-03-13 18:50 ` Marcel Holtmann
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=20200313051633.30724-1-amit.k.bag@intel.com \
--to=amit.k.bag@intel.com \
--cc=chethan.tumkur.narayan@intel.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-firmware@kernel.org \
--cc=ravishankar.srivatsa@intel.com \
--cc=sukumar.ghorai@intel.com \
/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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).