From: Ayaz Abdulla <aabdulla@nvidia.com>
To: Ayaz Abdulla <AAbdulla@nvidia.com>
Cc: Jeff Garzik <jgarzik@pobox.com>,
Manfred Spraul <manfred@colorfullife.com>,
Andrew Morton <akpm@osdl.org>, nedev <netdev@vger.kernel.org>
Subject: Re: [PATCH] forcedeth fix: tx/rx reset
Date: Wed, 27 Aug 2008 10:37:27 -0400 [thread overview]
Message-ID: <48B566A7.8060409@nvidia.com> (raw)
In-Reply-To: <48B2EDBA.6070802@nvidia.com>
I am retracting this path for the time being because we believe there is
other circumstances in play. Once the final root cause is found, I can
send out the correct patch.
Ayaz
Ayaz Abdulla wrote:
> This patch keeps the HW reset for tx/rx asserted until DMA is enabled.
> This is to ensure that all tx/rx initialization (i.e ring setup) is
> finished before de-asserting the reset.
>
> Signed-off-by: Ayaz Abdulla <aabdulla@nvidia.com>
>
>
> ------------------------------------------------------------------------
>
> --- old/drivers/net/forcedeth.c 2008-08-25 13:02:17.000000000 -0400
> +++ new/drivers/net/forcedeth.c 2008-08-25 13:02:20.000000000 -0400
> @@ -233,7 +233,7 @@
> NvRegTxRxControl = 0x144,
> #define NVREG_TXRXCTL_KICK 0x0001
> #define NVREG_TXRXCTL_BIT1 0x0002
> -#define NVREG_TXRXCTL_BIT2 0x0004
> +#define NVREG_TXRXCTL_DMA_DISABLE 0x0004
> #define NVREG_TXRXCTL_IDLE 0x0008
> #define NVREG_TXRXCTL_RESET 0x0010
> #define NVREG_TXRXCTL_RXCHECK 0x0400
> @@ -1555,11 +1555,9 @@
> u8 __iomem *base = get_hwbase(dev);
>
> dprintk(KERN_DEBUG "%s: nv_txrx_reset\n", dev->name);
> - writel(NVREG_TXRXCTL_BIT2 | NVREG_TXRXCTL_RESET | np->txrxctl_bits, base + NvRegTxRxControl);
> + writel(NVREG_TXRXCTL_DMA_DISABLE | NVREG_TXRXCTL_RESET | np->txrxctl_bits, base + NvRegTxRxControl);
> pci_push(base);
> udelay(NV_TXRX_RESET_DELAY);
> - writel(NVREG_TXRXCTL_BIT2 | np->txrxctl_bits, base + NvRegTxRxControl);
> - pci_push(base);
> }
>
> static void nv_mac_reset(struct net_device *dev)
> @@ -1570,7 +1568,7 @@
>
> dprintk(KERN_DEBUG "%s: nv_mac_reset\n", dev->name);
>
> - writel(NVREG_TXRXCTL_BIT2 | NVREG_TXRXCTL_RESET | np->txrxctl_bits, base + NvRegTxRxControl);
> + writel(NVREG_TXRXCTL_DMA_DISABLE | NVREG_TXRXCTL_RESET | np->txrxctl_bits, base + NvRegTxRxControl);
> pci_push(base);
>
> /* save registers since they will be cleared on reset */
> @@ -1589,9 +1587,6 @@
> writel(temp1, base + NvRegMacAddrA);
> writel(temp2, base + NvRegMacAddrB);
> writel(temp3, base + NvRegTransmitPoll);
> -
> - writel(NVREG_TXRXCTL_BIT2 | np->txrxctl_bits, base + NvRegTxRxControl);
> - pci_push(base);
> }
>
> static void nv_get_hw_stats(struct net_device *dev)
>
prev parent reply other threads:[~2008-08-27 17:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-25 17:36 [PATCH] forcedeth fix: tx/rx reset Ayaz Abdulla
2008-08-27 14:37 ` Ayaz Abdulla [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=48B566A7.8060409@nvidia.com \
--to=aabdulla@nvidia.com \
--cc=akpm@osdl.org \
--cc=jgarzik@pobox.com \
--cc=manfred@colorfullife.com \
--cc=netdev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).