From: Pavel Machek <pavel@ucw.cz>
To: David Brownell <david-b@pacbell.net>
Cc: linux-pm@lists.osdl.org,
Patrick Mochel <mochel@digitalimplant.org>,
Greg KH <greg@kroah.com>,
kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [linux-pm] Adapt drivers to type-safe pci
Date: Fri, 12 Nov 2004 16:35:30 +0100 [thread overview]
Message-ID: <20041112153530.GA1091@elf.ucw.cz> (raw)
In-Reply-To: <200411011700.46493.david-b@pacbell.net>
Hi!
> > This adapts few drivers to type-safe pci powermanagment. I introduced
> > device_to_pci_state helper that will be usefull to few drivers... Does
> > it look okay?
>
> I'd rather have something like the attached patch.
> Fixed policy mappings are generically broken; what
> about devices that don't support PCI_D2?
Point taken, this function is probably too big to be in header.
> This should I guess use the new "pci_power_t", but
> I'm not that current yet.
I'd still like this function to return suitable state (and do nothing
else), to make converting drivers easier.
For now suspend() only gets 0 or 3; I'd rather not change code for
now. Do we really enter PCI_D1 on standby? I believe PCI transitions
are fast enough to enter PCI_D3hot even for standby / suspend-to-ram.
Pavel
> +void
> +pci_choose_state(struct pci_dev *pdev, suspend_state_t sleepstate)
> +{
> + int pm, state;
> + u16 pmc;
> +
> + /* nothing to do for legacy PCI devices */
> + pm = pci_find_capability(pdev, PCI_CAP_ID_PM);
> + if (!pm)
> + return;
> +
> + /* map to a PCI PM state this device supports
> + * FIXME ACPI may know what states to use; we should probably
> + * prefer that policy to this one.
> + */
> + state = 3;
> + switch (sleepstate) {
> + case PM_SUSPEND_ON:
> + state = 0;
> + break;
> + case PM_SUSPEND_STANDBY:
> + case PM_SUSPEND_MEM:
> + pci_read_config_word(pdev, pm + PCI_PM_PMC, &pmc);
> + if (sleepstate == PM_SUSPEND_STANDBY
> + && (pmc & PCI_PM_CAP_D1) != 0)
> + state = 1;
> + else if ((pmc & PCI_PM_CAP_D2) != 0)
> + state = 2;
> + break;
> + }
> +
> + /* maybe go to a deeper power state */
> + if (pdev->current_state < state)
> + pci_set_power_state(pdev, state);
> +}
> +EXPORT_SYMBOL(pci_choose_state);
>
> /**
> * pci_save_state - save the PCI configuration space of a device before suspending
--
People were complaining that M$ turns users into beta-testers...
...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!
prev parent reply other threads:[~2004-11-12 15:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-01 20:26 Pavel Machek
2004-11-02 1:00 ` [linux-pm] " David Brownell
2004-11-02 2:31 ` Benjamin Herrenschmidt
2004-11-12 15:35 ` 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=20041112153530.GA1091@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=david-b@pacbell.net \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.osdl.org \
--cc=mochel@digitalimplant.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
Powered by JetHome