Re: [PATCH] arm64: dts: rockchip: Fix SD card init on rk3399-nanopi4

[Christian Kohlschütter]

> Am 14.07.2022 um 13:41 schrieb Robin Murphy <robin.murphy@xxxxxxx>:
> 
> On 2022-07-14 00:41, Heiko Stübner wrote:
>> Hi Christian,
>> Am Donnerstag, 14. Juli 2022, 00:22:23 CEST schrieb Christian Kohlschütter:
>>> mmc/SD-card initialization may sometimes fail on NanoPi r4s with
>>> "mmc1: problem reading SD Status register" /
>>> "mmc1: error -110 whilst initialising SD card"
>>> 
>>> Moreover, rebooting would also sometimes hang.
>>> 
>> Nit: here the commit message should continue with something like:
>> -----
>> This is caused by the vcc3v0-sd regulator referencing the wrong gpio.
>> Fix the regulator to use the correct pin and drop the always-on property.
>> -----
>>> Signed-off-by: Christian Kohlschütter <christian@xxxxxxxxxxxxxxxx>
>>> ---
>>>  arch/arm64/boot/dts/rockchip/rk3399-nanopi4.dtsi | 6 +++---
>>>  1 file changed, 3 insertions(+), 3 deletions(-)
>>> 
>>> diff --git a/arch/arm64/boot/dts/rockchip/rk3399-nanopi4.dtsi b/arch/arm64/boot/dts/rockchip/rk3399-nanopi4.dtsi
>>> index 8c0ff6c96e03..91789801ab03 100644
>>> --- a/arch/arm64/boot/dts/rockchip/rk3399-nanopi4.dtsi
>>> +++ b/arch/arm64/boot/dts/rockchip/rk3399-nanopi4.dtsi
>>> @@ -67,10 +67,10 @@ vcc1v8_s3: vcc1v8-s3 {
>>>  	vcc3v0_sd: vcc3v0-sd {
>>>  		compatible = "regulator-fixed";
>>>  		enable-active-high;
>>> -		gpio = <&gpio0 RK_PA1 GPIO_ACTIVE_HIGH>;
>>> +		gpio = <&gpio0 RK_PD6 GPIO_ACTIVE_HIGH>;
>> The interesting question would be how nano-pi-specific that gpio is.
>> I.e. this is the rk3399-nanopi4.dtsi that is shared by multiple board types,
>> so can you check in schematics if gpio0-d6 is always used on all of them?
> 
> On the R4S schematic, this is GPIO0_A1 same as the others. GPIO0 doesn't even have a bank D on RK3399, it only goes up to B5 :/
> 
>> Thanks
>> Heiko
>>>  		pinctrl-names = "default";
>>>  		pinctrl-0 = <&sdmmc0_pwr_h>;
>>> -		regulator-always-on;
>>> +		regulator-boot-on;
>>>  		regulator-min-microvolt = <3000000>;
>>>  		regulator-max-microvolt = <3000000>;
>>>  		regulator-name = "vcc3v0_sd";
>>> @@ -580,7 +580,7 @@ wifi_reg_on_h: wifi-reg_on-h {
>>>    	sdmmc {
>>>  		sdmmc0_det_l: sdmmc0-det-l {
>>> -			rockchip,pins = <0 RK_PA7 RK_FUNC_GPIO &pcfg_pull_up>;
>>> +			rockchip,pins = <0 RK_PD6 RK_FUNC_GPIO &pcfg_pull_up>;
> 
> ...and claiming the card detect is on the same non-existent pin as the regulator enable is clearly even more wrong.
> 
> Is this another case where a UHS card is involved, such that VCC_SDIO gets left at 1.8V after a reboot, so subsequent attempts to do the initial handshake where the card is expecting 3V logic levels fail? (AKA the Tinkerboard problem). Hobbling the regulator such that Linux can never actually turn VCC3V0_SD off, thus the card never gets reset, might appear to "work", but isn't the right thing to do.
> 
> Robin.

Right, this is all very strange. 

Indeed, I have a UHS card and the problem you describe.
I've actually looked into the other RK3399 dts files to come up with that patch (e.g. rk3399-roc-pc.dtsi, which does this; also see [1])

I understand that we should do the right thing, but I am by no means sure what the "right" thing for this problem is.
That said, I wished someone with expertise and authority in the mmc/rockchip community would fix this for good.

There are several patches around this 1.8V/3V voltage dance that do work, get used by several distributions but didn't get merged to mainline because, well, there could be a better right thing to do (like [2], which is also still needed when using mainline u-boot).

Given the state of this issue, at least aligning the code to match another board's fix — which already is in the mainline kernel — seems a sensible approach to me. It unblocks users like me who would perhaps otherwise just give up on using these devices.

[1] https://lore.kernel.org/linux-mmc/3364813.APbW32NlgJ@phil/T/#m1b23cd2c43b600b5a6f084461ae53e482ad65316
[2] https://patchwork.kernel.org/project/linux-mmc/patch/AM3PR03MB09664161A7FA2BD68B2800A7AC620@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx/