On Wed, May 22, 2013 at 02:12:13PM +0200, Francisco Cuesta wrote:
Hello,
I would like to know whether someone might point out where a sta-mode
scan in ath9k driver is carried out. I mean, if I want to perform such
a scan, I have seen that hostapd or wpa supplicant requests the driver
From: Mohammed Shafi Shajakhan moham...@qca.qualcomm.com
Roger says, Ubiquiti produce 2 versions of their WiFiStation USB adapter. One
has an internal antenna, the other has an external antenna and
name suffix EXT. They have separate USB ids and in distribution
openSUSE 12.2 (kernel 3.4.6
From: Mohammed Shafi Shajakhan moham...@qca.qualcomm.com
When WLAN is idle ensure we downgrade to FTP_STOMP_LOW weight
(from STOMP_LOW) to provide more bandwidth for BT FTP profile.
WLAN's idleness can be estimated by taking into account of the
rx data packets and just ignore beacons, qos
From: Mohammed Shafi Shajakhan moham...@qca.qualcomm.com
This will allow us to create virtual interface the driver supports.
Also this ensures multivif support and limitation advertised
by the driver is taken care in cfg80211 itself.
Signed-off-by: Mohammed Shafi Shajakhan moham
From: Mohammed Shafi Shajakhan moham...@qca.qualcomm.com
Once the driver advertizes interface combination logic
based on its firmware/hardware limitation, cfg80211
takes care of all the necessary logic such as maximum
beaconing vifs, standlone interface etc.
Signed-off-by: Mohammed Shafi
From: Mohammed Shafi Shajakhan moham...@qca.qualcomm.com
Currently ath9k need to have beacon interval matched
between STA mode and beaconing mode. Advertize this
through interface combinations.
Signed-off-by: Mohammed Shafi Shajakhan moham...@qca.qualcomm.com
---
drivers/net/wireless/ath/ath9k
Hi Holger,
On Friday 28 September 2012 02:30 PM, Holger Schurig wrote:
We WLAN is idle we can some better bandwidth to FTP by
setting STOMP_LOW_FTP where stomping the FTP BT is pretty
much reduced when compared to setting STOMP_LOW weight.
I understand that english isn't your first language
From: Mohammed Shafi Shajakhan moham...@qca.qualcomm.com
We WLAN is idle we can some better bandwidth to FTP by
setting STOMP_LOW_FTP where stomping the FTP BT is pretty
much reduced when compared to setting STOMP_LOW weight.
we calculate WLAN is idle by taking into account of the
rx data packets
From: Mohammed Shafi Shajakhan moham...@qca.qualcomm.com
Currently ath9k need to have beacon interval matched
between STA mode and beaconing mode. Advertize this
through interface combinations. Need to test this
properly.
Signed-off-by: Mohammed Shafi Shajakhan moham...@qca.qualcomm.com
From: Mohammed Shafi Shajakhan moham...@qca.qualcomm.com
Once the driver advertizes interface combination logic
based on its firmware/hardware limitation, cfg80211
takes care of all the necessary logic such as maximum
beaconing vifs, standlone interface etc.
Signed-off-by: Antonio Quartulli
to be advertized
in the combinations allowed.
Signed-off-by: Antonio Quartulli or...@autistici.org
Signed-off-by: Mohammed Shafi Shajakhan moham...@qca.qualcomm.com
---
drivers/net/wireless/ath/ath9k/htc_drv_init.c | 35 +
1 files changed, 35 insertions(+), 0 deletions(-)
diff
On Thursday 27 September 2012 09:22 PM, Mohammed Shafi Shajakhan wrote:
From: Antonio Quartulli or...@autistici.org
Advertize allowed VIFs combinations to the cfg80211 sublayer.
Other than that, practical tests shown that ath9k_htc devices allow an
IBSS VIF to coexist with VIF set up on other
Hi Sujith,
On Friday 28 September 2012 07:53 AM, Sujith Manoharan wrote:
Mohammed Shafi Shajakhan wrote:
From: Antonio Quartulli or...@autistici.org
Advertize allowed VIFs combinations to the cfg80211 sublayer.
Other than that, practical tests shown that ath9k_htc devices allow an
IBSS VIF
Shafi Shajakhan moham...@qca.qualcomm.com
---
drivers/net/wireless/ath/ath9k/recv.c |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/net/wireless/ath/ath9k/recv.c
b/drivers/net/wireless/ath/ath9k/recv.c
index 9b2a8cc..a04028b 100644
--- a/drivers/net/wireless/ath
On Tue, Aug 21, 2012 at 10:43 AM, Mohammed Shafi Shajakhan
moham...@qca.qualcomm.com wrote:
Hi,
On Friday 17 August 2012 12:42 PM, Sunil Mehta wrote:
Hi
We are using AR9331 and are currently using the device in - AP mode, and
Station mode.
We would like to use the device for a P2P
Hi Tom,
On Monday 17 September 2012 10:47 AM, Mohammed Shafi Shajakhan wrote:
Hi Tom,
+ linux-wireless
On Saturday 15 September 2012 12:24 AM, Thomas Wagner wrote:
Hi,
I'm really not sure about this being tied to sc-nvifs.
If it's mesh related, how about just adding a check
Hi Tom,
+ linux-wireless
On Saturday 15 September 2012 12:24 AM, Thomas Wagner wrote:
Hi,
I'm really not sure about this being tied to sc-nvifs.
If it's mesh related, how about just adding a check for the number of mesh
interfaces [...]
No, it is not mesh related!
Several frames where
From: Mohammed Shafi Shajakhan moham...@qca.qualcomm.com
Update the 'hw_timer_enabled' to 'false' wherever we are stopping
hardware generic timers, excecpt the case where we start them
again immediately.
Signed-off-by: Mohammed Shafi Shajakhan moham...@qca.qualcomm.com
---
drivers/net/wireless
From: Mohammed Shafi Shajakhan moham...@qca.qualcomm.com
We need to have the promiscus mode enabled for older
chipset(ie rule out many frames being filtered in the
hardware itself)if 'FIF_OTHER_BSS' flag is set, when we
start the mesh mode. Fix this by enabling promiscus
mode for all chipsets
-by: Mohammed Shafi Shajakhan moham...@qca.qualcomm.com
---
drivers/net/wireless/ath/ath9k/recv.c |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/net/wireless/ath/ath9k/recv.c
b/drivers/net/wireless/ath/ath9k/recv.c
index 4480c0c..76db0b3 100644
--- a/drivers/net
On Friday 14 September 2012 08:16 PM, Mohammed Shafi Shajakhan wrote:
From: Mohammed Shafi Shajakhan moham...@qca.qualcomm.com
We need to have the promiscus mode enabled for older
chipset(ie rule out many frames being filtered in the
hardware itself)if 'FIF_OTHER_BSS' flag is set, when we
From: Mohammed Shafi Shajakhan moham...@qca.qualcomm.com
We WLAN is idle we can some better bandwidth to FTP by
setting STOMP_LOW_FTP where stomping the FTP BT is pretty
much reduced when compared to setting STOMP_LOW weight.
we calculate WLAN is idle by taking into account of the
rx data packets
From: Mohammed Shafi Shajakhan moham...@qca.qualcomm.com
Having generic hardware timer interrupt in debugfs
would come handy when we are debugging 3 WIRE
BTCOEX issues.
Signed-off-by: Mohammed Shafi Shajakhan moham...@qca.qualcomm.com
---
drivers/net/wireless/ath/ath9k/debug.c |3
From: Mohammed Shafi Shajakhan moham...@qca.qualcomm.com
There is a possibility that AR_MCI_GPM_1 register can
return 0xdeadbeef and this results in caching of invalid
GPM index in ar9003_mci_is_gpm_valid. Ensure we
have appropriate checks to avoid this.
Cc: xijin luo xi...@qca.qualcomm.com
From: Mohammed Shafi Shajakhan moham...@qca.qualcomm.com
Its more correct to convert btcoex_period to 'us' while
comparing with btcoex_no_stomp which is in 'us'.
Did not find any functionality issues being fixed,
as the generic hardware timer triggers are usually
refreshed with the newer duty
From: Mohammed Shafi Shajakhan moham...@qca.qualcomm.com
Additionally it has a neat debug message informing us
that we are stopping the ANI algorithm.
Signed-off-by: Mohammed Shafi Shajakhan moham...@qca.qualcomm.com
---
drivers/net/wireless/ath/ath9k/main.c |2 +-
1 files changed, 1
From: Mohammed Shafi Shajakhan moham...@qca.qualcomm.com
Signed-off-by: Mohammed Shafi Shajakhan moham...@qca.qualcomm.com
---
drivers/net/wireless/ath/ath9k/ath9k.h |1 -
1 files changed, 0 insertions(+), 1 deletions(-)
diff --git a/drivers/net/wireless/ath/ath9k/ath9k.h
b/drivers/net
From: Mohammed Shafi Shajakhan moham...@qca.qualcomm.com
*Remove all the checks that will be handled by cfg80211
based on the interface combination advertised. For instance,
driver supports at the maximum 8 beaconing interface, while
we advertise maximum 8 beaconing interface in the interface
From: Mohammed Shafi Shajakhan moham...@qca.qualcomm.com
Signed-off-by: Mohammed Shafi Shajakhan moham...@qca.qualcomm.com
---
drivers/net/wireless/ath/ath9k/htc_drv_main.c | 14 +-
1 files changed, 5 insertions(+), 9 deletions(-)
diff --git a/drivers/net/wireless/ath/ath9k
From: Mohammed Shafi Shajakhan moham...@qca.qualcomm.com
Enable BTCOEX for WB193(which seems to be the only supported
ath9k_htc BTCOEX chipset)only when it is enabled via modparam,
rather than enabling it by default.
Cc: Vivek Natarajan natar...@qualcomm.com
Signed-off-by: Mohammed Shafi
From: Mohammed Shafi Shajakhan moham...@qca.qualcomm.com
Before disabling BTCOEX in the h/w cancel all BTCOEX related
works. This is similar to the commit in ath9k(c32cdbd8)
ath9k: Stop the BTCOEX timers before disabling BTCOEX
Signed-off-by: Mohammed Shafi Shajakhan moham...@qca.qualcomm.com
From: Mohammed Shafi Shajakhan moham...@qca.qualcomm.com
Update the 'hw_timer_enabled' to 'false' wherever we are stopping
hardware generic timers, excecpt the case where we start them
again immediately. I will just test the case the generic hardware
timer is stopped again and again even though
wrote:
On Wed, Aug 1, 2012 at 11:28 PM, Mohammed Shafi Shajakhan
moham...@qca.qualcomm.com wrote:
From: Mohammed Shafi Shajakhan moham...@qca.qualcomm.com
AR is same as AR9485. The h/w
difference between them is quite insignificant,
Felix suggests only very few baseband features
may
From: Mohammed Shafi Shajakhan moham...@qca.qualcomm.com
AR is same as AR9485. The h/w
difference between them is quite insignificant,
Felix suggests only very few baseband features
may not be available in AR. The h/w code for
AR9485 is already present, so AR should
work fine
From: Mohammed Shafi Shajakhan moham...@qca.qualcomm.com
Add support for hardware WoW in ath9k. Magic-packet,
beacon loss triggers, deauth/disassoc patterns
(a special case of user pattern) are tested.
User pattern needs a bit of investigation
on parsing to appropriate 802.11 format.
we will do
From: Mohammed Shafi Shajakhan moham...@qca.qualcomm.com
*MAC WoW registers
back-off shift, MAC interrupt enable, magic packet enable,
pattern match enable, aifs, slot wait period, keep alive
frame failure count, beacon fail enable, beacon timeout,
keep alive timeout, auto keep alive disable
From: Mohammed Shafi Shajakhan moham...@qca.qualcomm.com
*add structures, macros and variables for WoW, so that the driver
can make use of it.
*maintain a list for user enabled patterns and masks
*track pattern slots for the hardware limitation on the
maximum number of patterns that can be stored
From: Mohammed Shafi Shajakhan moham...@qca.qualcomm.com
have seperate wow capability flags for
*basic wow support
*device capable of matching exact user defined pattern
or de-authentication/disassoc pattern
*device such AR9280 requires first four bytes for
all sort of patterns
Cc: Senthil
From: Mohammed Shafi Shajakhan moham...@qca.qualcomm.com
support WoW for all chipsets starting from AR9280, AR9285, AR9287,
AR9380, AR9382, AR9485, AR9462. Really all hardware may not support
WoW even though the flag is set and the WoW working depends on
your laptop, BIOS apart from the hardware
From: Mohammed Shafi Shajakhan moham...@qca.qualcomm.com
currently the code supports WoW triggers due to
*magic packet
*user defined patterns
*deauth and disassoc patterns
*disconnect - beacon miss, last beacon received timeout,
no ack for keeep alive frames.
Cc: Senthil Balasubramanian senth
From: Mohammed Shafi Shajakhan moham...@qca.qualcomm.com
for AR9002 family of chipsets and for WoW sleep, we reprogram
the SerDes so that the PLL and CHK REQ are both enabled. this
uses more power but in certain cases this is required as otherwise
WoW sleep is unstable and chip may disappear.
Cc
From: Mohammed Shafi Shajakhan moham...@qca.qualcomm.com
add a new file wow.c which takes care of the hardware code
for WoW.
*program the descriptors and data words to periodically
send Keep Alive Frames.
*program the user defined patterns/masks and pattern length
in the hardware registers
From: Mohammed Shafi Shajakhan moham...@qca.qualcomm.com
to help the developers and users to debug/know
whats happening with WoW
Cc: Senthil Balasubramanian senth...@qca.qualcomm.com
Cc: Rajkumar Manoharan rmano...@qca.qualcomm.com
Cc: vadi...@qca.qualcomm.com
Signed-off-by: Mohammed Shafi
From: Mohammed Shafi Shajakhan moham...@qca.qualcomm.com
add suspend/resume/set_wakeup callbacks to the driver
*suspend
- bail out only if all the conditions for configuring WoW.
is fine, currently multivif case is not handled
- check for associated state.
- map wow triggers from user space
From: Mohammed Shafi Shajakhan moham...@qca.qualcomm.com
Hardware needs to be AWAKE and should maintain association
with the AP to process WoW triggers any time
Cc: Senthil Balasubramanian senth...@qca.qualcomm.com
Cc: Rajkumar Manoharan rmano...@qca.qualcomm.com
Cc: vadi...@qca.qualcomm.com
Hi Julian,
On Monday 09 July 2012 04:57 AM, Julian Calaby wrote:
Hi Mohammed,
On Sat, Jul 7, 2012 at 12:39 AM, Mohammed Shafi Shajakhan
moham...@qca.qualcomm.com wrote:
From: Mohammed Shafi Shajakhan moham...@qca.qualcomm.com
We are doing MCI cleanup eventhough BTCOEX is not enabled
via
.
On Mon, Jun 25, 2012 at 07:42:49PM +0530, Mohammed Shafi Shajakhan wrote:
From: Mohammed Shafi Shajakhan moham...@qca.qualcomm.com
Add support for hardware WoW in ath9k. Magic-packet,
beacon loss triggers, deauth/disassoc patterns
(a special case of user pattern) are tested with
AR9485. User
From: Mohammed Shafi Shajakhan moham...@qca.qualcomm.com
We are doing MCI cleanup eventhough BTCOEX is not enabled
via module parameter. This means we do ath_mci_cleanup
though we skipped calling ath_mci_setup. Yet it does not
causes any issues now as we free the DMA buffer allocated
only when
From: Mohammed Shafi Shajakhan moham...@qca.qualcomm.com
Its safe to stop the BTCOEX timers 'period_timer' and
'no_stomp_timer' before disabling BTCOEX. These timers
can call ath9k_hw_btcoex_enable (or) change the BT
stomp type if they seem to be running after we had
called
From: Mohammed Shafi Shajakhan moham...@qca.qualcomm.com
We are doing MCI cleanup eventhough BTCOEX is not enabled
via module parameter. This means we do ath_mci_cleanup
though we skipped calling ath_mci_setup. Yet it does not
causes any issues now as we free the DMA buffer allocated
only when
From: Mohammed Shafi Shajakhan moham...@qca.qualcomm.com
We are doing MCI cleanup eventhough BTCOEX is not enabled
via module parameter. This means we do ath_mci_cleanup
though we skipped calling ath_mci_setup. Yet it does not
causes any issues now as we free the DMA buffer allocated
only when
On Tuesday 03 July 2012 08:47 PM, Mohammed Shafi Shajakhan wrote:
From: Mohammed Shafi Shajakhanmoham...@qca.qualcomm.com
We are doing MCI cleanup eventhough BTCOEX is not enabled
via module parameter. This means we do ath_mci_cleanup
though we skipped calling ath_mci_setup. Yet it does
From: Mohammed Shafi Shajakhan moham...@qca.qualcomm.com
Stop the BT timers 'period_timer' and 'no_stomp_timer'.
Both these timers can change the BT stomp type especially
for AR9462 chipsets eventhough we had called ath9k_hw_btcoex_disable.
ath9k_hw_btcoex_disable-ath9k_hw_btcoex_bt_stomp(ah
From: Mohammed Shafi Shajakhan moham...@qca.qualcomm.com
BTCOEX flags are set/cleared by atomic operations.
We got to do the same in ath9k_btcoex_timer_resume,
while clearing those BTCOEX flags.
Cc: Sujith Manoharan c_man...@qca.qualcomm.com
Signed-off-by: Mohammed Shafi Shajakhan moham
From: Mohammed Shafi Shajakhan moham...@qca.qualcomm.com
BTCOEX flags are set/cleared by atomic operations.
We got to do the same in ath9k_btcoex_timer_resume,
while clearing those BTCOEX flags.
Acked-by: Sujith Manoharan c_man...@qca.qualcomm.com
Signed-off-by: Mohammed Shafi Shajakhan moham
From: Mohammed Shafi Shajakhan moham...@qca.qualcomm.com
seems i got a message like this
ath: phy0: BT_Status_Update: is_link=0, linkId=2,
state=1, SEQ=-2085766476 initially.
Signed-off-by: Mohammed Shafi Shajakhan moham...@qca.qualcomm.com
---
drivers/net/wireless/ath/ath9k/mci.c |2 +-
1
From: Mohammed Shafi Shajakhan moham...@qca.qualcomm.com
ath9k_hw_mci_is_enabled wrapper also takes care of
ATH9K_HW_CAP_MCI being set for the AR9462 under test.
Signed-off-by: Mohammed Shafi Shajakhan moham...@qca.qualcomm.com
---
drivers/net/wireless/ath/ath9k/gpio.c |2 +-
1 files
Hi Felix,
On Wednesday 27 June 2012 08:18 PM, Felix Fietkau wrote:
On 2012-06-27 4:30 PM, Mohammed Shafi Shajakhan wrote:
From: Mohammed Shafi Shajakhanmoham...@qca.qualcomm.com
seems i got a message like this
ath: phy0: BT_Status_Update: is_link=0, linkId=2,
state=1, SEQ=-2085766476
On Wednesday 27 June 2012 08:30 PM, Mohammed Shafi Shajakhan wrote:
Hi Felix,
On Wednesday 27 June 2012 08:18 PM, Felix Fietkau wrote:
On 2012-06-27 4:30 PM, Mohammed Shafi Shajakhan wrote:
From: Mohammed Shafi Shajakhanmoham...@qca.qualcomm.com
seems i got a message like this
ath: phy0
Hi Johannes,
On Tuesday 26 June 2012 12:20 PM, Johannes Berg wrote:
On Tue, 2012-06-26 at 10:54 +0530, Mohammed Shafi Shajakhan wrote:
the user pattern needs bit more stuff, we need to convert it to our chip
specific format(ie proper 802.11 format), previously there was
a logic of duplicate
From: Mohammed Shafi Shajakhan moham...@qca.qualcomm.com
ath9k_hw_mci_is_enabled wrapper also takes care of
ATH9K_HW_CAP_MCI being set for the AR9462 under test.
Signed-off-by: Mohammed Shafi Shajakhan moham...@qca.qualcomm.com
---
drivers/net/wireless/ath/ath9k/gpio.c |2 +-
1 files
Hi John,
please wait, i will send a v3 for this. i missed something while
rebasing with the latest wireless-testing.
On Saturday 23 June 2012 09:29 PM, Mohammed Shafi Shajakhan wrote:
From: Mohammed Shafi Shajakhanmoham...@qca.qualcomm.com
add suspend/resume/set_wakeup callbacks
From: Mohammed Shafi Shajakhan moham...@qca.qualcomm.com
Add support for hardware WoW in ath9k. Magic-packet,
beacon loss triggers, deauth/disassoc patterns
(a special case of user pattern) are tested with
AR9485. User pattern needs a bit of investigation
on parsing to appropriate 802.11 format
From: Mohammed Shafi Shajakhan moham...@qca.qualcomm.com
*MAC WoW registers
back-off shift, MAC interrupt enable, magic packet enable,
pattern match enable, aifs, slot wait period, keep alive
frame failure count, beacon fail enable, beacon timeout,
keep alive timeout, auto keep alive disable
From: Mohammed Shafi Shajakhan moham...@qca.qualcomm.com
*add structures, macros and variables for WoW, so that the driver
can make use of it.
*maintain a list for user enabled patterns and masks
*track pattern slots for the hardware limitation on the
maximum number of patterns that can be stored
From: Mohammed Shafi Shajakhan moham...@qca.qualcomm.com
have seperate wow capability flags for
*basic wow support
*device capable of matching exact user defined pattern
or de-authentication/disassoc pattern
*device such AR9280 requires first four bytes for
all sort of patterns
Cc: Senthil
From: Mohammed Shafi Shajakhan moham...@qca.qualcomm.com
support WoW for all chipsets starting from AR9280, AR9285, AR9287,
AR9380, AR9382, AR9485, AR9462. Really all hardware may not support
WoW even though the flag is set and the WoW working depends on
your laptop, BIOS apart from the hardware
From: Mohammed Shafi Shajakhan moham...@qca.qualcomm.com
currently the code supports WoW triggers due to
*magic packet
*user defined patterns
*deauth and disassoc patterns
*disconnect - beacon miss, last beacon received timeout,
no ack for keeep alive frames.
we need to support other WoW offload
From: Mohammed Shafi Shajakhan moham...@qca.qualcomm.com
for AR9002 family of chipsets and for WoW sleep, we reprogram
the SerDes so that the PLL and CHK REQ are both enabled. this
uses more power but in certain cases this is required as otherwise
WoW sleep is unstable and chip may disappear.
Cc
From: Mohammed Shafi Shajakhan moham...@qca.qualcomm.com
add a new file wow.c which takes care of the hardware code
for WoW.
*program the descriptors and data words to periodically
send Keep Alive Frames.
*program the user defined patterns/masks and pattern length
in the hardware registers
From: Mohammed Shafi Shajakhan moham...@qca.qualcomm.com
to help the developers and users to debug/know
whats happening with WoW
Cc: Senthil Balasubramanian senth...@qca.qualcomm.com
Cc: Rajkumar Manoharan rmano...@qca.qualcomm.com
Cc: vadi...@qca.qualcomm.com
Signed-off-by: Mohammed Shafi
From: Mohammed Shafi Shajakhan moham...@qca.qualcomm.com
add suspend/resume/set_wakeup callbacks to the driver
*suspend
- bail out only if all the conditions for configuring WoW.
is fine, currently multivif case is not handled
- check for associated state.
- map wow triggers from user space
Hi Sujith,
On Monday 25 June 2012 10:49 PM, Sujith Manoharan wrote:
Mohammed Shafi Shajakhan wrote:
From: Mohammed Shafi Shajakhanmoham...@qca.qualcomm.com
*MAC WoW registers
back-off shift, MAC interrupt enable, magic packet enable,
pattern match enable, aifs, slot wait period, keep alive
Hi Sujith,
On Monday 25 June 2012 10:54 PM, Sujith Manoharan wrote:
Mohammed Shafi Shajakhan wrote:
From: Mohammed Shafi Shajakhanmoham...@qca.qualcomm.com
support WoW for all chipsets starting from AR9280, AR9285, AR9287,
AR9380, AR9382, AR9485, AR9462. Really all hardware may not support
Hi Sujith,
On Tuesday 26 June 2012 12:14 AM, Sujith Manoharan wrote:
Mohammed Shafi Shajakhan wrote:
+static void ath9k_hw_set_powermode_wow_sleep(struct ath_hw *ah)
+{
+struct ath_common *common = ath9k_hw_common(ah);
+
+REG_SET_BIT(ah, AR_STA_ID1, AR_STA_ID1_PWR_SAV
From: Mohammed Shafi Shajakhan moham...@qca.qualcomm.com
Add support for hardware WoW in ath9k. Magic-packet,
beacon loss triggers, deauth/disassoc patterns
(a special case of user pattern) are tested with
AR9485. User pattern needs a bit of
investigation on parsing to appropriate 802.11 format
From: Mohammed Shafi Shajakhan moham...@qca.qualcomm.com
*MAC WoW registers
back-off shift, MAC interrupt enable, magic packet enable,
pattern match enable, aifs, slot wait period, keep alive
frame failure count, beacon fail enable, beacon timeout,
keep alive timeout, auto keep alive disable
From: Mohammed Shafi Shajakhan moham...@qca.qualcomm.com
have seperate wow capability flags for
*basic wow support
*device capable of matching exact user defined pattern
or de-authentication/disassoc pattern
*device such AR9280 requires first four bytes for
all sort of patterns
Cc: Senthil
From: Mohammed Shafi Shajakhan moham...@qca.qualcomm.com
support WoW for all chipsets starting from AR9280, AR9285, AR9287,
AR9380, AR9382, AR9485, AR9462. Really all hardware may not support
WoW even though the flag is set and the WoW working depends on
your laptop, BIOS apart from the hardware
From: Mohammed Shafi Shajakhan moham...@qca.qualcomm.com
for AR9002 family of chipsets and for WoW sleep, we reprogram
the SerDes so that the PLL and CHK REQ are both enabled. this
uses more power but in certain cases this is required as otherwise
WoW sleep is unstable and chip may disappear.
Cc
From: Mohammed Shafi Shajakhan moham...@qca.qualcomm.com
Hardware needs to be AWAKE and should maintain association
with the AP to process WoW triggers any time
Cc: Senthil Balasubramanian senth...@qca.qualcomm.com
Cc: Rajkumar Manoharan rmano...@qca.qualcomm.com
Cc: vadi...@qca.qualcomm.com
From: Mohammed Shafi Shajakhan moham...@qca.qualcomm.com
Add support for hardware WoW in ath9k. Magic-packet,
beacon loss triggers, deauth/disassoc patterns
(a special case of user pattern) are tested with
AR9485, AR9280. User pattern needs a bit of
investigation on parsing to appropriate 802.11
From: Mohammed Shafi Shajakhan moham...@qca.qualcomm.com
*MAC WoW registers
back-off shift, MAC interrupt enable, magic packet enable,
pattern match enable, aifs, slot wait period, keep alive
frame failure count, beacon fail enable, beacon timeout,
keep alive timeout, auto keep alive disable
From: Mohammed Shafi Shajakhan moham...@qca.qualcomm.com
*add structures, macros and variables for WoW, so that the driver
can make use of it.
*maintain a list for user enabled patterns and masks
*track pattern slots for the hardware limitation on the
maximum number of patterns that can be stored
From: Mohammed Shafi Shajakhan moham...@qca.qualcomm.com
have seperate wow capability flags for
*basic wow support
*device capable of matching exact user defined pattern
or de-authentication/disassoc pattern
*device such AR9280 requires first four bytes for
all sort of patterns
Cc: Senthil
From: Mohammed Shafi Shajakhan moham...@qca.qualcomm.com
support WoW for all chipsets starting from AR9280, AR9285, AR9287,
AR9380, AR9382, AR9485, AR9462. Really all hardware may not support
WoW even though the flag is set and the WoW working depends on
your laptop, BIOS apart from the hardware
From: Mohammed Shafi Shajakhan moham...@qca.qualcomm.com
currently the code supports WoW triggers due to
*magic packet
*user defined patterns
*deauth and disassoc patterns
*disconnect - beacon miss, last beacon received timeout,
no ack for keeep alive frames.
we need to support other WoW offload
From: Mohammed Shafi Shajakhan moham...@qca.qualcomm.com
for AR9002 family of chipsets and for WoW sleep, we reprogram
the SerDes so that the PLL and CHK REQ are both enabled. this
uses more power but in certain cases this is required as otherwise
WoW sleep is unstable and chip may disappear.
Cc
From: Mohammed Shafi Shajakhan moham...@qca.qualcomm.com
to help the developers and users to debug/know
whats happening with WoW
Cc: Senthil Balasubramanian senth...@qca.qualcomm.com
Cc: Rajkumar Manoharan rmano...@qca.qualcomm.com
Cc: vadi...@qca.qualcomm.com
Tested-by: Mohammed Shafi Shajakhan
From: Mohammed Shafi Shajakhan moham...@qca.qualcomm.com
add suspend/resume/set_wakeup callbacks to the driver
*suspend
- bail out only if all the conditions for configuring WoW
is fine, currently multivif case is not handled
- check for associated state
- map wow triggers from user space
From: Mohammed Shafi Shajakhan moham...@qca.qualcomm.com
Cc: Senthil Balasubramanian senth...@qca.qualcomm.com
Cc: Rajkumar Manoharan rmano...@qca.qualcomm.com
Cc: vadi...@qca.qualcomm.com
Tested-by: Mohammed Shafi Shajakhan moham...@qca.qualcomm.com
Signed-off-by: Mohammed Shafi Shajakhan moham
Hi Raj,
On Tuesday 19 June 2012 11:08 PM, Rajkumar Manoharan wrote:
On Tue, Jun 19, 2012 at 09:17:22PM +0530, Mohammed Shafi Shajakhan wrote:
From: Mohammed Shafi Shajakhanmoham...@qca.qualcomm.com
*add structures, macros and variables for WoW, so that the driver
can make use
On Tuesday 19 June 2012 10:50 PM, Rajkumar Manoharan wrote:
On Tue, Jun 19, 2012 at 09:17:23PM +0530, Mohammed Shafi Shajakhan wrote:
From: Mohammed Shafi Shajakhanmoham...@qca.qualcomm.com
have seperate wow capability flags for
*basic wow support
*device capable of matching exact user
Hi Julian,
On Wed, Jun 20, 2012 at 1:47 AM, Mohammed Shafi Shajakhan
moham...@qca.qualcomm.com wrote:
From: Mohammed Shafi Shajakhanmoham...@qca.qualcomm.com
currently the code supports WoW triggers due to
*magic packet
*user defined patterns
*deauth and disassoc patterns
*disconnect
Hi Raj,
On Tuesday 19 June 2012 11:20 PM, Rajkumar Manoharan wrote:
On Tue, Jun 19, 2012 at 09:17:27PM +0530, Mohammed Shafi Shajakhan wrote:
From: Mohammed Shafi Shajakhanmoham...@qca.qualcomm.com
add a new file wow.c which takes care of the hardware code
for WoW.
[...]
---
3 files
From: Mohammed Shafi Shajakhan moham...@qca.qualcomm.com
Add support for hardware WoW in ath9k. Magic-packet,
beacon loss triggers are tested with AR9485, AR9280.
Hardware code was cleaned up addressing Rajkumar's
comments. User pattern needs a bit of investigation
on parsing to appropriate
From: Mohammed Shafi Shajakhan moham...@qca.qualcomm.com
*MAC WoW registers
back-off shift, MAC interrupt enable, magic packet enable,
pattern match enable, aifs, slot wait period, keep alive
frame failure count, beacon fail enable, beacon timeout,
keep alive timeout, auto keep alive disable
From: Mohammed Shafi Shajakhan moham...@qca.qualcomm.com
*add structures, macros and variables for WoW, so that the driver
can make use of it.
*maintain a list for user enabled patterns and masks
*track pattern slots for the hardware limitation on the
maximum number of patterns that can be stored
From: Mohammed Shafi Shajakhan moham...@qca.qualcomm.com
have seperate wow capability flags for
*basic wow support
*device capable of matching exact user defined pattern
or de-authentication/disassoc pattern
*device such AR9280 requires first four bytes for
all sort of patterns
Signed-off
From: Mohammed Shafi Shajakhan moham...@qca.qualcomm.com
support WoW for all chipsets starting from AR9280, AR9285, AR9287,
AR9380, AR9382, AR9485, AR9462. Really all hardware may not support
WoW even though the flag is set and the WoW working depends on
your laptop, BIOS apart from the hardware
1 - 100 of 222 matches
Mail list logo
