aboutsummaryrefslogtreecommitdiffstats
path: root/lib/psci/psci_common.c
diff options
context:
space:
mode:
authorHeiko Stuebner <heiko@sntech.de>2019-08-05 16:40:35 +0200
committerHeiko Stuebner <heiko@sntech.de>2019-08-09 09:40:19 +0200
commitdd4a0d1618a6367061ab507ea450db98bbf2cc36 (patch)
tree01df0704ddf61621c72fdfb705eb795183b5824b /lib/psci/psci_common.c
parent30970e0f2979e297831f8ea27466aa3e67992ce4 (diff)
downloadplatform_external_arm-trusted-firmware-dd4a0d1618a6367061ab507ea450db98bbf2cc36.tar.gz
platform_external_arm-trusted-firmware-dd4a0d1618a6367061ab507ea450db98bbf2cc36.tar.bz2
platform_external_arm-trusted-firmware-dd4a0d1618a6367061ab507ea450db98bbf2cc36.zip
rockchip: move dt-coreboot uart distinction into param handling code
Rockchip platforms can be booted from either u-boot or coreboot. So far the Coreboot-console was initizalized from a coreboot data struct in the early_param2 callbacks and dt-based consoles with data from the rockchip_get_uart_* functions. But later code may also need this console information for example for special suspend handling. To make this easy follow a suggestion from Julius Werner and move the coreboot<->dt distinction into the rockchip_get_uart_* functions, thus making correct data about the used uart available to all Rockchip platform code at all times. This includes a new rockchip_get_uart_clock as well, because while the dt-platforms right now always just default the rate defined in a constant Coreboot provides its own field for the clock rate and we don't want to loose that information for the console init. Similarly the rk_uart_* variables should move into the non-Coreboot code, to prevent them from being marked as unused, which also requires the rk_get_uart_* functions to move below the actual dt-parsing. Signed-off-by: Heiko Stuebner <heiko@sntech.de> Change-Id: I278d595d2aa6c6864187fc8979a9fbff9814feac
Diffstat (limited to 'lib/psci/psci_common.c')
0 files changed, 0 insertions, 0 deletions