[ath9k-devel] Bluetooth not working on AR9462/0489:e076
Hello, I have some troubles making my bluetooth device work on Ubutun 14.10 (Kernel: 3.16.0-29-generic, linux-firmware* installed). Laptop : Acer VN7-571G The device seems to be a combo of Wifi on PCI (Atheros AR9462) and Bluetooth on USB (Foxconn / Hon Hai). lspci: - 02:00.0 Network controller: Qualcomm Atheros AR9462 Wireless Network Adapter (rev 01) - - Kernel driver in use: ath9k lsusb: - Bus 002 Device 002: ID 0489:e076 Foxconn / Hon Hai - - Kernel driver in use: (I don't know how to obtain this information, but i guess ath3k) Trying with a bluetooth mouse and a bluetooth-4 android phone: On cold boot: the device seems to work (and no firmware loading errors) but it is impossible to list or connect to bluetooth new device, On reboot from Windows 8.1 to Ubuntu 14.10: It is possible to list devices and the mouse and the Android phone connexion works perfectly, On subsequent reboots (ubuntu=ubuntu): It is possible to list devices ; the mouse and the Android phone connexion works perfectly (the connexions are remembered), On subsequent cold boots: The connexions are remembered but communication with the mouse or the phone do not work. My understanding is that Windows loads a firmware to the device that makes the device working in Linux. Is it possible that the Linux driver fails to notify that a firmware must be loaded ? Thanks and sorry for my english (not my native language) This message is linked to: - the thread How can I disable BT on AR9462 chip in Ubuntu kernel By Sujith Manoharan, - ask-ubuntu thread: http://askubuntu.com/questions/566890/bluetooth-not-working-with-atheros-ar9462-chip-on-utopic-3-16-kernel ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Re: [ath9k-devel] [PATCH] ath9k: ignore radar PHY errors when DFS is not enabled
On Friday 09 January 2015 19:57:37 Arend van Spriel wrote: On 01/09/15 17:54, Simon Wunderlich wrote: Performing spectral scans on 5 GHz channels may result in PHY errors sent by the hardware, even if DFS support is not enabled in the driver (e.g. channel scanning or passive monitoring). In that case channels may falsely get marked as 'unusable'. To fix that, only process radar PHY errors when radar is explicitly enabled in the driver. Hi Simon, Not an ath9k expert, but I would think those channels would already be marked as unusable, because DFS is disabled in the driver. Or does this also affect 5G channels that do not require DFS. Regards, Arend Hey Arend, maybe that was not really clear, but this is talking about the DFS state unusable. By default, channels are marked in DFS state usable, and after the clear channel assessment (which is done e.g. when starting AP mode) they are marked as available. As soon as radar is detected they are marked as unusable. These DFS state changes should only happen while there is something operating with radar enabled, e.g. AP mode. It should not happen if we just have monitor mode or scan for channels. These channels should then stay in their previous DFS state (e.g. 'usable'). This was borked and this patch tries to fix it. :) Cheers, Simon signature.asc Description: This is a digitally signed message part. ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Re: [ath9k-devel] ath9k-devel Digest, Vol 79, Issue 6
On 01/10/15 03:00, 杨铁军 wrote: Hi Arend My development environment is LINUX 2.26.31 Kernel, and I could not use new version kernel (The whole project work in Kernel 2.26.31, and the 2.26.31 is provided by my device manufactuer, I had no power to update to new kernel). Could you give a suggestion how to test your patch in LINUX 2.26.31? I am new to LINUX. I see. Well, you could grab this backports package [1] and apply the patch there. There is a twiki [2] containing info how to build, etc. Regards, Arend [1] http://www.kernel.org/pub/linux/kernel/projects/backports/stable/v3.19-rc1/backports-3.19-rc1-1.tar.xz [2] https://backports.wiki.kernel.org/ Thanks, David -- Original -- *From: * Arend van Sprielar...@broadcom.com; *Date: * Fri, Jan 9, 2015 06:01 PM *To: * 杨铁军y...@nethdv.com; *Cc: * ath9k-develath9k-devel@lists.ath9k.org; *Subject: * Re: ath9k-devel Digest, Vol 79, Issue 6 On 01/09/15 02:54, 杨铁军 wrote: Hi Arend, I had ATH9k hardware, my wireless device is WLE350NX, it is AR9580 chip. Please send me your code to test! I am new to LINUX. Ok. The patch can be found on patchwork [1]. That page contains download links to get the patch. _mbox_ link can be used with 'git am' command. _patch_ link can be used with 'patch' command. Regards, Arend [1] https://patchwork.kernel.org/patch/5544621/ Regards, David Yang -- Original -- *From: * ath9k-devel-requestath9k-devel-requ...@lists.ath9k.org; *Date: * Thu, Jan 8, 2015 07:00 PM *To: * ath9k-develath9k-devel@lists.ath9k.org; *Subject: * ath9k-devel Digest, Vol 79, Issue 6 Send ath9k-devel mailing list submissions to ath9k-devel@lists.ath9k.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.ath9k.org/mailman/listinfo/ath9k-devel or, via email, send a message with subject or body 'help' to ath9k-devel-requ...@lists.ath9k.org You can reach the person managing the list at ath9k-devel-ow...@lists.ath9k.org When replying, please edit your Subject line so it is more specific than Re: Contents of ath9k-devel digest... Today's Topics: 1. Re: [PATCH] ath: ath9k: use debugfs_create_devm_seqfile() helper for seq_file entries (Kalle Valo) 2. Re: [PATCH] ath: ath9k: use debugfs_create_devm_seqfile() helper for seq_file entries (Sujith Manoharan) -- Message: 1 Date: Wed, 07 Jan 2015 20:05:00 +0200 From: Kalle Valo kv...@codeaurora.org Subject: Re: [ath9k-devel] [PATCH] ath: ath9k: use debugfs_create_devm_seqfile() helper for seq_file entries To: Arend van Spriel ar...@broadcom.com Cc: ath9k-devel@lists.ath9k.org, linux-wireless linux-wirel...@vger.kernel.org Message-ID: 87bnmapiur@kamboji.qca.qualcomm.com Content-Type: text/plain; charset=us-ascii Arend van Spriel ar...@broadcom.com writes: Use the helper to get rid of the file operations per debugfs file. The device driver data contains struct ieee80211_hw pointer and the struct ath9k_softc pointer is assigned to ieee80211_hw::priv so it can be accessed in the seq_file read operation. Cc: ath9k-devel@lists.ath9k.org Signed-off-by: Arend van Spriel ar...@broadcom.com --- Hi Kalle, This patch was reverted in the driver-core repository as I overlooked the use of driver data and caused ath9k driver to crash. I believe this revised patch properly uses it now although I have no ath9k hardware to test this. So I hope some ath9k developers out there can give this patch a run for its money. It compiles and no checkpatch or sparse warnings. The patch applies to the master branch of the wireless-drivers-next repository. Can someone with ath9k hardware test this, please? I'm hesitant to apply this without testing. -- Kalle Valo -- Message: 2 Date: Thu, 8 Jan 2015 08:49:00 +0530 From: Sujith Manoharan suj...@msujith.org Subject: Re: [ath9k-devel] [PATCH] ath: ath9k: use debugfs_create_devm_seqfile() helper for seq_file entries To: Kalle Valo kv...@codeaurora.org Cc: Arend van Spriel ar...@broadcom.com, ath9k-devel@lists.ath9k.org, linux-wireless linux-wirel...@vger.kernel.org Message-ID: 21677.63268.657151.679...@gargle.gargle.howl Content-Type: text/plain; charset=us-ascii Arend van Spriel ar...@broadcom.com writes: Use the helper to get rid of the file operations per debugfs file. The device driver data contains struct ieee80211_hw pointer and the struct ath9k_softc pointer is assigned to ieee80211_hw::priv so it can be accessed in the seq_file read operation. Cc: ath9k-devel@lists.ath9k.org Signed-off-by: Arend van Spriel ar...@broadcom.com Thanks for the patch. Can someone with
Re: [ath9k-devel] Bluetooth not working on AR9462/0489:e076
Sekou DIAKITE wrote: Hello, I have some troubles making my bluetooth device work on Ubutun 14.10 (Kernel: 3.16.0-29-generic, linux-firmware* installed). Can you install the latest backports driver ? https://backports.wiki.kernel.org/index.php/Main_Page https://www.kernel.org/pub/linux/kernel/projects/backports/2014/12/21/ And load the ath9k driver with the parameter btcoex_enable=1 ? (http://wireless.kernel.org/en/users/Drivers/ath9k/btcoex) Sujith ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Re: [ath9k-devel] Bluetooth not working on AR9462/0489:e076
I've installed the latest backport driver and added the btcoex_enable=1. It doesn't change the behavior (bluetooth works only after a reboot from Windows). Maybe this information can help: My laptop has the latest BIOS from acer and the BIOS changelog is Correct BT D3 state (there aren't any other informations). Is it possible to read the ACPI device state of the USB device from /proc /sys or /dev ?, is it possible to force the ACPI device state to D0 at boot ? Thank's, Sekou 2015-01-10 16:04 GMT+01:00 Sujith Manoharan suj...@msujith.org: Sekou DIAKITE wrote: Hello, I have some troubles making my bluetooth device work on Ubutun 14.10 (Kernel: 3.16.0-29-generic, linux-firmware* installed). Can you install the latest backports driver ? https://backports.wiki.kernel.org/index.php/Main_Page https://www.kernel.org/pub/linux/kernel/projects/backports/2014/12/21/ And load the ath9k driver with the parameter btcoex_enable=1 ? (http://wireless.kernel.org/en/users/Drivers/ath9k/btcoex) Sujith ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
[ath9k-devel] [PATCH] ath9k_htc: Add a module parameter to disable blink
Add an option blink to enable or disable the LED blink. The default
value is set to 1 so that existing users would not experience any
unexpected changes.
---
drivers/net/wireless/ath/ath9k/htc.h | 1 +
drivers/net/wireless/ath/ath9k/htc_drv_gpio.c | 4
drivers/net/wireless/ath/ath9k/htc_drv_init.c | 4
3 files changed, 9 insertions(+)
diff --git a/drivers/net/wireless/ath/ath9k/htc.h
b/drivers/net/wireless/ath/ath9k/htc.h
index 9dde265..5697097 100644
--- a/drivers/net/wireless/ath/ath9k/htc.h
+++ b/drivers/net/wireless/ath/ath9k/htc.h
@@ -44,6 +44,7 @@
extern struct ieee80211_ops ath9k_htc_ops;
extern int htc_modparam_nohwcrypt;
+extern int led_blink;
enum htc_phymode {
HTC_MODE_11NA = 0,
diff --git a/drivers/net/wireless/ath/ath9k/htc_drv_gpio.c
b/drivers/net/wireless/ath/ath9k/htc_drv_gpio.c
index 50f74a2..998b558 100644
--- a/drivers/net/wireless/ath/ath9k/htc_drv_gpio.c
+++ b/drivers/net/wireless/ath/ath9k/htc_drv_gpio.c
@@ -279,6 +279,10 @@ void ath9k_init_leds(struct ath9k_htc_priv *priv)
else
priv-ah-led_pin = ATH_LED_PIN_DEF;
+ if (!led_blink)
+ priv-led_cdev.default_trigger =
+ ieee80211_get_radio_led_name(priv-hw);
+
ath9k_configure_leds(priv);
snprintf(priv-led_name, sizeof(priv-led_name),
diff --git a/drivers/net/wireless/ath/ath9k/htc_drv_init.c
b/drivers/net/wireless/ath/ath9k/htc_drv_init.c
index e8fa944..c762d84 100644
--- a/drivers/net/wireless/ath/ath9k/htc_drv_init.c
+++ b/drivers/net/wireless/ath/ath9k/htc_drv_init.c
@@ -38,6 +38,10 @@ static int ath9k_ps_enable;
module_param_named(ps_enable, ath9k_ps_enable, int, 0444);
MODULE_PARM_DESC(ps_enable, Enable WLAN PowerSave);
+int led_blink = 1;
+module_param_named(blink, led_blink, int, 0444);
+MODULE_PARM_DESC(blink, Enable LED blink on activity);
+
#ifdef CONFIG_MAC80211_LEDS
static const struct ieee80211_tpt_blink ath9k_htc_tpt_blink[] = {
{ .throughput = 0 * 1024, .blink_time = 334 },
--
2.2.1
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
[ath9k-devel] [PATCH] ath9k_htc: Add a module parameter to disable blink
Hi all,
The attached patch adds a module parameter to disable blink for ath9k_htc. Much
of it imitates how
ath9k makes its blink parameter.
Best,
Hong
From f7d643f3421dea4953abe370857234a4cbc0e11c Mon Sep 17 00:00:00 2001
From: Hong Xu h...@topbug.net
Date: Sat, 10 Jan 2015 22:14:59 -0800
Subject: [PATCH] ath9k_htc: Add a module parameter to disable blink
Add an option blink to enable or disable the LED blink. The default
value is set to 1 so that existing users would not experience any
unexpected changes.
---
drivers/net/wireless/ath/ath9k/htc.h | 1 +
drivers/net/wireless/ath/ath9k/htc_drv_gpio.c | 4
drivers/net/wireless/ath/ath9k/htc_drv_init.c | 4
3 files changed, 9 insertions(+)
diff --git a/drivers/net/wireless/ath/ath9k/htc.h b/drivers/net/wireless/ath/ath9k/htc.h
index 9dde265..5697097 100644
--- a/drivers/net/wireless/ath/ath9k/htc.h
+++ b/drivers/net/wireless/ath/ath9k/htc.h
@@ -44,6 +44,7 @@
extern struct ieee80211_ops ath9k_htc_ops;
extern int htc_modparam_nohwcrypt;
+extern int led_blink;
enum htc_phymode {
HTC_MODE_11NA = 0,
diff --git a/drivers/net/wireless/ath/ath9k/htc_drv_gpio.c b/drivers/net/wireless/ath/ath9k/htc_drv_gpio.c
index 50f74a2..998b558 100644
--- a/drivers/net/wireless/ath/ath9k/htc_drv_gpio.c
+++ b/drivers/net/wireless/ath/ath9k/htc_drv_gpio.c
@@ -279,6 +279,10 @@ void ath9k_init_leds(struct ath9k_htc_priv *priv)
else
priv-ah-led_pin = ATH_LED_PIN_DEF;
+ if (!led_blink)
+ priv-led_cdev.default_trigger =
+ ieee80211_get_radio_led_name(priv-hw);
+
ath9k_configure_leds(priv);
snprintf(priv-led_name, sizeof(priv-led_name),
diff --git a/drivers/net/wireless/ath/ath9k/htc_drv_init.c b/drivers/net/wireless/ath/ath9k/htc_drv_init.c
index e8fa944..c762d84 100644
--- a/drivers/net/wireless/ath/ath9k/htc_drv_init.c
+++ b/drivers/net/wireless/ath/ath9k/htc_drv_init.c
@@ -38,6 +38,10 @@ static int ath9k_ps_enable;
module_param_named(ps_enable, ath9k_ps_enable, int, 0444);
MODULE_PARM_DESC(ps_enable, Enable WLAN PowerSave);
+int led_blink = 1;
+module_param_named(blink, led_blink, int, 0444);
+MODULE_PARM_DESC(blink, Enable LED blink on activity);
+
#ifdef CONFIG_MAC80211_LEDS
static const struct ieee80211_tpt_blink ath9k_htc_tpt_blink[] = {
{ .throughput = 0 * 1024, .blink_time = 334 },
--
2.2.1
signature.asc
Description: PGP signature
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
