diff options
| author | Jonas Karlman <jonas@kwiboo.se> | 2023-08-04 09:34:01 +0000 |
|---|---|---|
| committer | Kever Yang <kever.yang@rock-chips.com> | 2023-08-12 10:35:35 +0800 |
| commit | 520fece4cacb294b78ca7e3a25667a6449c7287c (patch) | |
| tree | 9260af2e13871a9be6992f90350c610c70958404 | |
| parent | 9296f9a8d7ffc96b8a8220a0e74c7dacb1934b2e (diff) | |
| download | u-boot-520fece4cacb294b78ca7e3a25667a6449c7287c.zip u-boot-520fece4cacb294b78ca7e3a25667a6449c7287c.tar.gz u-boot-520fece4cacb294b78ca7e3a25667a6449c7287c.tar.bz2 | |
rockchip: rk356x-u-boot: Set max-frequency prop in sdhci node
Most board device trees for RK356x set max-frequency = <200000000> in
the sdhci node, some boards like Quartz64 do not. This result in an
error message due to sdhci driver trying to set a clock rate of 0
instead of the max-frequency value.
rockchip_sdhci_probe clk set rate fail!
Fix this by setting a common max-frequency in rk356x-u-boot.dtsi. A
patch to set default max-frequency of sdhci node in linux is planned.
Also remove the forced status = "okay" for the sdhci and sdmmc0 nodes,
boards already set correct state for these nodes.
Signed-off-by: Jonas Karlman <jonas@kwiboo.se>
Reviewed-by: Kever Yang <kever.yang@rock-chips.com>
| -rw-r--r-- | arch/arm/dts/rk356x-u-boot.dtsi | 3 |
1 files changed, 1 insertions, 2 deletions
diff --git a/arch/arm/dts/rk356x-u-boot.dtsi b/arch/arm/dts/rk356x-u-boot.dtsi index d21b182..32f687f 100644 --- a/arch/arm/dts/rk356x-u-boot.dtsi +++ b/arch/arm/dts/rk356x-u-boot.dtsi @@ -126,12 +126,11 @@ &sdhci { bootph-pre-ram; - status = "okay"; + max-frequency = <200000000>; }; &sdmmc0 { bootph-pre-ram; - status = "okay"; }; #ifdef CONFIG_ROCKCHIP_SPI_IMAGE |