aboutsummaryrefslogtreecommitdiff
path: root/configs/CMPCPRO_defconfig
diff options
context:
space:
mode:
authorEugen Hristev <eugen.hristev@collabora.com>2023-04-13 14:36:45 +0300
committerKever Yang <kever.yang@rock-chips.com>2023-05-09 22:50:01 +0800
commit716ed2a8c0bba085372df0eb7edb580b11e8d94c (patch)
tree610463632424733b8e2c5422a70c60afd080b054 /configs/CMPCPRO_defconfig
parent35c275065c22a73fd68792d4fa0c345caab5071f (diff)
downloadu-boot-716ed2a8c0bba085372df0eb7edb580b11e8d94c.zip
u-boot-716ed2a8c0bba085372df0eb7edb580b11e8d94c.tar.gz
u-boot-716ed2a8c0bba085372df0eb7edb580b11e8d94c.tar.bz2
clk: rockchip: rk3588: add hardcoded assigned clocks values
The CRU is being probed with a default set of assigned clocks, which are not implemented in the driver at all. Hence, when clk_set_defaults is called, it fails with ENOENT. This would not be a problem, as the CRU still handles all the required clocks, and the assigned clocks are default configs which are preprogrammed or not required for Uboot operations. However, the rockchip reset driver is being bound by the same DT node as CRU, as the reset driver has no DT node. But, when probing the reset node, it will call again the clk_set_defaults for the CRU node, and failing because of missing those specific clocks in the rk3588 clock driver. To avoid this, simply implement a basic set/get that will just return success and the default corresponding rate for the required assigned clocks. As those clocks were not supported in Uboot, not required for Uboot operations, there is no need to do any different kind of initialization. Signed-off-by: Eugen Hristev <eugen.hristev@collabora.com> Reviewed-by: Kever Yang <kever.yang@rock-chips.com>
Diffstat (limited to 'configs/CMPCPRO_defconfig')
0 files changed, 0 insertions, 0 deletions