From: Dan Malek <dan@embeddededge.com>
To: Jean-Denis Boyer <jdboyer@mediatrix.com>
Cc: Pavel Bartusek <pba@sysgo.de>,
linuxppc-embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: MDIO clock speed computation
Date: Tue, 23 Jul 2002 13:34:41 -0400 [thread overview]
Message-ID: <3D3D93B1.1090304@embeddededge.com> (raw)
In-Reply-To: 2702075D4DE2B043BF5EB82E9CFAD45B093B11@mail1.mediatrix.com
Jean-Denis Boyer wrote:
> With a frequency of 46.5MHz, you get a MII clock of 2.58MHz.
OK....We'll use something else, then.
> Why adding 500000 (0.5MHz) to the internal clock in this computation?
> We usually do that to round up (or down) to the nearest integer.
I did it to round up so the frequencies I knew about at the time would
generate the proper results. I have to admit, I never expected to
see someone run something like 46.5 MHz. I guess when we made the
change to represent the frequency in Hz instead of MHz, the arithmetic
fell apart. In the past, we couldn't represent 46.5 MHz, it would
have been 47 MHz, so the rounding would have produced a correct result.
> But we do NOT want to round down, or the divisor (MII_SPEED) will be too
> low.
I'm not rounding down, there are two cases where it is rounded up, but
I guess that still isn't enough.
> We want to round up to the nearest integer when divided by 2*2.5MHz.
Will this work for all cases? :
((((bd->bi_intfreq + 4999999) / 2500000) / 2 ) & 0x3F ) << 1;
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-07-23 17:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-23 15:47 MDIO clock speed computation Jean-Denis Boyer
2002-07-23 17:34 ` Dan Malek [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-07-23 19:41 Jean-Denis Boyer
2002-07-24 7:38 ` Pavel Bartusek
2002-07-22 20:54 Jean-Denis Boyer
2002-07-22 18:19 Jean-Denis Boyer
2002-07-22 19:51 ` Dan Malek
2002-07-22 20:12 ` Dan Malek
2002-07-22 20:15 ` Wolfgang Denk
2002-07-23 10:22 ` Pavel Bartusek
2002-07-23 15:01 ` Dan Malek
2002-07-22 17:19 Pavel Bartusek
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=3D3D93B1.1090304@embeddededge.com \
--to=dan@embeddededge.com \
--cc=jdboyer@mediatrix.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=pba@sysgo.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;
as well as URLs for NNTP newsgroup(s).