From: Philipp Rossak <embed3d@gmail.com>
To: Maxime Ripard <maxime.ripard@free-electrons.com>
Cc: robh+dt@kernel.org, mark.rutland@arm.com, linux@armlinux.org.uk,
wens@csie.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-sunxi@googlegroups.com
Subject: Re: [PATCH 4/7] ARM: dts: sun8i: h3: Enable AP6212 WiFi on mmc1 on Nanopi M1 Plus
Date: Wed, 30 Aug 2017 23:51:37 +0200 [thread overview]
Message-ID: <89e3d5f8-1b31-bf86-4a6b-aee454c0b85f@gmail.com> (raw)
In-Reply-To: <20170830145211.snicbwdytobtd7ro@flea.lan>
Hi,
thanks for the feedback I will rework the patch.
Should I also update the sun8i-h3-bananapi-m2-plus.dts? It uses also the
AP6212 and it is done in the same way like in this patch.
Am 30.08.2017 um 16:52 schrieb Maxime Ripard:
> Hi,
>
> On Wed, Aug 30, 2017 at 05:01:07AM +0200, Philipp Rossak wrote:
>> From: Philipp Rossak <embed3d@gmail.com>
>>
>> The WiFi side of the AP6212 WiFi/BT combo module is connected to
>> mmc1. There are also GPIOs for enable and interrupts.
>>
>> Enable WiFi on this board by enabling mmc1 and adding the power
>> sequencing clocks and GPIO, as well as the chip's interrupt line.
>>
>> Signed-off-by: Philipp Rossak <embed3d@gmail.com>
>> ---
>> arch/arm/boot/dts/sun8i-h3-nanopi-m1-plus.dts | 35 +++++++++++++++++++++++++++
>> 1 file changed, 35 insertions(+)
>>
>> diff --git a/arch/arm/boot/dts/sun8i-h3-nanopi-m1-plus.dts b/arch/arm/boot/dts/sun8i-h3-nanopi-m1-plus.dts
>> index b9c6c27..3054308 100644
>> --- a/arch/arm/boot/dts/sun8i-h3-nanopi-m1-plus.dts
>> +++ b/arch/arm/boot/dts/sun8i-h3-nanopi-m1-plus.dts
>> @@ -48,6 +48,7 @@
>>
>> aliases {
>> ethernet0 = &emac;
>> + ethernet1 = &ap6212;
>> };
>>
>> reg_gmac_3v3: gmac-3v3 {
>> @@ -59,6 +60,14 @@
>> enable-active-high;
>> gpio = <&pio 3 6 GPIO_ACTIVE_HIGH>;
>> };
>> +
>> + wifi_pwrseq: wifi_pwrseq {
>> + compatible = "mmc-pwrseq-simple";
>> + pinctrl-names = "default";
>> + pinctrl-0 = <&wifi_en_npi_m1p>;
>
> There's no need for pinctrl nodes when the pin is set to a GPIO.
>
>> + reset-gpios = <&r_pio 0 7 GPIO_ACTIVE_LOW>; /* PL7 */
>> + };
>> +
>> };
>>
>> &ehci1 {
>> @@ -93,6 +102,25 @@
>> };
>> };
>>
>> +&mmc1 {
>> + pinctrl-names = "default";
>> + pinctrl-0 = <&mmc1_pins_a>;
>> + vmmc-supply = <®_vcc3v3>;
>> + vqmmc-supply = <®_vcc3v3>;
>
> You don't need vqmmc in this case.
>
>> + mmc-pwrseq = <&wifi_pwrseq>;
>> + bus-width = <4>;
>> + non-removable;
>> + status = "okay";
>> +
>> + ap6212: sdio_wifi@1 {
>
> You're sure you need a label here?
>
> Thanks!
> Maxime
>
next prev parent reply other threads:[~2017-08-30 21:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-30 3:01 [PATCH 0/7] [DTS] enable hardware for Nanopi M1 & " Philipp Rossak
2017-08-30 3:01 ` [PATCH 1/7] ARM: dts: sun8i: h3: nanopi-m1: Enable IR controller Philipp Rossak
2017-08-30 14:49 ` Maxime Ripard
2017-08-30 3:01 ` [PATCH 2/7] ARM: dts: sun8i: h3: nanopi-m1-plus: " Philipp Rossak
2017-08-30 14:50 ` Maxime Ripard
2017-08-30 3:01 ` [PATCH 3/7] ARM: dts: sun8i: h3: Enable dwmac-sun8i on the Nanopi M1 Plus Philipp Rossak
2017-08-30 8:27 ` Chen-Yu Tsai
2017-08-30 3:01 ` [PATCH 4/7] ARM: dts: sun8i: h3: Enable AP6212 WiFi on mmc1 on " Philipp Rossak
2017-08-30 14:52 ` Maxime Ripard
2017-08-30 21:51 ` Philipp Rossak [this message]
2017-09-01 13:00 ` Maxime Ripard
2017-08-30 3:01 ` [PATCH 5/7] ARM: dts: sun8i: h3: Enable dwmac-sun8i on the Nanopi M1 Philipp Rossak
2017-08-30 3:01 ` [PATCH 6/7] ARM: dts: sun8i: h3: Adding UART3 RTS and CTS Pins Philipp Rossak
2017-09-01 12:59 ` Maxime Ripard
2017-08-30 3:01 ` [PATCH 7/7] ARM: dts: sun8i: h3: Enable AP6212 BT on uart3 on Nanopi M1 Plus Philipp Rossak
2017-09-01 12:59 ` Maxime Ripard
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=89e3d5f8-1b31-bf86-4a6b-aee454c0b85f@gmail.com \
--to=embed3d@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@googlegroups.com \
--cc=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
--cc=maxime.ripard@free-electrons.com \
--cc=robh+dt@kernel.org \
--cc=wens@csie.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
all inboxes | Powered by JetHome®