Linux-Rockchip Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Johan Jonker <jbx6244-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: Re: [PATCH 8/8] arm64: dts: rockchip: RockPro64: enable wifi module at sdio0
Date: Mon, 16 Dec 2019 14:16:10 +0100	[thread overview]
Message-ID: <d0f22c28-4c61-3901-0b81-fd2c65879b44@gmail.com> (raw)
In-Reply-To: <20191209223822.27236-8-smoch-S0/GAf8tV78@public.gmane.org>

Hi Soeren,

> diff --git a/arch/arm64/boot/dts/rockchip/rk3399-rockpro64.dts b/arch/arm64/boot/dts/rockchip/rk3399-rockpro64.dts
> index 7f4b2eba31d4..9fa92790d6e0 100644
> --- a/arch/arm64/boot/dts/rockchip/rk3399-rockpro64.dts
> +++ b/arch/arm64/boot/dts/rockchip/rk3399-rockpro64.dts

> +&sdio0 {
> +	bus-width = <4>;
> +	cap-sd-highspeed;
> +	cap-sdio-irq;

> +	disable-wp;

The mmc-controller.yaml didn't explicitly say disable-wp is for SD card
slot only, but that is what it was designed for in the first place.
Remove all disable-wp from emmc or sdio controllers.

> +	keep-power-in-suspend;
> +	mmc-pwrseq = <&sdio_pwrseq>;
> +	non-removable;
> +	pinctrl-names = "default";
> +	pinctrl-0 = <&sdio0_bus4 &sdio0_cmd &sdio0_clk>;
> +	sd-uhs-sdr104;
> +	status = "okay";
> +};

      parent reply	other threads:[~2019-12-16 13:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20191209223822.27236-1-smoch@web.de>
2019-12-09 22:38 ` [PATCH 8/8] arm64: dts: rockchip: RockPro64: enable wifi module at sdio0 Soeren Moch
2019-12-09 23:08   ` Heiko Stübner
2019-12-09 23:29     ` Soeren Moch
2019-12-10  1:18       ` Heiko Stübner
2019-12-10  9:14         ` Kalle Valo
2019-12-10  9:14         ` Kalle Valo
2019-12-10 10:08         ` Soeren Moch
2019-12-10 10:13           ` Heiko Stübner
     [not found]             ` <5d3bde69-9102-cc81-c1d2-d71b60258906@web.de>
2019-12-11 15:50               ` Soeren Moch
     [not found]         ` <0101016eef171394-2c71e1b8-45b9-4e38-96f9-2841dd0607ba-000000@us-west-2.amazonses.com>
     [not found]           ` <0101016eef171394-2c71e1b8-45b9-4e38-96f9-2841dd0607ba-000000-j0qUFrXf9azQVAzzCBYphlNw9kRHFGba@public.gmane.org>
2019-12-10 10:15             ` Soeren Moch
     [not found]   ` <20191209223822.27236-8-smoch-S0/GAf8tV78@public.gmane.org>
2019-12-16 13:16     ` Johan Jonker [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=d0f22c28-4c61-3901-0b81-fd2c65879b44@gmail.com \
    --to=jbx6244-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox