From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Patrick Mochel <mochel@transmeta.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-pm-devel@lists.sourceforge.net,
linux-power@phobos.fachschaften.tu-muenchen.de
Subject: Re: PCI power management
Date: Fri, 20 Apr 2001 08:40:37 -0400 [thread overview]
Message-ID: <3AE02E45.57D7BA9D@mandrakesoft.com> (raw)
In-Reply-To: <Pine.LNX.4.10.10104191607280.7690-100000@nobelium.transmeta.com> <20010420120603.28316@mailhost.mipsys.com>
Benjamin Herrenschmidt wrote:
> >When a device comes out of D3[hot], the equivalent of a soft reset is
> >performed. From D3[cold], PCI RST# is asserted, and the device must be
> >completely reinitialized.
>
> Some devices (bad bad HW designers ;) just can't do it themselves. The
> Rage M3 requires the host to assert PCI RST#, and some motherboards
> provide no documented facility for that (it might be possible with Apple
> ASICs for example, it's just not documented).
Why should we support such a non-spec device? Tell ATI to fix their
hardware, and tell users (a) not to use the hardware, or (b) use the
hardware with the knowledge that you are screwed when it comes to Power
Management.
Unless there are more cases like this, this should not factor at all
into the modifications to the PCI and PM code...
--
Jeff Garzik | The difference between America and England is that
Building 1024 | the English think 100 miles is a long distance and
MandrakeSoft | the Americans think 100 years is a long time.
| (random fortune)
next prev parent reply other threads:[~2001-04-20 12:41 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.10.10104181150530.7690-100000@nobelium.transmeta.com>
2001-04-19 8:25 ` PCI power management Jeff Garzik
2001-04-19 10:08 ` Benjamin Herrenschmidt
2001-04-19 10:38 ` CaT
2001-04-19 12:10 ` Benjamin Herrenschmidt
2001-04-19 12:57 ` Alan Cox
2001-04-19 13:14 ` Benjamin Herrenschmidt
2001-04-19 13:33 ` Alan Cox
2001-04-19 13:43 ` Benjamin Herrenschmidt
2001-04-20 0:05 ` Patrick Mochel
2001-04-20 12:06 ` Benjamin Herrenschmidt
2001-04-20 12:40 ` Jeff Garzik [this message]
2001-04-20 12:56 ` Benjamin Herrenschmidt
2001-04-21 9:09 ` Russell King
2001-04-19 10:18 ` Benjamin Herrenschmidt
2001-04-19 13:24 ` Jeff Garzik
2001-04-20 0:11 ` [Linux-pm-devel] " Patrick Mochel
2001-04-19 23:03 ` Patrick Mochel
2004-08-02 21:33 pci " Erik Rigtorp
2004-08-02 23:45 ` Brian Gerst
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=3AE02E45.57D7BA9D@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm-devel@lists.sourceforge.net \
--cc=linux-power@phobos.fachschaften.tu-muenchen.de \
--cc=mochel@transmeta.com \
/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