public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Richard Retanubun <RichardRetanubun@RuggedCom.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Subject: [PATCH] Standardize the use of MCFFEC_TOUT_LOOP as a udelay(1) loop counter.
Date: Wed, 20 May 2009 18:32:31 -0400	[thread overview]
Message-ID: <4A1484FF.2060807@RuggedCom.com> (raw)
In-Reply-To: <4791E710007FEB4BBF83775D787F462F08916819@az33exm22.fsl.freescale.net>

 From 584b5fbd4abfc43f920cc1c329633e03816e28be Mon Sep 17 00:00:00 2001
From: Richard Retanubun <RichardRetanubun@RuggedCom.com>
Date: Wed, 20 May 2009 18:26:01 -0400
Subject: [PATCH] Standardize the use of MCFFEC_TOUT_LOOP as a udelay(1) loop counter.


Signed-off-by: Richard Retanubun <RichardRetanubun@RuggedCom.com>
---
Hi TC,

Sorry for the long delay, I got tied up in an integration and sw release process.
It turns out that there is only one place that needed changing.

  drivers/net/mcfmii.c |    2 +-
  1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/drivers/net/mcfmii.c b/drivers/net/mcfmii.c
index 4f1c0a0..4acc29e 100644
--- a/drivers/net/mcfmii.c
+++ b/drivers/net/mcfmii.c
@@ -270,7 +270,7 @@ void __mii_init(void)
                 if ((status & linkgood) == linkgood)
                         break;

-               udelay(500);
+               udelay(1);
         }
         if (i >= MCFFEC_TOUT_LOOP) {
                 printf("Link UP timeout\n");
--
1.6.2.1

  reply	other threads:[~2009-05-20 22:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-08 12:52 [U-Boot] coldFire: net: Question about the use of MCFFEC_TOUT_LOOP Richard Retanubun
2009-05-11 21:36 ` Liew Tsi Chung-R5AAHP
2009-05-20 22:32   ` Richard Retanubun [this message]
2009-05-26  6:06     ` [U-Boot] Subject: [PATCH] Standardize the use of MCFFEC_TOUT_LOOP as a udelay(1) loop counter Ben Warren
2009-05-26 12:29       ` [U-Boot] Subject: [PATCH] [repost] " Richard Retanubun

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=4A1484FF.2060807@RuggedCom.com \
    --to=richardretanubun@ruggedcom.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