public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthew Garrett <mjg59-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org>
To: Pavel Machek <pavel-+ZI9xUNit7I@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Shutting down PCI devices on suspend
Date: Sun, 12 Dec 2004 23:23:40 +0000	[thread overview]
Message-ID: <1102893820.5984.42.camel@tyrosine> (raw)
In-Reply-To: <20041212171521.GC6272-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>

On Sun, 2004-12-12 at 18:15 +0100, Pavel Machek wrote:

> * legacy, like VGA or IDE -- okay, we need drivers for those. You need
> to reinit them on resume, anyway, so....
							
The current situation is that we can reinit /most/ VGA hardware from
userspace, but it's less than trivial to make sure that the appropriate
devices are shut down. Surely the situation is more like the following:

1) Some devices don't have drivers. In most cases, it doesn't matter
what power state they're in. Therefore, setting them to D3 (or whatever
SxD says) shouldn't be a problem.

2) For devices that do have drivers, the drivers should set them to the
appropriate power state.

I'd argue that devices that need to be in a specific power state but
whose drivers don't state this have broken drivers. If there's no driver
in charge of the device, we should be able to do whatever we want.
-- 
Matthew Garrett | mjg59-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/

  parent reply	other threads:[~2004-12-12 23:23 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-11 15:37 Shutting down PCI devices on suspend Matthew Garrett
2004-12-11 19:50 ` Nate Lawson
     [not found]   ` <41BB4F70.9060606-Y6VGUYTwhu0@public.gmane.org>
2004-12-11 22:41     ` Matthew Garrett
2004-12-11 23:20       ` Nate Lawson
     [not found]         ` <41BB80C6.1020404-Y6VGUYTwhu0@public.gmane.org>
2004-12-12  1:44           ` Arjen Verweij
2004-12-11 21:31 ` Arjen Verweij
2004-12-12 16:44 ` Pavel Machek
     [not found]   ` <20041212164422.GD6286-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
2004-12-12 17:01     ` Matthew Garrett
2004-12-12 17:15       ` Pavel Machek
     [not found]         ` <20041212171521.GC6272-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
2004-12-12 19:29           ` Adam Belay
     [not found]             ` <20041212192913.GB2661-IBH0VoN/3vPQT0dZR+AlfA@public.gmane.org>
2004-12-12 20:18               ` Pavel Machek
     [not found]                 ` <20041212201810.GE6272-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
2004-12-12 22:36                   ` Adam Belay
     [not found]                     ` <20041212223655.GC2661-IBH0VoN/3vPQT0dZR+AlfA@public.gmane.org>
2004-12-12 23:01                       ` Pavel Machek
     [not found]                         ` <20041212230157.GH6272-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
2004-12-13  0:11                           ` Adam Belay
     [not found]                             ` <20041213001125.GD2661-IBH0VoN/3vPQT0dZR+AlfA@public.gmane.org>
2004-12-13 11:09                               ` Pavel Machek
2004-12-12 23:23           ` Matthew Garrett [this message]
2004-12-13 10:52             ` Pavel Machek
  -- strict thread matches above, loose matches on Subject: below --
2004-12-13  1:59 Li, Shaohua
     [not found] ` <16A54BF5D6E14E4D916CE26C9AD30575C12271-4yWAQGcml66iAffOGbnezLfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2004-12-13 11:11   ` Pavel Machek

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=1102893820.5984.42.camel@tyrosine \
    --to=mjg59-1xo5oi07kqx4cg9nei1l7q@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=pavel-+ZI9xUNit7I@public.gmane.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