All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bala Shanmugam <sbalashanmugam@atheros.com>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: Shanmugamkamatchi Balashanmugam
	<Shanmugamkamatchi.Balashanmugam@Atheros.com>,
	"linux-bluetooth@vger.kernel.org"
	<linux-bluetooth@vger.kernel.org>
Subject: Re: [PATCH] Bluetooth: Add new PID for Atheros 3011
Date: Fri, 26 Nov 2010 17:40:12 +0530	[thread overview]
Message-ID: <4CEFA3A4.7030806@atheros.com> (raw)
In-Reply-To: <1290770560.4795.12.camel@aeonflux>

Marcel Holtmann wrote:
> Hi Bala,
>
>   
>> Atheros 3011 has small sflash firmware and needs to be
>> blacklisted in transport driver to load actual firmware
>> in DFU driver.
>>     
>
> please add an empty line here. The signed-off line should always be
> separated from the commit message. The git am takes it literal as it is
> and does not modify it.
>
>   
>> Signed-off-by: Bala Shanmugam <sbalashanmugam@atheros.com>
>> ---
>>  drivers/bluetooth/ath3k.c |    2 ++
>>  drivers/bluetooth/btusb.c |    3 +++
>>  2 files changed, 5 insertions(+), 0 deletions(-)
>>
>> diff --git a/drivers/bluetooth/ath3k.c b/drivers/bluetooth/ath3k.c
>> index 128cae4..c70fb0b 100644
>> --- a/drivers/bluetooth/ath3k.c
>> +++ b/drivers/bluetooth/ath3k.c
>> @@ -35,6 +35,8 @@
>>  static struct usb_device_id ath3k_table[] = {
>>  	/* Atheros AR3011 */
>>  	{ USB_DEVICE(0x0CF3, 0x3000) },
>>     
>
> For the sake of readability add another empty line here as well.
>
>   
>> +	/* Atheros AR3011 with sflash firmware*/
>> +	{ USB_DEVICE(0x0CF3, 0x3002) },
>>     
>
> And for consistency, add another empty line here as well.
>
>   
>>  	{ }	/* Terminating entry */
>>  };
>>  
>> diff --git a/drivers/bluetooth/btusb.c b/drivers/bluetooth/btusb.c
>> index ab3894f..ca3fdc1 100644
>> --- a/drivers/bluetooth/btusb.c
>> +++ b/drivers/bluetooth/btusb.c
>> @@ -99,6 +99,9 @@ static struct usb_device_id blacklist_table[] = {
>>  	/* Broadcom BCM2033 without firmware */
>>  	{ USB_DEVICE(0x0a5c, 0x2033), .driver_info = BTUSB_IGNORE },
>>  
>> +	/* Atheros 3011 with sflash firmware */
>> +	{ USB_DEVICE(0x0cf3, 0x3002), .driver_info = BTUSB_IGNORE },
>> +
>>  	/* Broadcom BCM2035 */
>>  	{ USB_DEVICE(0x0a5c, 0x2035), .driver_info = BTUSB_WRONG_SCO_MTU },
>>  	{ USB_DEVICE(0x0a5c, 0x200a), .driver_info = BTUSB_WRONG_SCO_MTU },
>>     
>
> If this finally solves the mess with the firmware loading, then I am
> fine with it. It looks clean and simple now.
>
> Acked-by: Marcel Holtmann <marcel@holtmann.org>
>
> Regards
>
> Marcel
>
>
>   
Yes Marcel it solves our problem.
Probably, later if our customers wants to use different VID/PID,
we might have to blacklist those.
I have sent the updated patch.

Thanks for your comments.

Regards,
Bala.

  reply	other threads:[~2010-11-26 12:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-26 10:13 [PATCH] Bluetooth: Add new PID for Atheros 3011 Bala Shanmugam
2010-11-26 11:22 ` Marcel Holtmann
2010-11-26 12:10   ` Bala Shanmugam [this message]
2010-11-26 15:40     ` Alexander Holler
2010-11-26 15:55       ` Alexander Holler
2010-11-29  6:09         ` Bala Shanmugam
2010-11-29 11:28           ` Alexander Holler
2010-11-30  5:59             ` Bala Shanmugam

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=4CEFA3A4.7030806@atheros.com \
    --to=sbalashanmugam@atheros.com \
    --cc=Shanmugamkamatchi.Balashanmugam@Atheros.com \
    --cc=linux-bluetooth@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.