* [PATCH] Add a new PID/VID 0cf3/e005 for AR3012.
@ 2013-08-30 9:09 Peng Chen
2014-03-05 18:59 ` Johan Hedberg
2014-06-20 10:01 ` Alexander Holler
0 siblings, 2 replies; 13+ messages in thread
From: Peng Chen @ 2013-08-30 9:09 UTC (permalink / raw)
To: gustavo, linux-bluetooth, marcel; +Cc: kumo, taowang, Peng Chen
usb devices info:
T: Bus=06 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 13 Spd=12 MxCh= 0
D: Ver= 1.10 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs= 1
P: Vendor=0cf3 ProdID=e005 Rev= 0.02
C:* #Ifs= 2 Cfg#= 1 Atr=e0 MxPwr=100mA
I:* If#= 0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=(none)
E: Ad=81(I) Atr=03(Int.) MxPS= 16 Ivl=1ms
E: Ad=82(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms
E: Ad=02(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms
I:* If#= 1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=(none)
E: Ad=83(I) Atr=01(Isoc) MxPS= 0 Ivl=1ms
E: Ad=03(O) Atr=01(Isoc) MxPS= 0 Ivl=1ms
I: If#= 1 Alt= 1 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=(none)
E: Ad=83(I) Atr=01(Isoc) MxPS= 9 Ivl=1ms
E: Ad=03(O) Atr=01(Isoc) MxPS= 9 Ivl=1ms
I: If#= 1 Alt= 2 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=(none)
E: Ad=83(I) Atr=01(Isoc) MxPS= 17 Ivl=1ms
E: Ad=03(O) Atr=01(Isoc) MxPS= 17 Ivl=1ms
I: If#= 1 Alt= 3 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=(none)
E: Ad=83(I) Atr=01(Isoc) MxPS= 25 Ivl=1ms
E: Ad=03(O) Atr=01(Isoc) MxPS= 25 Ivl=1ms
I: If#= 1 Alt= 4 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=(none)
E: Ad=83(I) Atr=01(Isoc) MxPS= 33 Ivl=1ms
E: Ad=03(O) Atr=01(Isoc) MxPS= 33 Ivl=1ms
I: If#= 1 Alt= 5 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=(none)
E: Ad=83(I) Atr=01(Isoc) MxPS= 49 Ivl=1ms
E: Ad=03(O) Atr=01(Isoc) MxPS= 49 Ivl=1ms
Signed-off-by: Peng Chen <pengchen@qca.qualcomm.com>
---
drivers/bluetooth/ath3k.c | 2 ++
drivers/bluetooth/btusb.c | 1 +
2 files changed, 3 insertions(+)
diff --git a/drivers/bluetooth/ath3k.c b/drivers/bluetooth/ath3k.c
index 11f467c..10e9a64 100644
--- a/drivers/bluetooth/ath3k.c
+++ b/drivers/bluetooth/ath3k.c
@@ -85,6 +85,7 @@ static struct usb_device_id ath3k_table[] = {
{ USB_DEVICE(0x04CA, 0x3008) },
{ USB_DEVICE(0x13d3, 0x3362) },
{ USB_DEVICE(0x0CF3, 0xE004) },
+ { USB_DEVICE(0x0CF3, 0xE005) },
{ USB_DEVICE(0x0930, 0x0219) },
{ USB_DEVICE(0x0489, 0xe057) },
{ USB_DEVICE(0x13d3, 0x3393) },
@@ -122,6 +123,7 @@ static struct usb_device_id ath3k_blist_tbl[] = {
{ USB_DEVICE(0x04ca, 0x3008), .driver_info = BTUSB_ATH3012 },
{ USB_DEVICE(0x13d3, 0x3362), .driver_info = BTUSB_ATH3012 },
{ USB_DEVICE(0x0cf3, 0xe004), .driver_info = BTUSB_ATH3012 },
+ { USB_DEVICE(0x0cf3, 0xe005), .driver_info = BTUSB_ATH3012 },
{ USB_DEVICE(0x0930, 0x0219), .driver_info = BTUSB_ATH3012 },
{ USB_DEVICE(0x0489, 0xe057), .driver_info = BTUSB_ATH3012 },
{ USB_DEVICE(0x13d3, 0x3393), .driver_info = BTUSB_ATH3012 },
diff --git a/drivers/bluetooth/btusb.c b/drivers/bluetooth/btusb.c
index de4cf4d..299df99 100644
--- a/drivers/bluetooth/btusb.c
+++ b/drivers/bluetooth/btusb.c
@@ -148,6 +148,7 @@ static struct usb_device_id blacklist_table[] = {
{ USB_DEVICE(0x04ca, 0x3008), .driver_info = BTUSB_ATH3012 },
{ USB_DEVICE(0x13d3, 0x3362), .driver_info = BTUSB_ATH3012 },
{ USB_DEVICE(0x0cf3, 0xe004), .driver_info = BTUSB_ATH3012 },
+ { USB_DEVICE(0x0cf3, 0xe005), .driver_info = BTUSB_ATH3012 },
{ USB_DEVICE(0x0930, 0x0219), .driver_info = BTUSB_ATH3012 },
{ USB_DEVICE(0x0489, 0xe057), .driver_info = BTUSB_ATH3012 },
{ USB_DEVICE(0x13d3, 0x3393), .driver_info = BTUSB_ATH3012 },
--
1.7.9.5
^ permalink raw reply related [flat|nested] 13+ messages in thread
* [PATCH] Add a new PID/VID 0cf3/e005 for AR3012.
@ 2013-08-30 9:41 Peng Chen
2013-09-01 16:50 ` Gustavo Padovan
0 siblings, 1 reply; 13+ messages in thread
From: Peng Chen @ 2013-08-30 9:41 UTC (permalink / raw)
To: gustavo, linux-bluetooth, marcel; +Cc: kumo, taowang, Peng Chen
usb device info:
T: Bus=06 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 15 Spd=12 MxCh= 0
D: Ver= 1.10 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs= 1
P: Vendor=0cf3 ProdID=e005 Rev= 0.02
C:* #Ifs= 2 Cfg#= 1 Atr=e0 MxPwr=100mA
I:* If#= 0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
E: Ad=81(I) Atr=03(Int.) MxPS= 16 Ivl=1ms
E: Ad=82(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms
E: Ad=02(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms
I:* If#= 1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
E: Ad=83(I) Atr=01(Isoc) MxPS= 0 Ivl=1ms
E: Ad=03(O) Atr=01(Isoc) MxPS= 0 Ivl=1ms
I: If#= 1 Alt= 1 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
E: Ad=83(I) Atr=01(Isoc) MxPS= 9 Ivl=1ms
E: Ad=03(O) Atr=01(Isoc) MxPS= 9 Ivl=1ms
I: If#= 1 Alt= 2 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
E: Ad=83(I) Atr=01(Isoc) MxPS= 17 Ivl=1ms
E: Ad=03(O) Atr=01(Isoc) MxPS= 17 Ivl=1ms
I: If#= 1 Alt= 3 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
E: Ad=83(I) Atr=01(Isoc) MxPS= 25 Ivl=1ms
E: Ad=03(O) Atr=01(Isoc) MxPS= 25 Ivl=1ms
I: If#= 1 Alt= 4 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
E: Ad=83(I) Atr=01(Isoc) MxPS= 33 Ivl=1ms
E: Ad=03(O) Atr=01(Isoc) MxPS= 33 Ivl=1ms
I: If#= 1 Alt= 5 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
E: Ad=83(I) Atr=01(Isoc) MxPS= 49 Ivl=1ms
E: Ad=03(O) Atr=01(Isoc) MxPS= 49 Ivl=1ms
Signed-off-by: Peng Chen <pengchen@qca.qualcomm.com>
---
drivers/bluetooth/ath3k.c | 2 ++
drivers/bluetooth/btusb.c | 1 +
2 files changed, 3 insertions(+)
diff --git a/drivers/bluetooth/ath3k.c b/drivers/bluetooth/ath3k.c
index 11f467c..10e9a64 100644
--- a/drivers/bluetooth/ath3k.c
+++ b/drivers/bluetooth/ath3k.c
@@ -85,6 +85,7 @@ static struct usb_device_id ath3k_table[] = {
{ USB_DEVICE(0x04CA, 0x3008) },
{ USB_DEVICE(0x13d3, 0x3362) },
{ USB_DEVICE(0x0CF3, 0xE004) },
+ { USB_DEVICE(0x0CF3, 0xE005) },
{ USB_DEVICE(0x0930, 0x0219) },
{ USB_DEVICE(0x0489, 0xe057) },
{ USB_DEVICE(0x13d3, 0x3393) },
@@ -122,6 +123,7 @@ static struct usb_device_id ath3k_blist_tbl[] = {
{ USB_DEVICE(0x04ca, 0x3008), .driver_info = BTUSB_ATH3012 },
{ USB_DEVICE(0x13d3, 0x3362), .driver_info = BTUSB_ATH3012 },
{ USB_DEVICE(0x0cf3, 0xe004), .driver_info = BTUSB_ATH3012 },
+ { USB_DEVICE(0x0cf3, 0xe005), .driver_info = BTUSB_ATH3012 },
{ USB_DEVICE(0x0930, 0x0219), .driver_info = BTUSB_ATH3012 },
{ USB_DEVICE(0x0489, 0xe057), .driver_info = BTUSB_ATH3012 },
{ USB_DEVICE(0x13d3, 0x3393), .driver_info = BTUSB_ATH3012 },
diff --git a/drivers/bluetooth/btusb.c b/drivers/bluetooth/btusb.c
index de4cf4d..299df99 100644
--- a/drivers/bluetooth/btusb.c
+++ b/drivers/bluetooth/btusb.c
@@ -148,6 +148,7 @@ static struct usb_device_id blacklist_table[] = {
{ USB_DEVICE(0x04ca, 0x3008), .driver_info = BTUSB_ATH3012 },
{ USB_DEVICE(0x13d3, 0x3362), .driver_info = BTUSB_ATH3012 },
{ USB_DEVICE(0x0cf3, 0xe004), .driver_info = BTUSB_ATH3012 },
+ { USB_DEVICE(0x0cf3, 0xe005), .driver_info = BTUSB_ATH3012 },
{ USB_DEVICE(0x0930, 0x0219), .driver_info = BTUSB_ATH3012 },
{ USB_DEVICE(0x0489, 0xe057), .driver_info = BTUSB_ATH3012 },
{ USB_DEVICE(0x13d3, 0x3393), .driver_info = BTUSB_ATH3012 },
--
1.7.9.5
^ permalink raw reply related [flat|nested] 13+ messages in thread
* Re: [PATCH] Add a new PID/VID 0cf3/e005 for AR3012.
2013-08-30 9:41 [PATCH] Add a new PID/VID 0cf3/e005 for AR3012 Peng Chen
@ 2013-09-01 16:50 ` Gustavo Padovan
0 siblings, 0 replies; 13+ messages in thread
From: Gustavo Padovan @ 2013-09-01 16:50 UTC (permalink / raw)
To: Peng Chen; +Cc: linux-bluetooth, marcel, kumo, taowang
Hi Peng,
2013-08-30 Peng Chen <pengchen@qti.qualcomm.com>:
> usb device info:
>
> T: Bus=06 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 15 Spd=12 MxCh= 0
> D: Ver= 1.10 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs= 1
> P: Vendor=0cf3 ProdID=e005 Rev= 0.02
> C:* #Ifs= 2 Cfg#= 1 Atr=e0 MxPwr=100mA
> I:* If#= 0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
> E: Ad=81(I) Atr=03(Int.) MxPS= 16 Ivl=1ms
> E: Ad=82(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms
> E: Ad=02(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms
> I:* If#= 1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
> E: Ad=83(I) Atr=01(Isoc) MxPS= 0 Ivl=1ms
> E: Ad=03(O) Atr=01(Isoc) MxPS= 0 Ivl=1ms
> I: If#= 1 Alt= 1 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
> E: Ad=83(I) Atr=01(Isoc) MxPS= 9 Ivl=1ms
> E: Ad=03(O) Atr=01(Isoc) MxPS= 9 Ivl=1ms
> I: If#= 1 Alt= 2 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
> E: Ad=83(I) Atr=01(Isoc) MxPS= 17 Ivl=1ms
> E: Ad=03(O) Atr=01(Isoc) MxPS= 17 Ivl=1ms
> I: If#= 1 Alt= 3 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
> E: Ad=83(I) Atr=01(Isoc) MxPS= 25 Ivl=1ms
> E: Ad=03(O) Atr=01(Isoc) MxPS= 25 Ivl=1ms
> I: If#= 1 Alt= 4 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
> E: Ad=83(I) Atr=01(Isoc) MxPS= 33 Ivl=1ms
> E: Ad=03(O) Atr=01(Isoc) MxPS= 33 Ivl=1ms
> I: If#= 1 Alt= 5 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
> E: Ad=83(I) Atr=01(Isoc) MxPS= 49 Ivl=1ms
> E: Ad=03(O) Atr=01(Isoc) MxPS= 49 Ivl=1ms
>
> Signed-off-by: Peng Chen <pengchen@qca.qualcomm.com>
> ---
> drivers/bluetooth/ath3k.c | 2 ++
> drivers/bluetooth/btusb.c | 1 +
> 2 files changed, 3 insertions(+)
Patch has been applied to bluetooth.git. Thanks.
Gustavo
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: [PATCH] Add a new PID/VID 0cf3/e005 for AR3012.
2013-08-30 9:09 Peng Chen
@ 2014-03-05 18:59 ` Johan Hedberg
2014-06-20 10:01 ` Alexander Holler
1 sibling, 0 replies; 13+ messages in thread
From: Johan Hedberg @ 2014-03-05 18:59 UTC (permalink / raw)
To: Peng Chen; +Cc: gustavo, linux-bluetooth, marcel, kumo, taowang
Hi,
On Fri, Aug 30, 2013, Peng Chen wrote:
> usb devices info:
>
> T: Bus=06 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 13 Spd=12 MxCh= 0
> D: Ver= 1.10 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs= 1
> P: Vendor=0cf3 ProdID=e005 Rev= 0.02
> C:* #Ifs= 2 Cfg#= 1 Atr=e0 MxPwr=100mA
> I:* If#= 0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=(none)
> E: Ad=81(I) Atr=03(Int.) MxPS= 16 Ivl=1ms
> E: Ad=82(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms
> E: Ad=02(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms
> I:* If#= 1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=(none)
> E: Ad=83(I) Atr=01(Isoc) MxPS= 0 Ivl=1ms
> E: Ad=03(O) Atr=01(Isoc) MxPS= 0 Ivl=1ms
> I: If#= 1 Alt= 1 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=(none)
> E: Ad=83(I) Atr=01(Isoc) MxPS= 9 Ivl=1ms
> E: Ad=03(O) Atr=01(Isoc) MxPS= 9 Ivl=1ms
> I: If#= 1 Alt= 2 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=(none)
> E: Ad=83(I) Atr=01(Isoc) MxPS= 17 Ivl=1ms
> E: Ad=03(O) Atr=01(Isoc) MxPS= 17 Ivl=1ms
> I: If#= 1 Alt= 3 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=(none)
> E: Ad=83(I) Atr=01(Isoc) MxPS= 25 Ivl=1ms
> E: Ad=03(O) Atr=01(Isoc) MxPS= 25 Ivl=1ms
> I: If#= 1 Alt= 4 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=(none)
> E: Ad=83(I) Atr=01(Isoc) MxPS= 33 Ivl=1ms
> E: Ad=03(O) Atr=01(Isoc) MxPS= 33 Ivl=1ms
> I: If#= 1 Alt= 5 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=(none)
> E: Ad=83(I) Atr=01(Isoc) MxPS= 49 Ivl=1ms
> E: Ad=03(O) Atr=01(Isoc) MxPS= 49 Ivl=1ms
>
> Signed-off-by: Peng Chen <pengchen@qca.qualcomm.com>
> ---
> drivers/bluetooth/ath3k.c | 2 ++
> drivers/bluetooth/btusb.c | 1 +
> 2 files changed, 3 insertions(+)
Applied to bluetooth-next. Thanks.
Johan
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: [PATCH] Add a new PID/VID 0cf3/e005 for AR3012.
2013-08-30 9:09 Peng Chen
2014-03-05 18:59 ` Johan Hedberg
@ 2014-06-20 10:01 ` Alexander Holler
2014-06-20 10:50 ` Marcel Holtmann
1 sibling, 1 reply; 13+ messages in thread
From: Alexander Holler @ 2014-06-20 10:01 UTC (permalink / raw)
To: Peng Chen, gustavo, linux-bluetooth, marcel; +Cc: kumo, taowang
Am 30.08.2013 11:09, schrieb Peng Chen:
> ---
> drivers/bluetooth/ath3k.c | 2 ++
> drivers/bluetooth/btusb.c | 1 +
> 2 files changed, 3 insertions(+)
>
> diff --git a/drivers/bluetooth/ath3k.c b/drivers/bluetooth/ath3k.c
> index 11f467c..10e9a64 100644
> --- a/drivers/bluetooth/ath3k.c
> +++ b/drivers/bluetooth/ath3k.c
> @@ -85,6 +85,7 @@ static struct usb_device_id ath3k_table[] = {
> { USB_DEVICE(0x04CA, 0x3008) },
> { USB_DEVICE(0x13d3, 0x3362) },
> { USB_DEVICE(0x0CF3, 0xE004) },
> + { USB_DEVICE(0x0CF3, 0xE005) },
> { USB_DEVICE(0x0930, 0x0219) },
> { USB_DEVICE(0x0489, 0xe057) },
> { USB_DEVICE(0x13d3, 0x3393) },
> @@ -122,6 +123,7 @@ static struct usb_device_id ath3k_blist_tbl[] = {
> { USB_DEVICE(0x04ca, 0x3008), .driver_info = BTUSB_ATH3012 },
> { USB_DEVICE(0x13d3, 0x3362), .driver_info = BTUSB_ATH3012 },
> { USB_DEVICE(0x0cf3, 0xe004), .driver_info = BTUSB_ATH3012 },
> + { USB_DEVICE(0x0cf3, 0xe005), .driver_info = BTUSB_ATH3012 },
> { USB_DEVICE(0x0930, 0x0219), .driver_info = BTUSB_ATH3012 },
> { USB_DEVICE(0x0489, 0xe057), .driver_info = BTUSB_ATH3012 },
> { USB_DEVICE(0x13d3, 0x3393), .driver_info = BTUSB_ATH3012 },
> diff --git a/drivers/bluetooth/btusb.c b/drivers/bluetooth/btusb.c
> index de4cf4d..299df99 100644
> --- a/drivers/bluetooth/btusb.c
> +++ b/drivers/bluetooth/btusb.c
> @@ -148,6 +148,7 @@ static struct usb_device_id blacklist_table[] = {
> { USB_DEVICE(0x04ca, 0x3008), .driver_info = BTUSB_ATH3012 },
> { USB_DEVICE(0x13d3, 0x3362), .driver_info = BTUSB_ATH3012 },
> { USB_DEVICE(0x0cf3, 0xe004), .driver_info = BTUSB_ATH3012 },
> + { USB_DEVICE(0x0cf3, 0xe005), .driver_info = BTUSB_ATH3012 },
> { USB_DEVICE(0x0930, 0x0219), .driver_info = BTUSB_ATH3012 },
> { USB_DEVICE(0x0489, 0xe057), .driver_info = BTUSB_ATH3012 },
> { USB_DEVICE(0x13d3, 0x3393), .driver_info = BTUSB_ATH3012 },
This patch ended up in 3.15 as
-----
[aholler@krabat linux]# git diff ca58e5~1..ca58e5
diff --git a/drivers/bluetooth/ath3k.c b/drivers/bluetooth/ath3k.c
index 59b2e6a..bc5cf90 100644
--- a/drivers/bluetooth/ath3k.c
+++ b/drivers/bluetooth/ath3k.c
@@ -89,6 +89,7 @@ static const struct usb_device_id ath3k_table[] = {
{ USB_DEVICE(0x0b05, 0x17d0) },
{ USB_DEVICE(0x0CF3, 0x0036) },
{ USB_DEVICE(0x0CF3, 0x3004) },
+ { USB_DEVICE(0x0CF3, 0x3005) },
{ USB_DEVICE(0x0CF3, 0x3008) },
{ USB_DEVICE(0x0CF3, 0x311D) },
{ USB_DEVICE(0x0CF3, 0x311E) },
@@ -137,6 +138,7 @@ static const struct usb_device_id ath3k_blist_tbl[] = {
{ USB_DEVICE(0x0b05, 0x17d0), .driver_info = BTUSB_ATH3012 },
{ USB_DEVICE(0x0CF3, 0x0036), .driver_info = BTUSB_ATH3012 },
{ USB_DEVICE(0x0cf3, 0x3004), .driver_info = BTUSB_ATH3012 },
+ { USB_DEVICE(0x0cf3, 0x3005), .driver_info = BTUSB_ATH3012 },
{ USB_DEVICE(0x0cf3, 0x3008), .driver_info = BTUSB_ATH3012 },
{ USB_DEVICE(0x0cf3, 0x311D), .driver_info = BTUSB_ATH3012 },
{ USB_DEVICE(0x0cf3, 0x311E), .driver_info = BTUSB_ATH3012 },
diff --git a/drivers/bluetooth/btusb.c b/drivers/bluetooth/btusb.c
index 199b9d4..f338b0c 100644
--- a/drivers/bluetooth/btusb.c
+++ b/drivers/bluetooth/btusb.c
@@ -159,6 +159,7 @@ static const struct usb_device_id blacklist_table[] = {
{ USB_DEVICE(0x0b05, 0x17d0), .driver_info = BTUSB_ATH3012 },
{ USB_DEVICE(0x0cf3, 0x0036), .driver_info = BTUSB_ATH3012 },
{ USB_DEVICE(0x0cf3, 0x3004), .driver_info = BTUSB_ATH3012 },
+ { USB_DEVICE(0x0cf3, 0x3005), .driver_info = BTUSB_ATH3012 },
{ USB_DEVICE(0x0cf3, 0x3008), .driver_info = BTUSB_ATH3012 },
{ USB_DEVICE(0x0cf3, 0x311d), .driver_info = BTUSB_ATH3012 },
{ USB_DEVICE(0x0cf3, 0x311e), .driver_info = BTUSB_ATH3012 },
-----
which is wrong and disables the ath3k driver.
Alexander Holler
^ permalink raw reply related [flat|nested] 13+ messages in thread
* Re: [PATCH] Add a new PID/VID 0cf3/e005 for AR3012.
2014-06-20 10:01 ` Alexander Holler
@ 2014-06-20 10:50 ` Marcel Holtmann
2014-07-08 7:31 ` Alexander Holler
0 siblings, 1 reply; 13+ messages in thread
From: Marcel Holtmann @ 2014-06-20 10:50 UTC (permalink / raw)
To: Alexander Holler
Cc: Peng Chen, Gustavo F. Padovan, Linux Bluetooth mailing list, kumo,
taowang
Hi Alexander,
>> ---
>> drivers/bluetooth/ath3k.c | 2 ++
>> drivers/bluetooth/btusb.c | 1 +
>> 2 files changed, 3 insertions(+)
>>
>> diff --git a/drivers/bluetooth/ath3k.c b/drivers/bluetooth/ath3k.c
>> index 11f467c..10e9a64 100644
>> --- a/drivers/bluetooth/ath3k.c
>> +++ b/drivers/bluetooth/ath3k.c
>> @@ -85,6 +85,7 @@ static struct usb_device_id ath3k_table[] = {
>> { USB_DEVICE(0x04CA, 0x3008) },
>> { USB_DEVICE(0x13d3, 0x3362) },
>> { USB_DEVICE(0x0CF3, 0xE004) },
>> + { USB_DEVICE(0x0CF3, 0xE005) },
>> { USB_DEVICE(0x0930, 0x0219) },
>> { USB_DEVICE(0x0489, 0xe057) },
>> { USB_DEVICE(0x13d3, 0x3393) },
>> @@ -122,6 +123,7 @@ static struct usb_device_id ath3k_blist_tbl[] = {
>> { USB_DEVICE(0x04ca, 0x3008), .driver_info = BTUSB_ATH3012 },
>> { USB_DEVICE(0x13d3, 0x3362), .driver_info = BTUSB_ATH3012 },
>> { USB_DEVICE(0x0cf3, 0xe004), .driver_info = BTUSB_ATH3012 },
>> + { USB_DEVICE(0x0cf3, 0xe005), .driver_info = BTUSB_ATH3012 },
>> { USB_DEVICE(0x0930, 0x0219), .driver_info = BTUSB_ATH3012 },
>> { USB_DEVICE(0x0489, 0xe057), .driver_info = BTUSB_ATH3012 },
>> { USB_DEVICE(0x13d3, 0x3393), .driver_info = BTUSB_ATH3012 },
>> diff --git a/drivers/bluetooth/btusb.c b/drivers/bluetooth/btusb.c
>> index de4cf4d..299df99 100644
>> --- a/drivers/bluetooth/btusb.c
>> +++ b/drivers/bluetooth/btusb.c
>> @@ -148,6 +148,7 @@ static struct usb_device_id blacklist_table[] = {
>> { USB_DEVICE(0x04ca, 0x3008), .driver_info = BTUSB_ATH3012 },
>> { USB_DEVICE(0x13d3, 0x3362), .driver_info = BTUSB_ATH3012 },
>> { USB_DEVICE(0x0cf3, 0xe004), .driver_info = BTUSB_ATH3012 },
>> + { USB_DEVICE(0x0cf3, 0xe005), .driver_info = BTUSB_ATH3012 },
>> { USB_DEVICE(0x0930, 0x0219), .driver_info = BTUSB_ATH3012 },
>> { USB_DEVICE(0x0489, 0xe057), .driver_info = BTUSB_ATH3012 },
>> { USB_DEVICE(0x13d3, 0x3393), .driver_info = BTUSB_ATH3012 },
>
> This patch ended up in 3.15 as
>
> -----
> [aholler@krabat linux]# git diff ca58e5~1..ca58e5
> diff --git a/drivers/bluetooth/ath3k.c b/drivers/bluetooth/ath3k.c
> index 59b2e6a..bc5cf90 100644
> --- a/drivers/bluetooth/ath3k.c
> +++ b/drivers/bluetooth/ath3k.c
> @@ -89,6 +89,7 @@ static const struct usb_device_id ath3k_table[] = {
> { USB_DEVICE(0x0b05, 0x17d0) },
> { USB_DEVICE(0x0CF3, 0x0036) },
> { USB_DEVICE(0x0CF3, 0x3004) },
> + { USB_DEVICE(0x0CF3, 0x3005) },
> { USB_DEVICE(0x0CF3, 0x3008) },
> { USB_DEVICE(0x0CF3, 0x311D) },
> { USB_DEVICE(0x0CF3, 0x311E) },
> @@ -137,6 +138,7 @@ static const struct usb_device_id ath3k_blist_tbl[] = {
> { USB_DEVICE(0x0b05, 0x17d0), .driver_info = BTUSB_ATH3012 },
> { USB_DEVICE(0x0CF3, 0x0036), .driver_info = BTUSB_ATH3012 },
> { USB_DEVICE(0x0cf3, 0x3004), .driver_info = BTUSB_ATH3012 },
> + { USB_DEVICE(0x0cf3, 0x3005), .driver_info = BTUSB_ATH3012 },
> { USB_DEVICE(0x0cf3, 0x3008), .driver_info = BTUSB_ATH3012 },
> { USB_DEVICE(0x0cf3, 0x311D), .driver_info = BTUSB_ATH3012 },
> { USB_DEVICE(0x0cf3, 0x311E), .driver_info = BTUSB_ATH3012 },
> diff --git a/drivers/bluetooth/btusb.c b/drivers/bluetooth/btusb.c
> index 199b9d4..f338b0c 100644
> --- a/drivers/bluetooth/btusb.c
> +++ b/drivers/bluetooth/btusb.c
> @@ -159,6 +159,7 @@ static const struct usb_device_id blacklist_table[] = {
> { USB_DEVICE(0x0b05, 0x17d0), .driver_info = BTUSB_ATH3012 },
> { USB_DEVICE(0x0cf3, 0x0036), .driver_info = BTUSB_ATH3012 },
> { USB_DEVICE(0x0cf3, 0x3004), .driver_info = BTUSB_ATH3012 },
> + { USB_DEVICE(0x0cf3, 0x3005), .driver_info = BTUSB_ATH3012 },
> { USB_DEVICE(0x0cf3, 0x3008), .driver_info = BTUSB_ATH3012 },
> { USB_DEVICE(0x0cf3, 0x311d), .driver_info = BTUSB_ATH3012 },
> { USB_DEVICE(0x0cf3, 0x311e), .driver_info = BTUSB_ATH3012 },
> -----
>
> which is wrong and disables the ath3k driver.
I reverted the broken patch in bluetooth.git now and marked it for 3.15 stable.
Regards
Marcel
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: [PATCH] Add a new PID/VID 0cf3/e005 for AR3012.
2014-06-20 10:50 ` Marcel Holtmann
@ 2014-07-08 7:31 ` Alexander Holler
2014-07-08 10:35 ` Marcel Holtmann
0 siblings, 1 reply; 13+ messages in thread
From: Alexander Holler @ 2014-07-08 7:31 UTC (permalink / raw)
To: Marcel Holtmann
Cc: Peng Chen, Gustavo F. Padovan, Linux Bluetooth mailing list, kumo,
taowang
Am 20.06.2014 12:50, schrieb Marcel Holtmann:
>> which is wrong and disables the ath3k driver.
>
> I reverted the broken patch in bluetooth.git now and marked it for 3.15 stable.
Must got missed, it's not in 3.15.4 nor in 3.15.5.
As my solution was a revert too, I can offer a Tested-By, if such is
needed, at least in regard to the point that ath3k-dongles will work
again after reverting ca58e5.
Regards,
Alexander Holler
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: [PATCH] Add a new PID/VID 0cf3/e005 for AR3012.
2014-07-08 7:31 ` Alexander Holler
@ 2014-07-08 10:35 ` Marcel Holtmann
2014-07-08 10:49 ` Alexander Holler
0 siblings, 1 reply; 13+ messages in thread
From: Marcel Holtmann @ 2014-07-08 10:35 UTC (permalink / raw)
To: Alexander Holler
Cc: Peng Chen, Gustavo F. Padovan, Linux Bluetooth mailing list, kumo,
taowang
Hi Alexander,
>>> which is wrong and disables the ath3k driver.
>>
>> I reverted the broken patch in bluetooth.git now and marked it for 3.15 stable.
>
> Must got missed, it's not in 3.15.4 nor in 3.15.5.
>
> As my solution was a revert too, I can offer a Tested-By, if such is needed, at least in regard to the point that ath3k-dongles will work again after reverting ca58e5.
it is in net tree, but not in 3.16-rcX yet. Only after it got into Linus' tree it can be backported to stable tree.
Regards
Marcel
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: [PATCH] Add a new PID/VID 0cf3/e005 for AR3012.
2014-07-08 10:35 ` Marcel Holtmann
@ 2014-07-08 10:49 ` Alexander Holler
2014-07-09 10:48 ` Alexander Holler
0 siblings, 1 reply; 13+ messages in thread
From: Alexander Holler @ 2014-07-08 10:49 UTC (permalink / raw)
To: Marcel Holtmann
Cc: Peng Chen, Gustavo F. Padovan, Linux Bluetooth mailing list, kumo,
taowang
Am 08.07.2014 12:35, schrieb Marcel Holtmann:
> Hi Alexander,
>
>>>> which is wrong and disables the ath3k driver.
>>>
>>> I reverted the broken patch in bluetooth.git now and marked it for 3.15 stable.
>>
>> Must got missed, it's not in 3.15.4 nor in 3.15.5.
>>
>> As my solution was a revert too, I can offer a Tested-By, if such is needed, at least in regard to the point that ath3k-dongles will work again after reverting ca58e5.
>
> it is in net tree, but not in 3.16-rcX yet. Only after it got into Linus' tree it can be backported to stable tree.
Ah, the funny maze of linux kernel repos. ;)
I've just wondered because I've seen several bluetooth related patches
in 3.15.5 and therefor got the impression it got missed.
Regards,
Alexander Holler
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: [PATCH] Add a new PID/VID 0cf3/e005 for AR3012.
2014-07-08 10:49 ` Alexander Holler
@ 2014-07-09 10:48 ` Alexander Holler
2014-07-09 11:05 ` Marcel Holtmann
0 siblings, 1 reply; 13+ messages in thread
From: Alexander Holler @ 2014-07-09 10:48 UTC (permalink / raw)
To: Marcel Holtmann
Cc: Peng Chen, Gustavo F. Padovan, Linux Bluetooth mailing list, kumo,
taowang
Am 08.07.2014 12:49, schrieb Alexander Holler:
> Am 08.07.2014 12:35, schrieb Marcel Holtmann:
>> Hi Alexander,
>>
>>>>> which is wrong and disables the ath3k driver.
>>>>
>>>> I reverted the broken patch in bluetooth.git now and marked it for
>>>> 3.15 stable.
>>>
>>> Must got missed, it's not in 3.15.4 nor in 3.15.5.
>>>
>>> As my solution was a revert too, I can offer a Tested-By, if such is
>>> needed, at least in regard to the point that ath3k-dongles will work
>>> again after reverting ca58e5.
>>
>> it is in net tree, but not in 3.16-rcX yet. Only after it got into
>> Linus' tree it can be backported to stable tree.
>
> Ah, the funny maze of linux kernel repos. ;)
That lead me to the idea to rename bluetooth-next to bluetooth-ubernext
because that what be more appropriate if bluetooth-next ends up in
net-next or linux-next or something-else-next. ;)
Sorry for the joke. ;)
Regards,
Alexander Holler
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: [PATCH] Add a new PID/VID 0cf3/e005 for AR3012.
2014-07-09 10:48 ` Alexander Holler
@ 2014-07-09 11:05 ` Marcel Holtmann
2014-07-09 11:21 ` Alexander Holler
0 siblings, 1 reply; 13+ messages in thread
From: Marcel Holtmann @ 2014-07-09 11:05 UTC (permalink / raw)
To: Alexander Holler
Cc: Peng Chen, Gustavo F. Padovan, Linux Bluetooth mailing list, kumo,
taowang
Hi Alexander,
>>>>>> which is wrong and disables the ath3k driver.
>>>>>
>>>>> I reverted the broken patch in bluetooth.git now and marked it for
>>>>> 3.15 stable.
>>>>
>>>> Must got missed, it's not in 3.15.4 nor in 3.15.5.
>>>>
>>>> As my solution was a revert too, I can offer a Tested-By, if such is
>>>> needed, at least in regard to the point that ath3k-dongles will work
>>>> again after reverting ca58e5.
>>>
>>> it is in net tree, but not in 3.16-rcX yet. Only after it got into
>>> Linus' tree it can be backported to stable tree.
>>
>> Ah, the funny maze of linux kernel repos. ;)
>
> That lead me to the idea to rename bluetooth-next to bluetooth-ubernext because that what be more appropriate if bluetooth-next ends up in net-next or linux-next or something-else-next. ;)
it goes bluetooth-next -> linux-next
`- wireless-next -> net-next -> linux
Regards
Marcel
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: [PATCH] Add a new PID/VID 0cf3/e005 for AR3012.
2014-07-09 11:05 ` Marcel Holtmann
@ 2014-07-09 11:21 ` Alexander Holler
2014-07-09 11:47 ` Alexander Holler
0 siblings, 1 reply; 13+ messages in thread
From: Alexander Holler @ 2014-07-09 11:21 UTC (permalink / raw)
To: Marcel Holtmann
Cc: Peng Chen, Gustavo F. Padovan, Linux Bluetooth mailing list, kumo,
taowang
Am 09.07.2014 13:05, schrieb Marcel Holtmann:
> Hi Alexander,
>
>>>>>>> which is wrong and disables the ath3k driver.
>>>>>>
>>>>>> I reverted the broken patch in bluetooth.git now and marked it for
>>>>>> 3.15 stable.
>>>>>
>>>>> Must got missed, it's not in 3.15.4 nor in 3.15.5.
>>>>>
>>>>> As my solution was a revert too, I can offer a Tested-By, if such is
>>>>> needed, at least in regard to the point that ath3k-dongles will work
>>>>> again after reverting ca58e5.
>>>>
>>>> it is in net tree, but not in 3.16-rcX yet. Only after it got into
>>>> Linus' tree it can be backported to stable tree.
>>>
>>> Ah, the funny maze of linux kernel repos. ;)
>>
>> That lead me to the idea to rename bluetooth-next to bluetooth-ubernext because that what be more appropriate if bluetooth-next ends up in net-next or linux-next or something-else-next. ;)
>
> it goes bluetooth-next -> linux-next
> `- wireless-next -> net-next -> linux
Oh, so ubernext would be an understatement.
That makes up for some interesting stats about timing.
If I assume every one of those next repos do use just a 2 week testing
period before forwarding patches, I end up with 2 + 2 + 2 + 2 weeks.
And if every one of these trees do use one month, this would be 4 month
until a patch ends up in mainline where it resides another 3 month until
it reaches people.
Regards,
Alexander Holler
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: [PATCH] Add a new PID/VID 0cf3/e005 for AR3012.
2014-07-09 11:21 ` Alexander Holler
@ 2014-07-09 11:47 ` Alexander Holler
0 siblings, 0 replies; 13+ messages in thread
From: Alexander Holler @ 2014-07-09 11:47 UTC (permalink / raw)
To: Marcel Holtmann
Cc: Peng Chen, Gustavo F. Padovan, Linux Bluetooth mailing list, kumo,
taowang
Am 09.07.2014 13:21, schrieb Alexander Holler:
> Am 09.07.2014 13:05, schrieb Marcel Holtmann:
>> Hi Alexander,
>>
>>>>>>>> which is wrong and disables the ath3k driver.
>>>>>>>
>>>>>>> I reverted the broken patch in bluetooth.git now and marked it for
>>>>>>> 3.15 stable.
>>>>>>
>>>>>> Must got missed, it's not in 3.15.4 nor in 3.15.5.
>>>>>>
>>>>>> As my solution was a revert too, I can offer a Tested-By, if such is
>>>>>> needed, at least in regard to the point that ath3k-dongles will work
>>>>>> again after reverting ca58e5.
>>>>>
>>>>> it is in net tree, but not in 3.16-rcX yet. Only after it got into
>>>>> Linus' tree it can be backported to stable tree.
>>>>
>>>> Ah, the funny maze of linux kernel repos. ;)
>>>
>>> That lead me to the idea to rename bluetooth-next to
>>> bluetooth-ubernext because that what be more appropriate if
>>> bluetooth-next ends up in net-next or linux-next or
>>> something-else-next. ;)
>>
>> it goes bluetooth-next -> linux-next
>> `- wireless-next -> net-next -> linux
>
> Oh, so ubernext would be an understatement.
>
> That makes up for some interesting stats about timing.
>
> If I assume every one of those next repos do use just a 2 week testing
> period before forwarding patches, I end up with 2 + 2 + 2 + 2 weeks.
>
> And if every one of these trees do use one month, this would be 4 month
> until a patch ends up in mainline where it resides another 3 month until
> it reaches people.
And if we look at the patch about which revert we are currently talking
about, it's more like 2 + 2 + 2 + 2 months + 3 months in mainline-rc,
because the patch (see subject) was posted 2013-08-30 and became visible
on 2014-06-08 (with 3.15).
Quiet interesting.
Regards,
Alexander Holler
^ permalink raw reply [flat|nested] 13+ messages in thread
end of thread, other threads:[~2014-07-09 11:47 UTC | newest]
Thread overview: 13+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-08-30 9:41 [PATCH] Add a new PID/VID 0cf3/e005 for AR3012 Peng Chen
2013-09-01 16:50 ` Gustavo Padovan
-- strict thread matches above, loose matches on Subject: below --
2013-08-30 9:09 Peng Chen
2014-03-05 18:59 ` Johan Hedberg
2014-06-20 10:01 ` Alexander Holler
2014-06-20 10:50 ` Marcel Holtmann
2014-07-08 7:31 ` Alexander Holler
2014-07-08 10:35 ` Marcel Holtmann
2014-07-08 10:49 ` Alexander Holler
2014-07-09 10:48 ` Alexander Holler
2014-07-09 11:05 ` Marcel Holtmann
2014-07-09 11:21 ` Alexander Holler
2014-07-09 11:47 ` Alexander Holler
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).