From: Greg KH <greg@kroah.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Andrew Morton <akpm@osdl.org>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Fw: [PATCH] Fix e100 suspend/resume w/ 2.6.10-rc1 and above (due to pci_save_state change)
Date: Thu, 28 Oct 2004 09:29:56 -0500 [thread overview]
Message-ID: <20041028142956.GA9400@kroah.com> (raw)
In-Reply-To: <41810066.5000705@pobox.com>
On Thu, Oct 28, 2004 at 10:21:26AM -0400, Jeff Garzik wrote:
> Andrew Morton wrote:
> >
> >Begin forwarded message:
> >
> >Date: Thu, 28 Oct 2004 17:34:19 +0800 (CST)
> >From: "Zhu, Yi" <yi.zhu@intel.com>
> >To: Andrew Morton <akpm@osdl.org>, Linux Kernel Mailing List
> ><linux-kernel@vger.kernel.org>
> >Subject: [PATCH] Fix e100 suspend/resume w/ 2.6.10-rc1 and above (due to
> >pci_save_state change)
> >
> >
> >
> >Hi,
> >
> >Recent 2.6.10-rc1 merged the pci_save_state change. This prevents some
> >drivers from working with suspend/resume. The reason is the
> >pci_save_state() called in driver's ->suspend doesn't take effect any more,
> >since pci bus ->suspend will override it. And the two states might be
> >different in some drivers, i.e. e100. I don't know if there are other
> >drivers also suffer from it.
> >
> >Thanks,
> >-yi
> >
> >
> >Signed-off-by: Zhu Yi <yi.zhu@intel.com>
> >
> >--- /tmp/e100.c 2004-10-28 16:31:41.000000000 +0800
> >+++ drivers/net/e100.c 2004-10-28 16:33:14.000000000 +0800
> >@@ -2309,9 +2309,7 @@ static int e100_suspend(struct pci_dev *
> >
> >- pci_save_state(pdev);
> > pci_enable_wake(pdev, state, nic->flags & (wol_magic |
> > e100_asf(nic)));
> >- pci_disable_device(pdev);
> > pci_set_power_state(pdev, state);
>
>
> I'm waiting for Greg to respond to the serious concerns raised by
> BenH[1] and me[2].
>
> AFAICS, Greg has broken the standard Linux "driver knows it, driver does
> it" model.
Huh? How did changing the pci_save_state() api change anything? I
didn't change the pci core any, just made it easier to not have to
specify the storage location of the memory to save everything off on.
> [1] http://marc.theaimsgroup.com/?l=linux-kernel&m=109867742404637&w=2
> [2] http://marc.theaimsgroup.com/?l=linux-kernel&m=109868495426108&w=2
I'm still on the road (all week long) and will try to get to the above
messages soon...
thanks,
greg k-h
next prev parent reply other threads:[~2004-10-28 14:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20041028025536.5d9b1067.akpm@osdl.org>
2004-10-28 14:21 ` Fw: [PATCH] Fix e100 suspend/resume w/ 2.6.10-rc1 and above (due to pci_save_state change) Jeff Garzik
2004-10-28 14:29 ` Greg KH [this message]
2004-10-28 14:59 ` Jeff Garzik
2004-10-28 16:06 ` Greg KH
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=20041028142956.GA9400@kroah.com \
--to=greg@kroah.com \
--cc=akpm@osdl.org \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.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 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.