From: Greg KH <gregkh@suse.de>
To: Adam Belay <abelay@novell.com>
Cc: Linux-pm mailing list <linux-pm@lists.osdl.org>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC][PATCH 2/6] PCI PM: capability probing and setup
Date: Wed, 16 Nov 2005 10:07:48 -0800 [thread overview]
Message-ID: <20051116180748.GD6908@suse.de> (raw)
In-Reply-To: <1132125661.3656.7.camel@localhost.localdomain>
On Wed, Nov 16, 2005 at 02:21:01AM -0500, Adam Belay wrote:
> On Tue, 2005-11-15 at 22:21 -0800, Greg KH wrote:
> > On Tue, Nov 15, 2005 at 10:31:17PM -0500, Adam Belay wrote:
> > > +int pci_setup_device_pm(struct pci_dev *dev)
> >
> > Care to give kernel doc for this new function?
>
> Absolutely. I was planing to do this but must have forgotten.
>
> > > + unsigned char state_mask; /* a mask of supported power states */
> > > + unsigned char pme_mask; /* a mask of power states that allow #PME */
> >
> > Trailing space, use quilt it strips this :)
>
> Sorry about that :)
>
> >
> > > + struct pci_dev_pm *pm; /* power management information */
> >
> > Why make this a pointer and not just part of this structure? Don't all
> > pci devices need this?
>
> Actually, not every PCI device supports the PCI PM spec. There are many
> devices, even in modern systems, that can only be in D0. I was thinking
> we could save some memory and allocate this structure when PCI PM is
> detected. Would that be ok?
That would be ok, but you better remember to check for the pointer when
doing things like suspend and resume of the config space.
thanks,
greg k-h
prev parent reply other threads:[~2005-11-16 18:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-16 3:31 [RFC][PATCH 2/6] PCI PM: capability probing and setup Adam Belay
2005-11-16 6:21 ` Greg KH
2005-11-16 7:21 ` Adam Belay
2005-11-16 18:07 ` 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=20051116180748.GD6908@suse.de \
--to=gregkh@suse.de \
--cc=abelay@novell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.osdl.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