From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from coyote.holtmann.net ([212.227.132.17]:47026 "EHLO mail.holtmann.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750907AbdGHMUS (ORCPT ); Sat, 8 Jul 2017 08:20:18 -0400 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: Request to add bluetooth module identifier to net/rfkill/rfkill-gpio.c From: Marcel Holtmann In-Reply-To: Date: Sat, 8 Jul 2017 14:20:15 +0200 Cc: Johannes Berg , "David S. Miller" , linux-wireless , Network Development , linux-kernel@vger.kernel.org Message-Id: <985A2192-C2F2-4361-BE23-9E9A5F53DAFA@holtmann.org> (sfid-20170708_142035_090248_5BFB5075) References: To: Sundar Nagarajan Sender: linux-wireless-owner@vger.kernel.org List-ID: Hi Sundar, > I have a Cherry Trail laptop with an Atom X5-Z8300. It has a bluetooth > chip that needs the r8723bs (coexisting RTL 8723BS wifi and > bluetooth). > > I am using linux-next (20150817) with the r8723bs staging driver and > the firmware and utility from https://github.com/lwfinger/rtl8723bs_bt > by Larry finger. > > With linux-next the bluetooth works SOMETIMES, but on reboot, it does > not work any more (no bluetooth interfaces are detected and hciconfig > shows nothing). > > I am a kernel novice, but I saw that another kernel that I had tried > had the following line added in struct acpi_device_id > rfkill_acpi_match: > > { "OBDA8723",RFKILL_TYPE_BLUETOOTH } > > With the attached patch applied (one line added), my bluetooth works every time. > > Does this belong in rfkill-gpio.c, or should I contact someone else? it does not belong in rfkill-gpio.c since this controls the power of the Bluetooth device. This belongs in the Bluetooth driver. We already moved all the Intel and Broadcom ones into hci_intel.c and respectively hci_bcm.c. So have the staging driver deal with the power GPIO. Regards Marcel