All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Ivan Kokshaysky <ink@jurassic.park.msu.ru>
Cc: "David S. Miller" <davem@redhat.com>,
	willy@debian.org, linux-kernel@vger.kernel.org,
	Jeff.Wiedemeier@hp.com
Subject: Re: [patch 2.5] tg3.c: pci_{save,restore}_extended_state
Date: Fri, 24 Jan 2003 14:31:35 -0500	[thread overview]
Message-ID: <20030124193135.GA30884@gtf.org> (raw)
In-Reply-To: <20030124212748.C25285@jurassic.park.msu.ru>

On Fri, Jan 24, 2003 at 09:27:48PM +0300, Ivan Kokshaysky wrote:
> --- 2.5.59/drivers/net/tg3.c	Fri Jan 17 05:22:16 2003
> +++ linux/drivers/net/tg3.c	Fri Jan 24 19:28:44 2003
> @@ -3096,7 +3096,12 @@ static void tg3_chip_reset(struct tg3 *t
>  		val |= PCISTATE_RETRY_SAME_DMA;
>  	pci_write_config_dword(tp->pdev, TG3PCI_PCISTATE, val);
>  
> -	pci_restore_state(tp->pdev, tp->pci_cfg_state);
> +	pci_restore_extended_state(tp->pdev, tp->pci_cfg_state);
> +
> +	/* Make sure MSGINT_MODE is set if MSI is configured. */
> +	pci_read_config_dword(tp->pdev, TG3PCI_MSI_CAP_ID, &val);
> +	if ((val >> 16) & PCI_MSI_FLAGS_ENABLE)
> +		tw32(MSGINT_MODE, MSGINT_MODE_ENABLE);
>  
>  	/* Make sure PCI-X relaxed ordering bit is clear. */
>  	pci_read_config_dword(tp->pdev, TG3PCI_X_CAPS, &val);

hmmmm.  We don't use MSI in the driver anymore, unless I am missing
something.

So, the above patch is probably the wrong thing to do.  I'll need to
check to be sure, but I think that h/w reset clears MSGINT_MODE_ENABLE,
so we wouldn't want to be randomly enabling it when it is purposefully
disabled.

DaveM/Jeff, corrections?


  reply	other threads:[~2003-01-24 19:22 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-24 18:27 [patch 2.5] tg3.c: pci_{save,restore}_extended_state Ivan Kokshaysky
2003-01-24 19:31 ` Jeff Garzik [this message]
2003-01-24 19:34   ` David S. Miller
2003-01-24 20:00   ` Wiedemeier, Jeff
2003-01-24 19:53     ` David S. Miller
2003-01-24 20:04       ` Wiedemeier, Jeff
2003-01-24 20:05     ` Jeff Garzik
2003-01-24 20:24       ` Wiedemeier, Jeff
2003-01-24 20:34         ` Jeff Garzik
2003-01-24 20:46           ` Wiedemeier, Jeff
2003-01-24 20:51             ` David S. Miller
2003-01-24 21:33               ` Wiedemeier, Jeff
2003-01-24 21:34                 ` David S. Miller
2003-01-24 22:41                   ` Ivan Kokshaysky
2003-01-24 22:32                     ` David S. Miller
2003-01-24 22:51                       ` Jeff Garzik
2003-01-25  0:33                       ` Wiedemeier, Jeff
2003-01-25  1:42                         ` David S. Miller
2003-01-24 22:56                 ` Jeff Garzik

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=20030124193135.GA30884@gtf.org \
    --to=jgarzik@pobox.com \
    --cc=Jeff.Wiedemeier@hp.com \
    --cc=davem@redhat.com \
    --cc=ink@jurassic.park.msu.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=willy@debian.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.