linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kai-Heng Feng <kai.heng.feng@canonical.com>
To: marcel@holtmann.org, johan.hedberg@gmail.com
Cc: drake@endlessm.com, linux-bluetooth@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Kai-Heng Feng <kai.heng.feng@canonical.com>
Subject: [PATCH 3/3] Bluetooth: btrtl: Skip initialization if firmware is already loaded
Date: Thu, 24 Jan 2019 23:23:10 +0800	[thread overview]
Message-ID: <20190124152310.29717-3-kai.heng.feng@canonical.com> (raw)
In-Reply-To: <20190124152310.29717-1-kai.heng.feng@canonical.com>

Realtek bluetooth may not work after reboot:
[   12.446130] Bluetooth: hci0: RTL: rtl: unknown IC info, lmp subver a99e, hci rev 826c, hci ver 0008

The power is not cut during system reboot, so the firmware is kept in
Bluetooth controller.

Realtek bluetooth doesn't have the ability to check firmware loading
status. but the version queried by HCI_OP_READ_LOCAL_VERSION will be
different if firmware is already loaded. Realtek's own fork, rtk_btusb
also use this method to detect the loading status.

So let's assume the firmware is already loaded when we can't find
matching IC info.

Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=201921
Signed-off-by: Kai-Heng Feng <kai.heng.feng@canonical.com>
---
 drivers/bluetooth/btrtl.c | 10 ++++++----
 1 file changed, 6 insertions(+), 4 deletions(-)

diff --git a/drivers/bluetooth/btrtl.c b/drivers/bluetooth/btrtl.c
index c36f500d8313..e2f89d57dd14 100644
--- a/drivers/bluetooth/btrtl.c
+++ b/drivers/bluetooth/btrtl.c
@@ -546,9 +546,10 @@ int btrtl_initialize(struct hci_dev *hdev,
 					    hdev->bus);
 
 	if (!btrtl_dev->ic_info) {
-		rtl_dev_err(hdev, "rtl: unknown IC info, lmp subver %04x, hci rev %04x, hci ver %04x",
-			    lmp_subver, hci_rev, hci_ver);
-		return -EINVAL;
+		rtl_dev_info(hdev, "rtl: unknown IC info, lmp subver %04x, hci rev %04x, hci ver %04x",
+			     lmp_subver, hci_rev, hci_ver);
+		rtl_dev_info(hdev, "rtl: firmware may be already loaded, or it's an unsupported IC.");
+		return 0;
 	}
 
 	if (btrtl_dev->ic_info->has_rom_version) {
@@ -621,7 +622,8 @@ int btrtl_setup_realtek(struct hci_dev *hdev)
 	if (ret)
 		return ret;
 
-	ret = btrtl_download_firmware(hdev, &btrtl_dev);
+	if (btrtl_dev.ic_info)
+		ret = btrtl_download_firmware(hdev, &btrtl_dev);
 
 	return ret;
 }
-- 
2.17.1


  parent reply	other threads:[~2019-01-24 15:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-24 15:23 [PATCH 1/3] Bluetooth: btrtl: Let rtl_load_file() always return error code Kai-Heng Feng
2019-01-24 15:23 ` [PATCH 2/3] Bluetooth: btrtl: Let btrtl_initialize() " Kai-Heng Feng
2019-01-24 15:23 ` Kai-Heng Feng [this message]
2019-01-25  0:55   ` [PATCH 3/3] Bluetooth: btrtl: Skip initialization if firmware is already loaded Daniel Drake
2019-01-25 17:46     ` Kai-Heng Feng

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=20190124152310.29717-3-kai.heng.feng@canonical.com \
    --to=kai.heng.feng@canonical.com \
    --cc=drake@endlessm.com \
    --cc=johan.hedberg@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcel@holtmann.org \
    /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).