diff options
| author | Rick Chen <rick@andestech.com> | 2019-01-15 13:30:35 +0800 |
|---|---|---|
| committer | Andes <uboot@andestech.com> | 2019-01-22 17:36:20 +0800 |
| commit | 866ab879c94f837150af6c5094372de23ca3bd17 (patch) | |
| tree | 5c67f13246e16cae32b6fb7094f6e94d0e26a829 | |
| parent | e690148223cb0828d601f43703e7fc238d85884d (diff) | |
| download | u-boot-866ab879c94f837150af6c5094372de23ca3bd17.zip u-boot-866ab879c94f837150af6c5094372de23ca3bd17.tar.gz u-boot-866ab879c94f837150af6c5094372de23ca3bd17.tar.bz2 | |
nds32: dts: Fix mmc node compatible string
In the two commits:
cf3922dddc44a968685b535f2af195f1e51f4a7b
mmc: ftsdc010_mci: Sync compatible with DT mmc node
c14e90e8445e7b1c3531b4bdeb778c47bd6570eb
riscv: dts: Sync DT with Linux Kernel
ftsdc010_mci's compatible has been modified as
"andestech,atfsdc010" for RISC-V synchronization.
But ae3xx.dts and ag101p.dts which are used for
nds32 adp-ae3xx and adp-ag101p platforms did not
be modified correctly at that time. It will cause
mmc detection failure. Fix it here.
Signed-off-by: Rick Chen <rick@andestech.com>
Cc: Greentime Hu <greentime@andestech.com>
| -rw-r--r-- | arch/nds32/dts/ae3xx.dts | 2 | ||||
| -rw-r--r-- | arch/nds32/dts/ag101p.dts | 2 |
2 files changed, 2 insertions, 2 deletions
diff --git a/arch/nds32/dts/ae3xx.dts b/arch/nds32/dts/ae3xx.dts index b19ba98..272eb33 100644 --- a/arch/nds32/dts/ae3xx.dts +++ b/arch/nds32/dts/ae3xx.dts @@ -70,7 +70,7 @@ }; mmc0: mmc@f0e00000 { - compatible = "andestech,atsdc010"; + compatible = "andestech,atfsdc010"; max-frequency = <100000000>; fifo-depth = <0x10>; reg = <0xf0e00000 0x1000>; diff --git a/arch/nds32/dts/ag101p.dts b/arch/nds32/dts/ag101p.dts index 7832efb..d2ed9ef 100644 --- a/arch/nds32/dts/ag101p.dts +++ b/arch/nds32/dts/ag101p.dts @@ -62,7 +62,7 @@ }; mmc0: mmc@98e00000 { - compatible = "andestech,atsdc010"; + compatible = "andestech,atfsdc010"; max-frequency = <30000000>; fifo-depth = <0x10>; reg = <0x98e00000 0x1000>; |