mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@suse.cz>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: kernel list <linux-kernel@vger.kernel.org>,
	Ingo Molnar <mingo@elte.hu>, Dave Jones <davej@codemonkey.org.uk>,
	Andi Kleen <andi@firstfloor.org>,
	"Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: amd64-agp: resume but too late?
Date: Wed, 28 May 2008 12:42:50 +0200	[thread overview]
Message-ID: <20080528104250.GC5728@elf.ucw.cz> (raw)
In-Reply-To: <alpine.LFD.1.10.0805271415160.3295@apollo.tec.linutronix.de>

On Tue 2008-05-27 14:18:19, Thomas Gleixner wrote:
> On Mon, 26 May 2008, Pavel Machek wrote:
> > Hi!
> > 
> > I don't get it:
> > 
> > --- a/drivers/char/agp/amd64-agp.c
> > +++ b/drivers/char/agp/amd64-agp.c
> > @@ -549,6 +549,8 @@ static int agp_amd64_suspend(struct pci_
> >         return 0;
> >  }
> >  
> > +/* FIXME: this is strange; we enable iommu translation here, but that
> > + * may be too late, no? */
> >  static int agp_amd64_resume(struct pci_dev *pdev)
> >  {
> >         pci_set_power_state(pdev, PCI_D0);
> > 
> > ...but resume is normal pci device, so other devices may be resumed
> > before this one, and already depend on iommu running...
> > 
> > How is this supposed to work? Should agp_amd64_resume be called from
> > sysdev or something like that?
> 
> Hmm, you sent a patch some days ago to change it to
> suspend_late/resume_early. Is the discussion resolved about that ?

I'm not aware of such patch. I don't think I sent it.

I did add suspend/resume support to pci-gart_64.c , which is
confusingly similar code. That patch needs a bit more testing, and
some de-uglyfication.
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

      reply	other threads:[~2008-05-28 10:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-26 18:29 Pavel Machek
2008-05-27 12:18 ` Thomas Gleixner
2008-05-28 10:42   ` Pavel Machek [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=20080528104250.GC5728@elf.ucw.cz \
    --to=pavel@suse.cz \
    --cc=andi@firstfloor.org \
    --cc=davej@codemonkey.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rjw@sisk.pl \
    --cc=tglx@linutronix.de \
    /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®