mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: "Zhu, Yi" <yi.zhu@intel.com>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org, linux-pm@lists.osdl.org
Subject: Re: [linux-pm] [PATCH] make pm_suspend_disk suspend/resume sysdev and dpm_off_irq
Date: Thu, 25 Nov 2004 12:28:01 +0100	[thread overview]
Message-ID: <20041125112801.GB1014@elf.ucw.cz> (raw)
In-Reply-To: <3ACA40606221794F80A5670F0AF15F8403BD586A@pdsmsx403>

Hi!

> >> This patch makes the new swsusp code ( pm_suspend_disk since
> >> 2.6.9-rc3) call suspend/resume functions for sysdev and devices in
> >> dpm_off_irq list. Otherwise, PCI link device in the system won't
> >> provide correct interrupt for PCI devices during resume.
> > 
> > I do not think this is right approach; you enable interrupts
> > then disable that again, potentially without interrupt controller
> > being initialized. 
> > 
> > This should be better patch:
> 
> Agreed. Your patch solves the bug. But do you plan to deal with the 
> devices in dpm_off_irq list?

Ouch, okay... Calling irq-off phase of device_suspend() is not
intuitive at all and I hate that -EAGAIN idea.

...ouch, wait, it is less messy than I expected. I have no business
calling sysdev_suspend directly.

I'll test the patch and post it in the next message.
								Pavel
-- 
People were complaining that M$ turns users into beta-testers...
...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!

  reply	other threads:[~2004-11-27  4:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-25  4:59 Zhu, Yi
2004-11-25 11:28 ` Pavel Machek [this message]
2004-11-25 11:34 ` Pavel Machek
  -- strict thread matches above, loose matches on Subject: below --
2004-11-26  2:38 Zhu, Yi
2004-11-26 11:52 ` Pavel Machek
2004-11-24 10:18 Zhu, Yi
2004-11-24 10:25 ` [linux-pm] " Pavel Machek

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=20041125112801.GB1014@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@lists.osdl.org \
    --cc=yi.zhu@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®