netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: "Bjørn Mork" <bjorn@mork.no>
Cc: netdev <netdev@vger.kernel.org>, Greg KH <gregkh@suse.de>
Subject: Re: [PATCH] 3Com PCI 3c905 causes annoying pci_set_power_state() messages
Date: Tue, 08 May 2007 01:40:24 -0400	[thread overview]
Message-ID: <46400D48.80307@garzik.org> (raw)
In-Reply-To: <87ejlwmd8k.fsf@obelix.mork.no>

Bjørn Mork wrote:
> I don't know if this is the correct place for 3c59x bugs.  Couldn't find
> a maintainer entry for it.  Please redirect as appropriate.
> 
> pci_set_power_state() is a bit weird, causing a failure if a device
> doesn't support PM and the driver tries to
> 
>  1) save it's power_state, 
>  2) wake up and do something, and 
>  3) then reset to the saved state.
> 
> The 3c59x driver does this in it's ioctl function.
> 
> 
> pci_set_power_state() will never set current_state for such devices,
> causing them to remain in PCI_UNKNOWN (5) forever.  But if you try to
> set the state to PCI_UNKNOWN, bounding will kick in, limiting the state
> to PCI_D3hot (3).  Then pci_set_power_state() will complain because 
> PCI_D3hot < current_state, printing useless messages like this:
> 
>  pci_set_power_state(): 0000:00:09.0: state=3, current state=5
>  pci_set_power_state(): 0000:00:09.0: state=3, current state=5
> 
> and returning -EINVAL.
> 
> I believe this is wrong because pci_set_power_state() is supposed to
> return -EIO if device does not support PCI PM.

Yes, please fix PCI.

	Jeff




       reply	other threads:[~2007-05-08  5:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87ejlwmd8k.fsf@obelix.mork.no>
2007-05-08  5:40 ` Jeff Garzik [this message]
2007-05-07  7:30 [PATCH] 3Com PCI 3c905 causes annoying pci_set_power_state() messages Bjørn Mork

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=46400D48.80307@garzik.org \
    --to=jeff@garzik.org \
    --cc=bjorn@mork.no \
    --cc=gregkh@suse.de \
    --cc=netdev@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;
as well as URLs for NNTP newsgroup(s).