public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Shaohua Li <shaohua.li@intel.com>
Cc: Greg KH <gregkh@suse.de>, linux acpi <linux-acpi@vger.kernel.org>,
	linux-pci <linux-pci@atrey.karlin.mff.cuni.cz>,
	Len Brown <lenb@kernel.org>
Subject: Re: [RFC] fix asus_hides_smbus_lpc_ich6() for resume
Date: Fri, 14 Mar 2008 15:37:49 +0100	[thread overview]
Message-ID: <200803141537.50589.rjw@sisk.pl> (raw)
In-Reply-To: <1205481045.16349.1.camel@sli10-desk.sh.intel.com>

On Friday, 14 of March 2008, Shaohua Li wrote:
> 
> On Thu, 2008-03-13 at 21:44 -0700, Greg KH wrote:
> > On Fri, Mar 14, 2008 at 11:49:09AM +0800, Shaohua Li wrote:
> > > diff --git a/include/linux/pci.h b/include/linux/pci.h
> > > index 9010f54..821ad02 100644
> > > --- a/include/linux/pci.h
> > > +++ b/include/linux/pci.h
> > > @@ -1016,6 +1016,8 @@ enum pci_fixup_pass {
> > >  	pci_fixup_final,	/* Final phase of device fixups */
> > >  	pci_fixup_enable,	/* pci_enable_device() time */
> > >  	pci_fixup_resume,	/* pci_enable_device() time */
> > > +	pci_fixup_suspend,
> > > +	pci_fixup_resume_later,
> > 
> > Please document when these quirks are run.
> will do if you think the method is correct.
> 
> > And why "_later"?  What's wrong with the normal resume time?
> pci_fixup_resume is called in pci_device_resume_earily(), which is
> called with interrupt disable, so I added a new one which is called at
> pci_device_resume(), this routine is called with interrupt enabled.

Is the pci_fixup_resume thing used at all?  If it is, how can I check who uses
it?

Thanks,
Rafael

  reply	other threads:[~2008-03-14 14:38 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-14  3:49 [RFC] fix asus_hides_smbus_lpc_ich6() for resume Shaohua Li
2008-03-14  4:44 ` Greg KH
2008-03-14  7:50   ` Shaohua Li
2008-03-14 14:37     ` Rafael J. Wysocki [this message]
2008-03-14 17:15       ` Jesse Barnes
2008-03-14 21:03         ` Rafael J. Wysocki
2008-03-17  1:15           ` Shaohua Li
2008-03-17 16:26             ` Rafael J. Wysocki
2008-03-18  3:11               ` Shaohua Li
2008-04-16 17:30                 ` Rafael J. Wysocki
2008-04-17  2:16                   ` Shaohua Li
2008-03-14 12:26   ` Matthew Wilcox
2008-03-14 14:34     ` Rafael J. Wysocki
2008-03-14 14:43       ` Matthew Wilcox
2008-03-14 15:44         ` Rafael J. Wysocki
2008-03-14 17:14           ` Jesse Barnes
2008-03-17  3:40 ` Sergio Monteiro Basto
2008-03-17 21:39   ` Sergio Monteiro Basto
2008-03-18  3:14     ` Shaohua Li
2008-03-18 23:47       ` Sergio Monteiro Basto
2008-04-06  2:05       ` Sergio Monteiro Basto

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=200803141537.50589.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=gregkh@suse.de \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-pci@atrey.karlin.mff.cuni.cz \
    --cc=shaohua.li@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