From: Kalle Valo <kvalo@qca.qualcomm.com>
To: <rmani@qca.qualcomm.com>
Cc: <linux-wireless@vger.kernel.org>, <ath6kl-devel@qualcomm.com>
Subject: Re: [PATCH] ath6kl: Add provision to define suspend policy in disconnected state.
Date: Mon, 27 Feb 2012 20:12:15 +0200 [thread overview]
Message-ID: <4F4BC77F.2010400@qca.qualcomm.com> (raw)
In-Reply-To: <1329308528-2925-1-git-send-email-rmani@qca.qualcomm.com>
On 02/15/2012 02:22 PM, rmani@qca.qualcomm.com wrote:
> From: Raja Mani <rmani@qca.qualcomm.com>
>
> It gives flexibility to the user to define suspend policy
> when the suspend mode is set to WOW and the device is in
> disconnected state at the time of suspend.
>
> Some bits (bit 4 to 7) of existing mod parameter suspend_mode
> is used for that purpose. There is no change in the existing
> way of defining suspend mode.
>
> To force cut power:
> suspend_mode=0x1
>
> To force deep sleep:
> suspend_mode=0x2
>
> To force wow (deep sleep is the default mode
> in disconnected state):
> suspend_mode=0x3
>
> To force wow in connected state and cut power
> in disconnected state:
> suspend_mode=0x13
What's the difference between values 0x3 and 0x13? It wasn't clear for
me from the description and neither from the code.
> To force wow in connected state and deep sleep
> in disconnected state:
> suspend_mode=0x23
I'm not sure if adding bits to suspend_mode is the best way. To me
adding a separate parameter wow_mode looks easier from user's point of
view. What do you think?
And if you add a new module paratemer please use charp type so that can
use strings like 'deepsleep' and 'cutpower'. I wish that we had used
that already with suspend_mode but it's too late now :(
> --- a/drivers/net/wireless/ath/ath6kl/cfg80211.c
> +++ b/drivers/net/wireless/ath/ath6kl/cfg80211.c
> @@ -2063,7 +2063,6 @@ int ath6kl_cfg80211_suspend(struct ath6kl *ar,
>
> ret = ath6kl_wow_suspend(ar, wow);
> if (ret) {
> - ath6kl_err("wow suspend failed: %d\n", ret);
> ar->state = prev_state;
> return ret;
> }
Please convert this to a debug message, maybe using the suspend level.
It might be useful when debugging something.
> diff --git a/drivers/net/wireless/ath/ath6kl/core.c b/drivers/net/wireless/ath/ath6kl/core.c
> index c4926cf..37c92a1 100644
> --- a/drivers/net/wireless/ath/ath6kl/core.c
> +++ b/drivers/net/wireless/ath/ath6kl/core.c
> @@ -41,6 +41,7 @@ int ath6kl_core_init(struct ath6kl *ar)
> {
> struct ath6kl_bmi_target_info targ_info;
> struct net_device *ndev;
> + u16 pri_suspend_mode, wow2_suspend_mode;
Why the number two? Why not just wow_suspend_mode?
Kalle
next prev parent reply other threads:[~2012-02-27 18:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-15 12:22 [PATCH] ath6kl: Add provision to define suspend policy in disconnected state rmani
2012-02-27 18:12 ` Kalle Valo [this message]
2012-02-29 6:48 ` Raja Mani
2012-03-01 19:30 ` Kalle Valo
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=4F4BC77F.2010400@qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath6kl-devel@qualcomm.com \
--cc=linux-wireless@vger.kernel.org \
--cc=rmani@qca.qualcomm.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.