public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Pavel Roskin <proski@gnu.org>
Cc: Pete Zaitcev <zaitcev@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: Patch to make ymfpci legacy address 16 bits
Date: Wed, 09 May 2001 17:08:15 -0400	[thread overview]
Message-ID: <3AF9B1BF.A6BCCCE2@mandrakesoft.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0105091627440.5113-100000@fonzie.nine.com>

Pavel Roskin wrote:
> 
> Hi, Jeff!
> 
> Thanks for your very (!!!) fast response :-)
> 
> > > http://www.red-bean.com/~proski/linux/ymfpci_pm.diff
> >
> > Why not use pci_driver::{suspend,resume} ?
> 
> I'm just a bit conservative. There are several drivers that don't use this
> mechanism, notably trident and maestro. Do you think it's safe to switch
> all sound drivers to the mechanism you are proposing?
> 
> I'm worried about a comment in maestro.c:
> 
>                 /*
>                  * we'd also like to find out about
>                  * power level changes because some biosen
>                  * do mean things to the maestro when they
>                  * change their power state.
>                  */
> 
> If we switch to pci_driver::{suspend,resume}, will it ever be possible to
> add support for any messages other than PM_SUSPEND and PM_RESUME? Probably
> yes, but only in the PCI driver dispatches them.

Basically the PCI core should implement what PM is necessary, because
eventually struct pci_driver will become a more generic struct driver. 
When that happens, drivers using pci_driver::{suspend,resume} will
automagically work under the new system.  To answer your question, the
PCI[/driver] core should support messages other than PM_{SUSPEND,RESUME}
if they need to be supported.  Right now I mostly see suspend/resume
implemented and nothing else, so that is a very straightforward
conversion to the new PCI API.

Why does maestro.c not use my suggestion?  Because it doesn't use struct
pci_driver.
Why does trident.c not use my suggestion?  Only because noone has
written and tested the patch for it yet :)  It uses struct pci_driver
and should be updated to use ::suspend/resume.

> > In ACPI land the kernel should save and restore the PCI device config
> > space and the PCI bus config space.  It is probably that similar is
> > necessary under APM.
> 
> I have never seen any sound driver doing that. I also know that PCI
> settings are saved by some BIOSes on some hardware.

That's because full PM support is still very much a work in progress :) 
The linux-pm-devel sourceforge list has carried recent discussions, as
has linux-kernel.  Patrick Mochel(sp?) @ Transmeta has posted a
hackers-only patch which incorporates my PCI PM work as well as his own
ACPI work to do suspend and resume.

-- 
Jeff Garzik      | Game called on account of naked chick
Building 1024    |
MandrakeSoft     |

  reply	other threads:[~2001-05-09 21:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-09 20:17 Patch to make ymfpci legacy address 16 bits Pavel Roskin
2001-05-09 20:23 ` Jeff Garzik
2001-05-09 20:52   ` Pavel Roskin
2001-05-09 21:08     ` Jeff Garzik [this message]
2001-05-09 23:43       ` Pavel Roskin
2001-05-09 23:53       ` Zach Brown
2001-05-10  2:53   ` Albert D. Cahalan
2001-05-10  7:28     ` Question: Status of USAGI/FreeSWAN? Dax Kelson
2001-05-11  2:52       ` Mike Fedyk
2001-05-10 11:54     ` Patch to make ymfpci legacy address 16 bits mirabilos
  -- strict thread matches above, loose matches on Subject: below --
2001-05-09  0:37 Pete Zaitcev

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=3AF9B1BF.A6BCCCE2@mandrakesoft.com \
    --to=jgarzik@mandrakesoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=proski@gnu.org \
    --cc=zaitcev@redhat.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