linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: heiko@sntech.de (Heiko Stuebner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/3] arm64: dts: rockchip: add WiFi module support for Firefly-RK3399
Date: Wed, 25 Jul 2018 13:02:44 +0200	[thread overview]
Message-ID: <10441742.bRvTIUQldp@phil> (raw)
In-Reply-To: <PS2P216MB05327A3B7901DEE585B0BA21D1530@PS2P216MB0532.KORP216.PROD.OUTLOOK.COM>

Hi,

Am Mittwoch, 18. Juli 2018, 16:58:16 CEST schrieb Maruyama Shohei:
> From: Shohei Maruyama <cheat.sc.linux@outlook.com>
> 
> This commit adds WiFi module support for the Firefly-RK3399.
> 
> Signed-off-by: Shohei Maruyama <cheat.sc.linux@outlook.com>

[...]

> +	/* Card detection */
> +	cd-gpios = <&gpio2 RK_PD2 GPIO_ACTIVE_LOW>;
> +
> +	/* Write protection */
> +	wp-gpios = <&gpio0 RK_PA3 GPIO_ACTIVE_HIGH>;

these two gpio connections look not correct. According to
the schematics, gpio2_d2 is bt_wake_l and gpio0_a3 is
wifi_host_wake_l, so definitly properties of the wifi module
below and not the sdio controller itself.


> +	brcmf: wifi at 1 {
> +		compatible = "brcm,bcm4329-fmac";
> +		brcm,drive-strength = <5>;
> +		interrupt-parent = <&gpio0>;
> +		interrupts = <RK_PA4 GPIO_ACTIVE_HIGH>;

And this seems to be bt_host_wake_l, so not sure
if this is the correct one from the module's point of view.


> +		interrupt-names = "host-wake";
> +	};
> +};


Heiko

      reply	other threads:[~2018-07-25 11:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-18 14:58 [PATCH 1/3] arm64: dts: rockchip: add WiFi module support for Firefly-RK3399 Maruyama Shohei
2018-07-25 11:02 ` Heiko Stuebner [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=10441742.bRvTIUQldp@phil \
    --to=heiko@sntech.de \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).