summaryrefslogtreecommitdiff
path: root/board/rmu
diff options
context:
space:
mode:
authorKumar Gala <galak@kernel.crashing.org>2011-02-16 02:03:29 -0600
committerKumar Gala <galak@kernel.crashing.org>2011-04-04 09:24:43 -0500
commitb5c8753fa173d6372d86dcd11f83ef23c911b0de (patch)
tree1b35489b34b36c3425cc53052109e68dd05ec20b /board/rmu
parent863a3eac23362e70f12a456e6b563c416cbc43fc (diff)
downloadu-boot-imx-b5c8753fa173d6372d86dcd11f83ef23c911b0de.zip
u-boot-imx-b5c8753fa173d6372d86dcd11f83ef23c911b0de.tar.gz
u-boot-imx-b5c8753fa173d6372d86dcd11f83ef23c911b0de.tar.bz2
powerpc/85xx: Fixup determining PME, FMan freq
On CoreNet based SoCs (P2040, P3041, P4080, P5020) we have some additional rules to determining the various frequencies that PME & FMan IP blocks run at. We need to take into account: * Reduced number of Core Complex PLL clusters * HWA_ASYNC_DIV (allows for /2 or /4 options) On P2040/P3041/P5020 we only have 2 Core Complex PLLs and in such SoCs the PME & FMan blocks utilize the second Core Complex PLL. On SoCs like p4080 with 4 Core Complex PLLs we utilize the third Core Complex PLL for PME & FMan blocks. On P2040/P3041/P5020 we have the added feature that we can divide the PLL down further by either /2 or /4 based on HWA_ASYNC_DIV. On P4080 this options doesn't exist, however HWA_ASYNC_DIV field in RCW should be set to 0 and this gets a backward compatiable /2 behavior. Signed-off-by: Kumar Gala <galak@kernel.crashing.org>
Diffstat (limited to 'board/rmu')
0 files changed, 0 insertions, 0 deletions