diff options
| author | Hannes Schmelzer | 2018-07-06 15:41:23 +0200 |
|---|---|---|
| committer | Tom Rini | 2018-07-19 17:03:34 -0400 |
| commit | 96cf89f86b98116539020ddff2a6d22cf70b267b (patch) | |
| tree | 19905ef4e6bbec3411eeefdd90456fb7e3cc6728 /board | |
| parent | 2930941aee2ceb1452a4a779cdb20df150fc332f (diff) | |
board/BuR/common: fix PMIC mpu-pll setup
If a board-code calls the pmicsetup(u32 mpupll) with a mpupll value
!= 0 it wants to force some frequency with the value provided by mpupll.
Setting up 1 GHz is wrong here.
Nobody did take notice about that yet, since every board calls this
function with zero.
Signed-off-by: Hannes Schmelzer <oe5hpm@oevsv.at>
Diffstat (limited to 'board')
| -rw-r--r-- | board/BuR/common/common.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/board/BuR/common/common.c b/board/BuR/common/common.c index 1e14a902e9b..38da36d50b5 100644 --- a/board/BuR/common/common.c +++ b/board/BuR/common/common.c @@ -280,7 +280,7 @@ void pmicsetup(u32 mpupll) printf("detected max. frequency: %d - ", dpll_mpu_opp100.m); if (0 != mpupll) { - dpll_mpu_opp100.m = MPUPLL_M_1000; + dpll_mpu_opp100.m = mpupll; printf("retuning MPU-PLL to: %d MHz.\n", dpll_mpu_opp100.m); } else { puts("ok.\n"); |