From: Mohammed Shafi Shajakhan <mohammed@qca.qualcomm.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] [PATCH v3 04/10] ath9k_hw: advertise WoW support for capable chipsets
Date: Tue, 26 Jun 2012 10:04:19 +0530 [thread overview]
Message-ID: <4FE93BCB.2080400@qca.qualcomm.com> (raw)
In-Reply-To: <20456.40631.937743.311973@gargle.gargle.HOWL>
Hi Sujith,
On Monday 25 June 2012 10:54 PM, Sujith Manoharan wrote:
> Mohammed Shafi Shajakhan wrote:
>> From: Mohammed Shafi Shajakhan<mohammed@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.
>>
>> Cc: Senthil Balasubramanian<senthilb@qca.qualcomm.com>
>> Cc: Rajkumar Manoharan<rmanohar@qca.qualcomm.com>
>> Cc: vadivel at qca.qualcomm.com
>> Signed-off-by: Luis R. Rodriguez<mcgrof@qca.qualcomm.com>
>> Signed-off-by: Mohammed Shafi Shajakhan<mohammed@qca.qualcomm.com>
>> ---
>> drivers/net/wireless/ath/ath9k/hw.c | 8 ++++++++
>> 1 files changed, 8 insertions(+), 0 deletions(-)
>>
>> diff --git a/drivers/net/wireless/ath/ath9k/hw.c b/drivers/net/wireless/ath/ath9k/hw.c
>> index a42c26f..041d797 100644
>> --- a/drivers/net/wireless/ath/ath9k/hw.c
>> +++ b/drivers/net/wireless/ath/ath9k/hw.c
>> @@ -2572,6 +2572,14 @@ int ath9k_hw_fill_cap_info(struct ath_hw *ah)
>> }
>>
>>
>> + if (AR_SREV_9280_20_OR_LATER(ah)) {
>> + pCap->hw_caps |= ATH9K_HW_WOW_DEVICE_CAPABLE |
>> + ATH9K_HW_WOW_PATTERN_MATCH_EXACT;
>> +
>> + if (AR_SREV_9280(ah))
>> + pCap->hw_caps |= ATH9K_HW_WOW_PATTERN_MATCH_DWORD;
>> + }
>> +
>
> I don't think this is a good idea - please enable WoW only for cards that
> we have actually tested.
>
I had tested it in quite a few of cards like AR9280, AR9285,AR9485 with
wow enabled. Further the hardware was generic, with only quite a few
changes needed between AR9002 and AR9003. thank you.
--
thanks,
shafi
next prev parent reply other threads:[~2012-06-26 4:34 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-25 14:12 [ath9k-devel] [PATCH v3 00/10] Add support for WOW in ath9k Mohammed Shafi Shajakhan
2012-06-25 14:12 ` [ath9k-devel] [PATCH v3 01/10] ath9k_hw: Add register definitions for WoW support Mohammed Shafi Shajakhan
2012-06-25 17:19 ` Sujith Manoharan
2012-06-26 4:28 ` Mohammed Shafi Shajakhan
2012-07-07 11:46 ` Mohammed Shafi
2012-06-25 14:12 ` [ath9k-devel] [PATCH v3 02/10] ath9k: Add definitions and structures to support WoW Mohammed Shafi Shajakhan
2012-06-25 14:12 ` [ath9k-devel] [PATCH v3 03/10] ath9k_hw: Add WoW hardware capability flags Mohammed Shafi Shajakhan
2012-06-25 14:12 ` [ath9k-devel] [PATCH v3 04/10] ath9k_hw: advertise WoW support for capable chipsets Mohammed Shafi Shajakhan
2012-06-25 17:24 ` Sujith Manoharan
2012-06-26 4:34 ` Mohammed Shafi Shajakhan [this message]
2012-06-25 14:12 ` [ath9k-devel] [PATCH v3 05/10] ath9k: advertise supported WoW flags to upper layer Mohammed Shafi Shajakhan
2012-06-25 14:12 ` [ath9k-devel] [PATCH v3 06/10] ath9k_hw: INI changes for WoW for AR9002 chipsets Mohammed Shafi Shajakhan
2012-06-25 14:12 ` [ath9k-devel] [PATCH v3 07/10] ath9k_hw: Add hardware code for WoW Mohammed Shafi Shajakhan
2012-06-25 18:44 ` Sujith Manoharan
2012-06-26 4:55 ` Mohammed Shafi Shajakhan
2012-06-25 14:12 ` [ath9k-devel] [PATCH v3 08/10] ath: Add Wake-on-Wireless debug mask Mohammed Shafi Shajakhan
2012-06-25 14:12 ` [ath9k-devel] [PATCH v3 09/10] ath9k: Add WoW related mac80211 callbacks Mohammed Shafi Shajakhan
2012-06-25 19:21 ` Sujith Manoharan
2012-06-26 5:24 ` Mohammed Shafi Shajakhan
2012-06-26 6:50 ` Johannes Berg
2012-06-26 7:28 ` Mohammed Shafi Shajakhan
2012-06-25 14:12 ` [ath9k-devel] [PATCH v3 10/10] ath9k: do not disable hardware while wow is enabled Mohammed Shafi Shajakhan
2012-07-06 19:35 ` [ath9k-devel] [PATCH v3 00/10] Add support for WOW in ath9k John W. Linville
2012-07-07 9:30 ` Mohammed Shafi Shajakhan
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=4FE93BCB.2080400@qca.qualcomm.com \
--to=mohammed@qca.qualcomm.com \
--cc=ath9k-devel@lists.ath9k.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 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).