Skip to content
Snippets Groups Projects
Commit bfac0847 authored by Stephen Warren's avatar Stephen Warren Committed by Tom Warren
Browse files

ARM: tegra: fix COUNTER_FREQUENCY for T210


While T210 boards all have 38.4MHz crystals, per the TRM, the only
supported configuration is to divide the crystal frequency by 2 to
generate clk_m, which is what feeds the ARM generic timers amongst other
things. Fix the value of COUNTER_FREQUENCY to reflect this divide-by-2.

When I queried the 19.2 value in Tom's original T210 patches, I wasn't
aware of this extra divide-by-2, and didn't notice any effect from the
incorrect value, since its only used if U-Boot is booted in EL3, whereas
I'm booting it in EL2.

Reported-by: default avatarThierry Reding <treding@nvidia.com>
Signed-off-by: default avatarStephen Warren <swarren@nvidia.com>
Signed-off-by: default avatarTom Warren <twarren@nvidia.com>
parent a6b2daff
No related branches found
No related tags found
No related merge requests found
......@@ -60,6 +60,7 @@
#include "tegra-common-usb-gadget.h"
#include "tegra-common-post.h"
#define COUNTER_FREQUENCY 38400000
/* Crystal is 38.4MHz. clk_m runs at half that rate */
#define COUNTER_FREQUENCY 19200000
#endif /* _E2220_1170_H */
......@@ -60,6 +60,7 @@
#include "tegra-common-usb-gadget.h"
#include "tegra-common-post.h"
#define COUNTER_FREQUENCY 38400000
/* Crystal is 38.4MHz. clk_m runs at half that rate */
#define COUNTER_FREQUENCY 19200000
#endif /* _P2371_0000_H */
......@@ -60,6 +60,7 @@
#include "tegra-common-usb-gadget.h"
#include "tegra-common-post.h"
#define COUNTER_FREQUENCY 38400000
/* Crystal is 38.4MHz. clk_m runs at half that rate */
#define COUNTER_FREQUENCY 19200000
#endif /* _P2371_2180_H */
......@@ -61,7 +61,8 @@
#include "tegra-common-usb-gadget.h"
#include "tegra-common-post.h"
#define COUNTER_FREQUENCY 38400000
/* Crystal is 38.4MHz. clk_m runs at half that rate */
#define COUNTER_FREQUENCY 19200000
#define CONFIG_OF_BOARD_SETUP
#endif /* _P2571_H */
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment