Relax no-mmc restriction on mmc1 for jh7110 boards. The restriction is only needed to block use of commands that would cause a device to malfunction, which by testing and observation [1] is not any problem.
1: https://lore.kernel.org/lkml/nt0pr01mb1312e0d9ee9f158a57b77700e6...@nt0pr01mb1312.chnpr01.prod.partner.outlook.cn/ Signed-off-by: E Shattow <[email protected]> Tested-by: Hal Feng <[email protected]> Signed-off-by: Conor Dooley <[email protected]> [ upstream commit: 08128670a931a4117f7b93c703d0186c67c9e1e2 ] (cherry picked from commit cd5d4277d9515be5c10752fd8140f03c3dfec541) --- dts/upstream/src/riscv/starfive/jh7110-common.dtsi | 1 - 1 file changed, 1 deletion(-) diff --git a/dts/upstream/src/riscv/starfive/jh7110-common.dtsi b/dts/upstream/src/riscv/starfive/jh7110-common.dtsi index a315113840e..4fa77ffd54e 100644 --- a/dts/upstream/src/riscv/starfive/jh7110-common.dtsi +++ b/dts/upstream/src/riscv/starfive/jh7110-common.dtsi @@ -299,7 +299,6 @@ assigned-clock-rates = <50000000>; bus-width = <4>; bootph-pre-ram; - no-mmc; cd-gpios = <&sysgpio 41 GPIO_ACTIVE_LOW>; disable-wp; cap-sd-highspeed; -- 2.50.0
