diff options
author | Ralf Baechle <ralf@linux-mips.org> | 2006-10-20 21:05:20 -0400 |
---|---|---|
committer | Ralf Baechle <ralf@linux-mips.org> | 2006-10-21 18:17:35 -0400 |
commit | 224dc50ece1b40f8cff5ecadd42a6b2691e231de (patch) | |
tree | e03d1b127e931b54aaea9579a211988a3f7f4c16 /Documentation | |
parent | cb7fabcf9d4340b61f012cc7e8e3d7ff5c4f441c (diff) |
[MIPS] Cleanup remaining references to mips_counter_frequency.
Noticed by Samium Gromoff but his patch got stale in flight ...
Signed-off-by: Ralf Baechle <ralf@linux-mips.org>
Diffstat (limited to 'Documentation')
-rw-r--r-- | Documentation/mips/time.README | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/Documentation/mips/time.README b/Documentation/mips/time.README index 69ddc5c14b79..e1304b6bc483 100644 --- a/Documentation/mips/time.README +++ b/Documentation/mips/time.README | |||
@@ -63,7 +63,7 @@ the following functions or values: | |||
63 | a) board_time_init - a function pointer. Invoked at the beginnig of | 63 | a) board_time_init - a function pointer. Invoked at the beginnig of |
64 | time_init(). It is optional. | 64 | time_init(). It is optional. |
65 | 1. (optional) set up RTC routines | 65 | 1. (optional) set up RTC routines |
66 | 2. (optional) calibrate and set the mips_counter_frequency | 66 | 2. (optional) calibrate and set the mips_hpt_frequency |
67 | 67 | ||
68 | b) plat_timer_setup - a function pointer. Invoked at the end of time_init() | 68 | b) plat_timer_setup - a function pointer. Invoked at the end of time_init() |
69 | 1. (optional) over-ride any decisions made in time_init() | 69 | 1. (optional) over-ride any decisions made in time_init() |
@@ -72,7 +72,7 @@ the following functions or values: | |||
72 | 72 | ||
73 | c) (optional) board-specific RTC routines. | 73 | c) (optional) board-specific RTC routines. |
74 | 74 | ||
75 | d) (optional) mips_counter_frequency - It must be definied if the board | 75 | d) (optional) mips_hpt_frequency - It must be definied if the board |
76 | is using CPU counter for timer interrupt or it is using fixed rate | 76 | is using CPU counter for timer interrupt or it is using fixed rate |
77 | gettimeoffset(). | 77 | gettimeoffset(). |
78 | 78 | ||
@@ -104,7 +104,7 @@ Step 1: decide how you like to implement the time services. | |||
104 | or use an exnternal timer? | 104 | or use an exnternal timer? |
105 | 105 | ||
106 | In order to use CPU counter register as the timer interrupt source, you | 106 | In order to use CPU counter register as the timer interrupt source, you |
107 | must know the counter speed (mips_counter_frequency). It is usually the | 107 | must know the counter speed (mips_hpt_frequency). It is usually the |
108 | same as the CPU speed or an integral divisor of it. | 108 | same as the CPU speed or an integral divisor of it. |
109 | 109 | ||
110 | d) decide on whether you want to use high-level or low-level timer | 110 | d) decide on whether you want to use high-level or low-level timer |
@@ -121,8 +121,8 @@ Step 3: implement rtc routines, board_time_init() and plat_timer_setup() | |||
121 | if needed. | 121 | if needed. |
122 | 122 | ||
123 | board_time_init() - | 123 | board_time_init() - |
124 | a) (optional) set up RTC routines, | 124 | a) (optional) set up RTC routines, |
125 | b) (optional) calibrate and set the mips_counter_frequency | 125 | b) (optional) calibrate and set the mips_hpt_frequency |
126 | (only needed if you intended to use fixed_rate_gettimeoffset | 126 | (only needed if you intended to use fixed_rate_gettimeoffset |
127 | or use cpu counter as timer interrupt source) | 127 | or use cpu counter as timer interrupt source) |
128 | 128 | ||