From: Ben Warren <biggerbadderben@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] arm:kirkwood Wait for the link to come up on kirkwood network init
Date: Wed, 19 Aug 2009 10:08:02 -0700 [thread overview]
Message-ID: <4A8C3172.70001@gmail.com> (raw)
In-Reply-To: <20090819122415.0487b2d8@marrow.netinsight.se>
Simon,
Simon Kagstrom wrote:
> Wait for the link to come up on kirkwood network init
>
> This patch makes the device wait for up to 5 seconds for the link to
> come up, similar to what many of the other network drivers do. This
> avoids confusing situations where, e.g., a tftp fails when initiated
> early after U-boot has started (before the link has come up).
>
> Signed-off-by: Simon Kagstrom <simon.kagstrom@netinsight.net>
> ---
> drivers/net/kirkwood_egiga.c | 17 ++++++++++++-----
> 1 files changed, 12 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/net/kirkwood_egiga.c b/drivers/net/kirkwood_egiga.c
> index f31fefc..9ac9c1f 100644
> --- a/drivers/net/kirkwood_egiga.c
> +++ b/drivers/net/kirkwood_egiga.c
> @@ -396,6 +396,7 @@ static int kwgbe_init(struct eth_device *dev)
> {
> struct kwgbe_device *dkwgbe = to_dkwgbe(dev);
> struct kwgbe_registers *regs = dkwgbe->regs;
> + int i;
>
> /* setup RX rings */
> kwgbe_init_rx_desc_ring(dkwgbe);
> @@ -443,12 +444,18 @@ static int kwgbe_init(struct eth_device *dev)
>
> #if (defined (CONFIG_MII) || defined (CONFIG_CMD_MII)) \
> && defined (CONFIG_SYS_FAULT_ECHO_LINK_DOWN)
> - u16 phyadr;
> - miiphy_read(dev->name, 0xEE, 0xEE, &phyadr);
> - if (!miiphy_link(dev->name, phyadr)) {
> - printf("%s: No link on %s\n", __FUNCTION__, dev->name);
>
Please use __func__ instead. It's defined in C99, while __FUNCTION__
isn't (or so I've read)
> - return -1;
> + /* Wait up to 5s for the link status */
> + for (i = 0; i < 5; i++) {
> + u16 phyadr;
>
Please put this variable declaration outside of the 'for' loop
> + miiphy_read(dev->name, 0xEE, 0xEE, &phyadr);
>
What does '0xEE' mean? I know you didn't write it, but magic numbers
are bad.
> + /* Return if we get link up */
> + if (miiphy_link(dev->name, phyadr))
>
> + return 0;
> + udelay(1000000);
> }
> +
> + printf("%s: No link on %s\n", __FUNCTION__, dev->name);
> + return -1;
> #endif
> return 0;
> }
>
regards,
Ben
next prev parent reply other threads:[~2009-08-19 17:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-19 10:24 [U-Boot] [PATCH] arm:kirkwood Wait for the link to come up on kirkwood network init Simon Kagstrom
2009-08-19 17:08 ` Ben Warren [this message]
2009-08-19 19:25 ` Wolfgang Denk
2009-08-19 19:29 ` Ben Warren
2009-08-19 19:40 ` Wolfgang Denk
2009-08-20 7:51 ` Simon Kagstrom
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=4A8C3172.70001@gmail.com \
--to=biggerbadderben@gmail.com \
--cc=u-boot@lists.denx.de \
/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