diff options
author | Andre Przywara <andre.przywara@arm.com> | 2020-04-27 19:17:59 +0100 |
---|---|---|
committer | Tom Rini <trini@konsulko.com> | 2020-05-07 09:01:42 -0400 |
commit | e3e2d662a273d5ac67998f390529966a8d8c8a3b (patch) | |
tree | 960e608c449f56aa82277bf96fbc83253590a35d /include/configs | |
parent | 7d6dae0dfb4b056850cde6ff91d06bb5cbda8fd3 (diff) |
uart: pl011: Add proper DM clock support
Even though the PL011 UART driver claims to be DM compliant, it does not
really a good job with parsing DT nodes. U-Boot seems to adhere to a
non-standard binding, either requiring to have a "skip-init" property in
the node, or to have an extra "clock" property holding the base
*frequency* value for the baud rate generator.
DTs in the U-Boot tree seem to have been hacked to match this
requirement.
The official binding does not mention any of these properties, instead
recommends a standard "clocks" property to point to the baud base clock.
Some boards use simple "fixed-clock" providers, which U-Boot readily
supports, so let's add some simple DM clock code to the PL011 driver to
learn the rate of the first clock, as described by the official binding.
These clock nodes seem to be not ready very early in the boot process,
so provide a fallback value, by re-using the already existing
CONFIG_PL011_CLOCK variable.
Signed-off-by: Andre Przywara <andre.przywara@arm.com>
[trini: Add <clock_legacy.h> for get_bus_freq() for layerscape
platforms]
Signed-off-by: Tom Rini <trini@konsulko.com>
Reviewed-by: Simon Glass <sjg@chromium.org>
Diffstat (limited to 'include/configs')
0 files changed, 0 insertions, 0 deletions