public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Question about setting the sys clk freq based on a pull up on io.
Date: Wed, 19 Nov 2003 09:59:06 +0100	[thread overview]
Message-ID: <20031119085911.219AFC5F5F@atlas.denx.de> (raw)
In-Reply-To: Your message of "Tue, 18 Nov 2003 18:02:29 PST." <3FBACF35.4020006@esteem.com>

Dear Conn,

in message <3FBACF35.4020006@esteem.com> you wrote:
> 
> 	My problem is how do I go about this without severly modifying U-Boots 
> structure. In analyzing how to do this I determined that the 
> configuration and reading of the IO pin sould be done in a 
> board_pre_init function. This rases the issue of passing values between 
> the init functions called by board_init_f. My second issue is how do I 

You can store the cpu_clk / bus_clk in the global_data structure.

> deal with the two frquencies since only one can be defined as 
> CONFIG_SYS_CLK_FREQ(which is used in several places) without sticking 
> lots of nasty board specific ifdefs through out the code.

I don't see the need for #ifdef's.

> (Note I didn't look at them all). We realy don't want to have to specify 
> at compile time what frequency we intend on using. This may become an 

I see no need that CONFIG_SYS_CLK_FREQ must be a constant. Instead of

	#define CONFIG_SYS_CLK_FREQ     33333333

you can - for example - use

	#define CONFIG_SYS_CLK_FREQ     my_function_to_read_clocks()

Best regards,

Wolfgang Denk

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd at denx.de
"Most people would like to be delivered  from  temptation  but  would
like it to keep in touch."                             - Robert Orben

      parent reply	other threads:[~2003-11-19  8:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-19  2:02 [U-Boot-Users] Question about setting the sys clk freq based on a pull up on io Conn Clark
2003-11-19  2:22 ` Andrew May
2003-11-19  8:59 ` Wolfgang Denk [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=20031119085911.219AFC5F5F@atlas.denx.de \
    --to=wd@denx.de \
    --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