keystone2: use correct EFUSE_BOOTROM fileds to configure speed
The get_max_arm_speed() and get_max_dev_speed() used wrong register fields to get the maximum speeds. This commit fixes the bug. Signed-off-by: Vitaly Andrianov <vitalya@ti.com> Reviewed-by: Tom Rini <trini@konsulko.com>
This commit is contained in:
parent
c6265f7f34
commit
437a7293a7
1 changed files with 6 additions and 6 deletions
|
@ -246,18 +246,18 @@ static inline u32 read_efuse_bootrom(void)
|
|||
}
|
||||
#endif
|
||||
|
||||
inline int get_max_dev_speed(void)
|
||||
{
|
||||
return get_max_speed(read_efuse_bootrom() & 0xffff, dev_speeds);
|
||||
}
|
||||
|
||||
#ifndef CONFIG_SOC_K2E
|
||||
inline int get_max_arm_speed(void)
|
||||
{
|
||||
return get_max_speed((read_efuse_bootrom() >> 16) & 0xffff, arm_speeds);
|
||||
return get_max_speed(read_efuse_bootrom() & 0xffff, arm_speeds);
|
||||
}
|
||||
#endif
|
||||
|
||||
inline int get_max_dev_speed(void)
|
||||
{
|
||||
return get_max_speed((read_efuse_bootrom() >> 16) & 0xffff, dev_speeds);
|
||||
}
|
||||
|
||||
void pass_pll_pa_clk_enable(void)
|
||||
{
|
||||
u32 reg;
|
||||
|
|
Loading…
Reference in a new issue