public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tim Gardner <tim.gardner@canonical.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: marcel@holtmann.org, linux-bluetooth@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Mario Limonciello <mario_limonciello@dell.com>
Subject: Re: Dell Wireless 365 requires reset quirk
Date: Thu, 13 Nov 2008 17:59:50 -0700	[thread overview]
Message-ID: <491CCD86.7050904@canonical.com> (raw)
In-Reply-To: <20081111145706.9bfb4627.akpm@linux-foundation.org>

[-- Attachment #1: Type: text/plain, Size: 1779 bytes --]

Andrew Morton wrote:
> On Tue,  4 Nov 2008 09:24:48 -0700 (MST)
> timg@tpi.com (Tim Gardner) wrote:
> 
>> >From 931ccb629d739aa563347a4e866bc26107e6b545 Mon Sep 17 00:00:00 2001
>> From: Tim Gardner <tim.gardner@canonical.com>
>> Date: Tue, 4 Nov 2008 09:18:06 -0700
>> Subject: [PATCH] Dell Wireless 365 needs BTUSB_RESET quirk.
>>  OriginalAuthor: Mario Limonciello <mario_limonciello@dell.com>
>>
>> Signed-off-by: Tim Gardner <tim.gardner@canonical.com>
>> Cc: stable@kernel.org
>> ---
>>  drivers/bluetooth/btusb.c |    3 +++
>>  1 files changed, 3 insertions(+), 0 deletions(-)
>>
>> diff --git a/drivers/bluetooth/btusb.c b/drivers/bluetooth/btusb.c
>> index af472e0..051b758 100644
>> --- a/drivers/bluetooth/btusb.c
>> +++ b/drivers/bluetooth/btusb.c
>> @@ -125,6 +125,9 @@ static struct usb_device_id blacklist_table[] = {
>>  	/* Dell laptop with Broadcom chip */
>>  	{ USB_DEVICE(0x413c, 0x8126), .driver_info = BTUSB_RESET | BTUSB_WRONG_SCO_MTU },
>>  
>> +	/* Dell Wireless 365 */
>> +	{ USB_DEVICE(0x413c, 0x8160), .driver_info = BTUSB_RESET },
>> +
>>  	/* Dell Wireless 370 */
>>  	{ USB_DEVICE(0x413c, 0x8156), .driver_info = BTUSB_RESET | BTUSB_WRONG_SCO_MTU },
>>  
> 
> I shall assume that this patch was authored by Mario.  This should have
> been communicated by adding his From: line right at the top of the
> changelog.  Mario's signed-off-by: is absent, but that is tolerable
> because we have yours.
> 
> The (absent) changelog fails to explain what effect this patch has. 
> _why_ does this driver need this quirk?
> 
> As it stands, there is insufficient information here for making
> 2.6.28-vs-2.6.29 decisions, let alone 2.6.27.x, 2.6.26.x, etc.
> 

Is this better (aside from being an attachment) ?

rtg
-- 
Tim Gardner tim.gardner@canonical.com

[-- Attachment #2: 0001--bluetooth-Dell-Wireless-365-needs-BTUSB_RESET-qui.patch --]
[-- Type: text/x-patch, Size: 1184 bytes --]

>From 8da2a85810aa0fb5abbc93d15482846af5d60669 Mon Sep 17 00:00:00 2001
From: Mario Limonciello <mario_limonciello@dell.com>
Date: Tue, 4 Nov 2008 09:18:06 -0700
Subject: [PATCH] bluetooth: Dell Wireless 365 needs BTUSB_RESET quirk.

This patch causes the BT365 to be reset when the driver is loaded.
Without it, you won't be able to connect to other devices or scan for
devices.

Signed-off-by: Mario Limonciello <mario_limonciello@dell.com>
Signed-off-by: Tim Gardner <tim.gardner@canonical.com>
Cc: stable@kernel.org
---
 drivers/bluetooth/btusb.c |    3 +++
 1 files changed, 3 insertions(+), 0 deletions(-)

diff --git a/drivers/bluetooth/btusb.c b/drivers/bluetooth/btusb.c
index af472e0..051b758 100644
--- a/drivers/bluetooth/btusb.c
+++ b/drivers/bluetooth/btusb.c
@@ -125,6 +125,9 @@ static struct usb_device_id blacklist_table[] = {
 	/* Dell laptop with Broadcom chip */
 	{ USB_DEVICE(0x413c, 0x8126), .driver_info = BTUSB_RESET | BTUSB_WRONG_SCO_MTU },
 
+	/* Dell Wireless 365 */
+	{ USB_DEVICE(0x413c, 0x8160), .driver_info = BTUSB_RESET },
+
 	/* Dell Wireless 370 */
 	{ USB_DEVICE(0x413c, 0x8156), .driver_info = BTUSB_RESET | BTUSB_WRONG_SCO_MTU },
 
-- 
1.5.6.3


  parent reply	other threads:[~2008-11-14  1:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-04 16:24 Dell Wireless 365 requires reset quirk Tim Gardner
2008-11-11 22:57 ` Andrew Morton
2008-11-11 23:41   ` Mario Limonciello
2008-11-14  0:59   ` Tim Gardner [this message]
2008-11-30 10:33     ` 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=491CCD86.7050904@canonical.com \
    --to=tim.gardner@canonical.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcel@holtmann.org \
    --cc=mario_limonciello@dell.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