linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: "Gustavo F. Padovan" <gustavo@padovan.org>,
	Johan Hedberg <johan.hedberg@gmail.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-bluetooth@vger.kernel.org,
	Hon Weng Chong <honwchong@gmail.com>
Subject: Re: [PATCH] bluetooth: btusb: Add device ID for RTL8822BE
Date: Sat, 11 Nov 2017 19:51:36 +0100	[thread overview]
Message-ID: <82ACB0CF-DD2F-4A44-A2F0-75D1C1B3DA9C@holtmann.org> (raw)
In-Reply-To: <20171111174326.9243-1-Larry.Finger@lwfinger.net>

Hi Larry,

> The Asus Z370-I contains a Realtek RTL8822BE device with an associated
> BT chip using a USB ID of 0b05:185c. This device is added to the driver.
> 
> Signed-off-by: Hon Weng Chong <honwchong@gmail.com>
> Signed-off-by: Larry Finger <Larry.Finger@lwfinger.net>
> ---
> drivers/bluetooth/btusb.c | 3 +++
> 1 file changed, 3 insertions(+)
> 
> diff --git a/drivers/bluetooth/btusb.c b/drivers/bluetooth/btusb.c
> index 7a5c06aaa181..c265ef63cab7 100644
> --- a/drivers/bluetooth/btusb.c
> +++ b/drivers/bluetooth/btusb.c
> @@ -373,6 +373,9 @@ static const struct usb_device_id blacklist_table[] = {
> 	{ USB_DEVICE(0x13d3, 0x3461), .driver_info = BTUSB_REALTEK },
> 	{ USB_DEVICE(0x13d3, 0x3462), .driver_info = BTUSB_REALTEK },
> 
> +	/* Additional Realtek 8822BE Bluetooth devices */
> +	{ USB_DEVICE(0x0b05, 0x1185c), .driver_info = BTUSB_REALTEK },
> +

I prefer to have /sys/kernel/debug/usb/devices for the device included in the commit message.

Regards

Marcel

  reply	other threads:[~2017-11-11 18:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-11 17:43 [PATCH] bluetooth: btusb: Add device ID for RTL8822BE Larry Finger
2017-11-11 18:51 ` Marcel Holtmann [this message]
2017-11-11 19:10   ` Larry Finger
2017-11-14 23:40     ` Hon Weng Chong
2017-11-12 13:45   ` Bjørn Mork
2017-11-14  9:22 ` kbuild test robot
2017-11-14  9:30 ` kbuild test robot

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=82ACB0CF-DD2F-4A44-A2F0-75D1C1B3DA9C@holtmann.org \
    --to=marcel@holtmann.org \
    --cc=Larry.Finger@lwfinger.net \
    --cc=gustavo@padovan.org \
    --cc=honwchong@gmail.com \
    --cc=johan.hedberg@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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).