From: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2005@gmx.net>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: acpi-devel <acpi-devel@lists.sourceforge.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-ide@vger.kernel.org, linux-usb-devel@lists.sourceforge.net
Subject: Re: [linux-usb-devel] PCI quirks not handled and config space differences on resume from S3
Date: Tue, 16 Aug 2005 17:44:18 +0200 [thread overview]
Message-ID: <430209D2.1000307@gmx.net> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0508161131240.18233-100000@iolanthe.rowland.org>
Alan Stern schrieb:
> On Tue, 16 Aug 2005, Carl-Daniel Hailfinger wrote:
>
>
>>Hi,
>>[...]
>>Besides that, a number of drivers do not restore the pci config
>>space of their associated devices properly on resume from S3.
>>
>>These drivers (and associated devices) are:
>>- uhci_hcd (USB Controller: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller)
>>[...]
>>Diff between "lspci -vvvxxx" before and after resume for all
>>problematic devices on my machine is attached.
>>
>>Are there any patches I can try?
>
>
> The uhci-hcd driver _does_ restore the config space for its devices
> properly.
>
>> [lspci dump]
>
>
> Just because the before and after values are different doesn't mean
> anything is wrong. Those particular bits are set by the hardware in
> response to various events. They are used only by the BIOS, to provide
> USB keyboard and mouse services. They don't affect the device's function
> or the Linux driver at all.
Thanks for the information and sorry for bothering you.
> Alan Stern
Regards,
Carl-Daniel
--
http://www.hailfinger.org/
prev parent reply other threads:[~2005-08-16 15:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-16 12:43 PCI quirks not handled and config space differences on resume from S3 Carl-Daniel Hailfinger
2005-08-16 15:37 ` [linux-usb-devel] " Alan Stern
2005-08-16 15:42 ` Erik Slagter
2005-08-16 15:44 ` Carl-Daniel Hailfinger [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=430209D2.1000307@gmx.net \
--to=c-d.hailfinger.devel.2005@gmx.net \
--cc=acpi-devel@lists.sourceforge.net \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=stern@rowland.harvard.edu \
/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).