public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Li Shaohua <shaohua.li-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
To: Pavel Machek <pavel-AlSwsSmVLrQ@public.gmane.org>
Cc: ACPI-DEV
	<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>,
	Len Brown <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
	Nigel Cunningham
	<ncunningham-jjFNsPSvq+iXDw4h08c5KA@public.gmane.org>
Subject: Re: [PATCH 0/3]making ACPICA safe for suspend/resume - take 2
Date: Thu, 27 Jan 2005 09:01:22 +0800	[thread overview]
Message-ID: <1106787682.9062.7.camel@sli10-desk.sh.intel.com> (raw)
In-Reply-To: <20050126115804.GC10264-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>

On Wed, 2005-01-26 at 19:58, Pavel Machek wrote:
> > > > The patches are designed to solve the issue of making call to ACPICA
> > > > safe for suspend/resume time. Please see the detail in
> > > > http://sourceforge.net/mailarchive/forum.php?thread_id=6378210&forum_id=6102
> > > > The new patches remove PCI link device resume code and let PCI device
> > > > driver resume code indirectly reconfigure Link's IRQ (call
> > > > pci_enable_device), so we will haven't an issue of invoking ACPICA with
> > > > interrupt disabled. This also works for suspend to disk case. After this
> > > > we only need to guarantee there is enough free memory for S3. One
> > > > problem of the idea is we must fix many PCI drivers, but it's ok to me.
> > > 
> > > Well, having to modify all the drivers should mean "this should be
> > > merged after 2.6.11" (I'm in process of converting all the drivers to
> > > pm_message_t, and would prefer another set of "touch all drivers"
> > > changes not to interfere).
> > There isn't conflict between the pm_message_t converting and adding
> > pci_enable/disable_device to me. It would be better we do them in the
> > meantime, so we don't require another round of change. If so, I can help
> > doing the converting also.
> 
> Well, when something breaks, we will not know "what was it". Plus, it
> is going to be quite an intrusive change and we are already at -rc2.
Ok, that makes sense, though I think pci_enable/disable_device hasn't
impact.

> If driver can do pci_enable_device to solve "ACPICA with interrupts
> isabled" problem, 
This is just one part. pci_disable_device will disable bus master and
possibly do more, I think it's much safer.

> why can't be the same done in code that calls
> device's suspend() method from PCI code? That would be smaller change,
> and we would not duplicate a lot of code.
This is good for pci_disable_device (suspend), but not for resume. We
must restore PCI config and then call pci_enable_device.

Thanks,
Shaohua



-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl

  parent reply	other threads:[~2005-01-27  1:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-21  7:48 [PATCH 0/3]making ACPICA safe for suspend/resume - take 2 Li Shaohua
     [not found] ` <1106293737.19407.60.camel-U5EdaLXB8smDugQYiPIPGdh3ngVCH38I@public.gmane.org>
2005-01-21  9:52   ` Pavel Machek
     [not found]     ` <20050121095219.GA18373-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
2005-01-26  1:53       ` Li Shaohua
     [not found]         ` <1106704432.5756.11.camel-U5EdaLXB8smDugQYiPIPGdh3ngVCH38I@public.gmane.org>
2005-01-26 11:58           ` Pavel Machek
     [not found]             ` <20050126115804.GC10264-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
2005-01-27  1:01               ` Li Shaohua [this message]
     [not found]                 ` <1106787682.9062.7.camel-U5EdaLXB8smDugQYiPIPGdh3ngVCH38I@public.gmane.org>
2005-01-27  8:03                   ` Pavel Machek
     [not found]                     ` <20050127080313.GA5749-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
2005-01-27  9:13                       ` Li Shaohua

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=1106787682.9062.7.camel@sli10-desk.sh.intel.com \
    --to=shaohua.li-ral2jqcrhueavxtiumwx3w@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    --cc=ncunningham-jjFNsPSvq+iXDw4h08c5KA@public.gmane.org \
    --cc=pavel-AlSwsSmVLrQ@public.gmane.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox