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 dup
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 patterns before programming to HW, where a list in
> the driver wa
Hi Sujith,
On Tuesday 26 June 2012 12:51 AM, Sujith Manoharan wrote:
> Mohammed Shafi Shajakhan wrote:
>> +#ifdef CONFIG_PM_SLEEP
>> +
>> +void ath_wow_cleanup(struct ath_softc *sc)
>> +{
>> +struct ath9k_wow_info *wow_info =&sc->wow_info;
>> +struct ath9k_wow_pattern *wow_pattern = NULL,
Mohammed Shafi Shajakhan wrote:
> +#ifdef CONFIG_PM_SLEEP
> +
> +void ath_wow_cleanup(struct ath_softc *sc)
> +{
> + struct ath9k_wow_info *wow_info = &sc->wow_info;
> + struct ath9k_wow_pattern *wow_pattern = NULL, *tmp;
> +
> + if (!(sc->wow_enabled & AH_WOW_USER_PATTERN_EN))
> +
From: Mohammed Shafi Shajakhan
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 data.
- add deauth/disassoc
