From: Ming Lei <tom.leiming@gmail.com>
To: reinette chatre <reinette.chatre@intel.com>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
Linux-kernel <linux-kernel@vger.kernel.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [possible BUG] PM suspend warning in 2.6.29-rc3-00227-gf1dd849
Date: Tue, 3 Feb 2009 21:58:19 +0800 [thread overview]
Message-ID: <d82e647a0902030558n262eaf35r233541d3e63e4df8@mail.gmail.com> (raw)
In-Reply-To: <1233600555.2411.158.camel@rc-desk>
2009/2/3 reinette chatre <reinette.chatre@intel.com>:
> Ming,
>
> On Mon, 2009-02-02 at 06:14 -0800, Ming Lei wrote:
>> After applying your patch, following is the dmesg output, so it is the
>> iwl3945 driver that does not save pci state.
>
> Could you please test with the patch below?
reinette,
The previous warning during pm suspending does disappear after
applying your patch.
Thanks!
>
> Thank you
>
> diff --git a/drivers/net/wireless/iwlwifi/iwl3945-base.c
> b/drivers/net/wireless/iwlwifi/iwl3945-base.c
> index 95d0198..5b44d32 100644
> --- a/drivers/net/wireless/iwlwifi/iwl3945-base.c
> +++ b/drivers/net/wireless/iwlwifi/iwl3945-base.c
> @@ -8143,6 +8143,7 @@ static int iwl3945_pci_suspend(struct pci_dev
> *pdev, pm_message_t state)
> priv->is_open = 1;
> }
>
> + pci_save_state(pdev);
> pci_set_power_state(pdev, PCI_D3hot);
>
> return 0;
> @@ -8153,6 +8154,7 @@ static int iwl3945_pci_resume(struct pci_dev
> *pdev)
> struct iwl3945_priv *priv = pci_get_drvdata(pdev);
>
> pci_set_power_state(pdev, PCI_D0);
> + pci_restore_state(pdev);
>
> if (priv->is_open)
> iwl3945_mac_start(priv->hw);
>
>
>
>
>
--
Lei Ming
prev parent reply other threads:[~2009-02-03 13:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <d82e647a0902010634o1b4e4075m7d38365f605d3c31@mail.gmail.com>
[not found] ` <200902012208.40758.rjw@sisk.pl>
2009-02-02 14:14 ` [possible BUG] PM suspend warning in 2.6.29-rc3-00227-gf1dd849 Ming Lei
2009-02-02 18:49 ` reinette chatre
2009-02-03 13:58 ` Ming Lei [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=d82e647a0902030558n262eaf35r233541d3e63e4df8@mail.gmail.com \
--to=tom.leiming@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=reinette.chatre@intel.com \
--cc=rjw@sisk.pl \
/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