mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alexander Gran <alex@zodiac.dnsalias.org>
To: David Brownell <david-b@pacbell.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: fixing usb suspend/resuming
Date: Mon, 19 Jul 2004 09:27:32 +0200	[thread overview]
Message-ID: <200407190927.38734@zodiac.zodiac.dnsalias.org> (raw)
In-Reply-To: <40F962B6.3000501@pacbell.net>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Am Samstag, 17. Juli 2004 19:32 schrieb David Brownell:
>> I'm not clear on the intended relationship between PCI device state
> numbers and ACPI device states in Linux ... but it's clear from the
> specs (ACPI ch2, the mostly-generic bit) that ACPI "3" != PCI "3".

ermm, ok. It is even more complicated. Section 2 of the ACPI specs speaks of 
Global Power states and device power states. 
So we ge the follwing, with G= ACPI Global power state, S = (ACPI?) Sleep 
State, D = ACPI Device power state,
G3 = Mechanical off = everything D3
G2=S5=soft off = everything D3
G1=S4 = Hibernation = everything D3
G1=S3/S2=Sleeping = parts in D2/D1/(D0?)
G0=S0=Working = evrything in D0

/proc/acpi/sleep talks about the S states, so when I want STR, which is S3 i 
echo 3 > /proc/acpi/sleep.
The PCI state would also be 3 for most devices, I think. Pci state 1 or 2 
cannot be expected to be supported.

> I'm suspecting that something is mistranslating between ACPI
> power state numbering and PCI power state numbering

ACK.

> I'd _certainly_ expect that the numbers passed to PCI suspend
> and resume calls would match the PCI state numbers, not the
> ACPI numbers!  But those numbers aren't documented in the
> Linux sources, so probably different people are making rather
> different assumptions.  After all, "3 == 3" and "2 == 2".
>
> That's all different from the ACPI system power states, too.
> (Which is what I'd expect /proc/acpi/sleep to affect.)

I think that file doesn't expect Global power states, as thats only on, 
sleeping, off, but sleep states. However I don't see the translation into PCI 
sleep states either. But there must be some translation, as a 3 is translatet 
into a 2 here (which than failes..)

I suppose some cleanup and documentation is required here.

regards
Alex

- -- 
Encrypted Mails welcome.
PGP-Key at http://zodiac.dnsalias.org/misc/pgpkey.asc | Key-ID: 0x6D7DD291
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFA+3fp/aHb+2190pERArKfAJ4mShRA2zHafuPrsWKTPVVFUumHQwCfYb3M
9x0AqFQqhhPILjYDEnxlXH4=
=d/FA
-----END PGP SIGNATURE-----


  reply	other threads:[~2004-07-19  7:27 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200405281406.10447@zodiac.zodiac.dnsalias.org>
     [not found] ` <40B74FC2.8000708@pacbell.net>
2004-06-01 14:14   ` Alexander Gran
2004-07-17 17:32     ` David Brownell
2004-07-19  7:27       ` Alexander Gran [this message]
2004-07-21  5:05         ` David Brownell
2004-07-29  8:35           ` Pavel Machek
2004-07-29 12:17             ` Nigel Cunningham
2004-07-29 12:51               ` Oliver Neukum
2004-07-29 22:15                 ` Nigel Cunningham
2004-07-29 14:07               ` David Brownell
2004-07-29 21:02               ` Pavel Machek
2004-07-29 22:26                 ` Nigel Cunningham
2004-07-29 22:39                   ` Pavel Machek
2004-07-29 22:51                     ` Nigel Cunningham
2004-07-29 14:16             ` David Brownell

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=200407190927.38734@zodiac.zodiac.dnsalias.org \
    --to=alex@zodiac.dnsalias.org \
    --cc=david-b@pacbell.net \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®