All of lore.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk@arm.linux.org.uk>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Greg KH <greg@kroah.com>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: Fwd: [CFT] Clean up yenta_socket
Date: Mon, 25 Aug 2003 23:52:10 +0100	[thread overview]
Message-ID: <20030825235210.J16790@flint.arm.linux.org.uk> (raw)
In-Reply-To: <3F4A9096.2000700@pobox.com>; from jgarzik@pobox.com on Mon, Aug 25, 2003 at 06:41:26PM -0400

On Mon, Aug 25, 2003 at 06:41:26PM -0400, Jeff Garzik wrote:
> WIBNI?

"wouldn't it be nice if"

> Anyway, MSI needs more than the standard size as well.
> 
> But I would actually prefer the interface to go the other way:
> 
> 	pci_save_state(pdev);
> 		and
> 	pci_restore_state(pdev);
> 
> Allocate and store the state in a pointer in struct pci_dev, or 
> somesuch.  And somebody other than the low-level driver figures out the 
> amount to save and restore.

Hmm.  The reason I wanted to stear clear of that was that sometimes we
don't know what's there.  Taking the yenta as an example, we know that
the "standard" space is 0x48 bytes long.  However, some devices have
extra control registers at 0x80, and then there's the PCI PM registers
up at around 0xa0 or so.

On a different cardbus bridge, the PCI PM registers might be somewhere
else.

Do we care if we overwrite the PCI PM registers with possibly old/stale
data?

In other words, how does the PCI layer itself know how much configuration
space to save and restore over power management calls?

-- 
Russell King (rmk@arm.linux.org.uk)                The developer of ARM Linux
             http://www.arm.linux.org.uk/personal/aboutme.html


      reply	other threads:[~2003-08-25 22:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20030825003529.K16635@flint.arm.linux.org.uk>
2003-08-25 22:41 ` Fwd: [CFT] Clean up yenta_socket Jeff Garzik
2003-08-25 22:52   ` Russell King [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=20030825235210.J16790@flint.arm.linux.org.uk \
    --to=rmk@arm.linux.org.uk \
    --cc=greg@kroah.com \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.