From: Greg KH <greg-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
To: Shaohua Li <shaohua.li-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: acpi-dev
<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>,
Len <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Subject: Re: [PATCH]Disable ACPI PCI link device if no PCI device uses it - takes 2
Date: Wed, 27 Jul 2005 22:25:08 -0700 [thread overview]
Message-ID: <20050728052508.GC13585@kroah.com> (raw)
In-Reply-To: <1122364343.7106.3.camel-ECwVeV2eNyQD0+JXs3kMbRL4W9x8LtSr@public.gmane.org>
On Tue, Jul 26, 2005 at 03:52:23PM +0800, Shaohua Li wrote:
> Hi,
> Looks like people agree device drivers should call
> free_irq/pci_disable_irq at suspend time per the OLS report. This patch
> tries to disable pci link device if no PCI device is using it, which is
> one goal of pci driver calls pci_disable_irq. This patch also warns
> users if some drivers don't call pci_disable_irq at suspend time. Next
> step we will implement acpi_unregister_gsi for x86/x86_64, so we can
> automically mask ioapic/pic if no device is using them. And in the same
> way, alarm users if driver doesn't call free_irq at suspend time.
> Greg, is the PCI part ok for you? It just has very small changes in PCI
> part.
Looks ok to me.
thanks,
greg k-h
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO September
19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
prev parent reply other threads:[~2005-07-28 5:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-26 7:52 [PATCH]Disable ACPI PCI link device if no PCI device uses it - takes 2 Shaohua Li
[not found] ` <1122364343.7106.3.camel-ECwVeV2eNyQD0+JXs3kMbRL4W9x8LtSr@public.gmane.org>
2005-07-28 5:25 ` Greg KH [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=20050728052508.GC13585@kroah.com \
--to=greg-u8xffu+wg4eavxtiumwx3w@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=shaohua.li-ral2JQCrhuEAvxtiuMwx3w@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 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.