All of lore.kernel.org
 help / color / mirror / Atom feed
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 v3 0/4] Allow the user to define suspend mode
Date: Mon, 30 Jan 2012 21:37:52 +0200	[thread overview]
Message-ID: <4F26F190.6060902@qca.qualcomm.com> (raw)
In-Reply-To: <1327923792-16408-1-git-send-email-rmani@qca.qualcomm.com>

On 01/30/2012 01:43 PM, rmani@qca.qualcomm.com wrote:
> From: Raja Mani <rmani@qca.qualcomm.com>
> 
> This series of patch enables the user to specify the suspend mode 
> via module parameter (suspend_mode) while doing insmod of the driver.
> 
>    To select Cut Power mode:
>       insmod ath6kl_sdio.ko suspend_mode = 1
> 
>    To select Deep Sleep mode:
>       insmod ath6kl_sdio.ko suspend_mode = 2
> 
>    To select WOW suspend mode:
>       insmod ath6kl_sdio.ko suspend_mode = 3
> 
> Existing module param 'suspend_cutpower' variable is renamed to 
> 'suspend_mode' for this purspose.
> 
> Additionally, If the user doesn't provide any WOW patterns, 
> the default WOW patterns will be configured while going to
> WOW suspend mode.

Thanks, all four applied.

Kalle

      parent reply	other threads:[~2012-01-30 19:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-30 11:43 [PATCH v3 0/4] Allow the user to define suspend mode rmani
2012-01-30 11:43 ` [PATCH v3 1/4] ath6kl: Re-architect suspend mode handling in ath6kl_sdio_suspend rmani
2012-01-30 11:43 ` [PATCH v3 2/4] ath6kl: Configure WOW patterns while going to wow_suspend rmani
2012-01-30 11:43 ` [PATCH v3 3/4] ath6kl: Wait for host sleep mode cmd processed event during WOW suspend rmani
2012-01-30 11:43 ` [PATCH v3 4/4] ath6kl: Return a proper error code when not in connected state rmani
2012-01-30 19:37 ` Kalle Valo [this message]

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=4F26F190.6060902@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.