Searched hist:"7 c0a1877e76b5dc7b6326e3cb670c5156d4d4383" (Results 1 – 5 of 5) sorted by relevance
| /rk3399_ARM-atf/plat/rpi/rpi3/ |
| H A D | rpi3_bl31_setup.c | 7c0a1877e76b5dc7b6326e3cb670c5156d4d4383 Sun Aug 04 09:46:21 UTC 2019 Andre Przywara <andre.przywara@arm.com> rpi3: Allow runtime determination of UART base clock rate
At the moment the UART input clock rate is hard coded at compile time.
This works as long as the GPU firmware always sets up the same rate,
which does not seem to be true for the Raspberry Pi 4.
In preparation for being able to change this at runtime, add a base
clock parameter to the console setup function. This is still hardcoded
for the Raspberry Pi 3.
Change-Id: I398bc2f1e9b46f7af9a84cb0b33cbe8e78f2d900
Signed-off-by: Andre Przywara <andre.przywara@arm.com>
|
| H A D | rpi3_bl1_setup.c | 7c0a1877e76b5dc7b6326e3cb670c5156d4d4383 Sun Aug 04 09:46:21 UTC 2019 Andre Przywara <andre.przywara@arm.com> rpi3: Allow runtime determination of UART base clock rate
At the moment the UART input clock rate is hard coded at compile time.
This works as long as the GPU firmware always sets up the same rate,
which does not seem to be true for the Raspberry Pi 4.
In preparation for being able to change this at runtime, add a base
clock parameter to the console setup function. This is still hardcoded
for the Raspberry Pi 3.
Change-Id: I398bc2f1e9b46f7af9a84cb0b33cbe8e78f2d900
Signed-off-by: Andre Przywara <andre.przywara@arm.com>
|
| H A D | rpi3_bl2_setup.c | 7c0a1877e76b5dc7b6326e3cb670c5156d4d4383 Sun Aug 04 09:46:21 UTC 2019 Andre Przywara <andre.przywara@arm.com> rpi3: Allow runtime determination of UART base clock rate
At the moment the UART input clock rate is hard coded at compile time.
This works as long as the GPU firmware always sets up the same rate,
which does not seem to be true for the Raspberry Pi 4.
In preparation for being able to change this at runtime, add a base
clock parameter to the console setup function. This is still hardcoded
for the Raspberry Pi 3.
Change-Id: I398bc2f1e9b46f7af9a84cb0b33cbe8e78f2d900
Signed-off-by: Andre Przywara <andre.przywara@arm.com>
|
| /rk3399_ARM-atf/plat/rpi/common/include/ |
| H A D | rpi_shared.h | 7c0a1877e76b5dc7b6326e3cb670c5156d4d4383 Sun Aug 04 09:46:21 UTC 2019 Andre Przywara <andre.przywara@arm.com> rpi3: Allow runtime determination of UART base clock rate
At the moment the UART input clock rate is hard coded at compile time.
This works as long as the GPU firmware always sets up the same rate,
which does not seem to be true for the Raspberry Pi 4.
In preparation for being able to change this at runtime, add a base
clock parameter to the console setup function. This is still hardcoded
for the Raspberry Pi 3.
Change-Id: I398bc2f1e9b46f7af9a84cb0b33cbe8e78f2d900
Signed-off-by: Andre Przywara <andre.przywara@arm.com>
|
| /rk3399_ARM-atf/plat/rpi/common/ |
| H A D | rpi3_common.c | 7c0a1877e76b5dc7b6326e3cb670c5156d4d4383 Sun Aug 04 09:46:21 UTC 2019 Andre Przywara <andre.przywara@arm.com> rpi3: Allow runtime determination of UART base clock rate
At the moment the UART input clock rate is hard coded at compile time.
This works as long as the GPU firmware always sets up the same rate,
which does not seem to be true for the Raspberry Pi 4.
In preparation for being able to change this at runtime, add a base
clock parameter to the console setup function. This is still hardcoded
for the Raspberry Pi 3.
Change-Id: I398bc2f1e9b46f7af9a84cb0b33cbe8e78f2d900
Signed-off-by: Andre Przywara <andre.przywara@arm.com>
|