From: Andrew Morton <akpm@linux-foundation.org>
To: Ayaz Abdulla <aabdulla@nvidia.com>
Cc: manfred@colorfullife.com, jgarzik@pobox.com, netdev@vger.kernel.org
Subject: Re: [PATCH] forcedeth: mgmt unit interface changes
Date: Tue, 27 Jan 2009 17:27:05 -0800 [thread overview]
Message-ID: <20090127172705.d6ad4c56.akpm@linux-foundation.org> (raw)
In-Reply-To: <497A3046.7060202@nvidia.com>
On Fri, 23 Jan 2009 16:01:58 -0500
Ayaz Abdulla <aabdulla@nvidia.com> wrote:
> +static int nv_mgmt_get_version(struct net_device *dev)
> +{
> + struct fe_priv *np = netdev_priv(dev);
> + u8 __iomem *base = get_hwbase(dev);
> + u32 data_ready = readl(base + NvRegTransmitterControl);
> + u32 data_ready2;
> + int i;
> +
> + writel(NVREG_MGMTUNITGETVERSION, base + NvRegMgmtUnitGetVersion);
> + writel(data_ready ^ NVREG_XMITCTL_DATA_START, base + NvRegTransmitterControl);
> + for (i = 0; i < 1000000; i++) {
> + data_ready2 = readl(base + NvRegTransmitterControl);
> + if ((data_ready & NVREG_XMITCTL_DATA_READY) != (data_ready2 & NVREG_XMITCTL_DATA_READY))
> + break;
> + udelay(50);
> + }
> +
> + if (i == 1000000 || (data_ready2 & NVREG_XMITCTL_DATA_ERROR))
> + return 0;
> +
> + np->mgmt_version = readl(base + NvRegMgmtUnitVersion) & NVREG_MGMTUNITVERSION;
> +
> + return 1;
> +}
whee, a 50 second busy-wait.
Unnecessarily, afacit. The sole caller calls this function from
->probe without any locks held?
I'd suggest that we
a) use schedule_timeout_uninterruptible(1) and
b) add a bit of user feedback (printk(".")?) so they don't get bored
and hit the reset button (remember those?)
next prev parent reply other threads:[~2009-01-28 1:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-23 21:01 [PATCH] forcedeth: mgmt unit interface changes Ayaz Abdulla
2009-01-28 1:27 ` Andrew Morton [this message]
2009-01-28 1:29 ` David Miller
2009-01-28 1:34 ` Ayaz Abdulla
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=20090127172705.d6ad4c56.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=aabdulla@nvidia.com \
--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).