On Fri, Nov 24, 2017 at 8:24 PM, Andre Przywara <[email protected]> wrote:
> Hi,
>
> adding Maxime.
>
> On 24/11/17 12:15, Chris Obbard wrote:
>> Hi andre,
>>
>> I used the orange pi pc2 dt  from mainline. Which hasn’t changed a while...
>>
>> I’ll try to find the commit I used that found the sd  card from last
>> week when I’m home....
>
> Mmh, I guess it's related to:
> commit 1396007286b1e2fd5dd10ae6a5ccaaaed51ab762
> Author: Maxime Ripard <[email protected]>
> Date:   Mon Oct 9 22:53:39 2017 +0200
>
>     pinctrl: sunxi: Enforce the strict mode by default
>
> This is probably due to the fact that we reference PF6 twice:
>
> arch/arm64/boot/dts/allwinner/sun50i-h5-orangepi-pc2.dts:
>> &mmc0 {
>>         pinctrl-names = "default";
>>         pinctrl-0 = <&mmc0_pins_a>, <&mmc0_cd_pin>;
>
> Once here:                            ^^^^^^^^^^^^^^
>

Drop this one.

>>         vmmc-supply = <&reg_vcc3v3>;
>>         bus-width = <4>;
>>         cd-gpios = <&pio 5 6 GPIO_ACTIVE_LOW>; /* PF6 */
>
> And then again here:  ^^^^^^^^
>

And keep this one.

ChenYu

>>         status = "okay";
>> };
>
> Maxime, can you say which one should stay?
>
> Cheers,
> Andre.
>
>> On Fri, 24 Nov 2017 at 12:13, Andre Przywara <[email protected]
>> <mailto:[email protected]>> wrote:
>>
>>     Hi,
>>
>>     On 24/11/17 11:58, Chris Obbard wrote:
>>     > [    2.982523] sun50i-h5-pinctrl 1c20800.pinctrl: pin PF6 already
>>     > requested by 1c0f000.mmc; cannot claim for 1c20800.pinctrl:166
>>     > [    2.993845] sun50i-h5-pinctrl 1c20800.pinctrl: pin-166
>>     > (1c20800.pinctrl:166) status -22
>>     > [    3.002001] sunxi-mmc: probe of 1c0f000.mmc failed with error -22
>>
>>     Did you change anything in the DT?
>>     Which DT do you actually use? Can you dump it here as well?
>>
>>     I will try it later tonight at home.
>>
>>     Cheers,
>>     Andre.
>>

-- 
You received this message because you are subscribed to the Google Groups 
"linux-sunxi" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to