From: Chen-Yu Tsai <wens@csie.org>
To: Maxime Ripard <maxime.ripard@free-electrons.com>
Cc: Chen-Yu Tsai <wens@csie.org>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/3] ARM: dts: sun9i: Enable SDIO-based WiFi
Date: Fri, 28 Oct 2016 18:11:51 +0800 [thread overview]
Message-ID: <20161028101154.7350-1-wens@csie.org> (raw)
Hi Maxime,
Now that we have support for both PMICs, we can turn on the
regulators needed for the onboard WiFi chips.
This is a fairly simple series. The WiFi chips themselves are
supported by the brcmfmac driver, but the user needs to get an
nvram.txt file and put it in their firmware directory, in
addition to the firmware file in linux-firmware. Otherwise we
just need to enable the mmc controller and supply the vmmc and
vqmmc regulators.
Regards
ChenYu
Chen-Yu Tsai (3):
ARM: dts: sun9i: Add mmc1 pinmux setting
ARM: dts: sun9i: a80-optimus: Enable AP6330 WiFi
ARM: dts: sun9i: cubieboard4: Enable AP6330 WiFi
arch/arm/boot/dts/sun9i-a80-cubieboard4.dts | 32 +++++++++++++++++++++++++++++
arch/arm/boot/dts/sun9i-a80-optimus.dts | 30 +++++++++++++++++++++++++++
arch/arm/boot/dts/sun9i-a80.dtsi | 8 ++++++++
3 files changed, 70 insertions(+)
--
2.9.3
next reply other threads:[~2016-10-28 10:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-28 10:11 Chen-Yu Tsai [this message]
[not found] ` <20161028101154.7350-1-wens-jdAy2FN1RRM@public.gmane.org>
2016-10-28 10:11 ` [PATCH 1/3] ARM: dts: sun9i: Add mmc1 pinmux setting Chen-Yu Tsai
2016-10-28 10:11 ` [PATCH 2/3] ARM: dts: sun9i: a80-optimus: Enable AP6330 WiFi Chen-Yu Tsai
2016-10-28 10:11 ` [PATCH 3/3] ARM: dts: sun9i: cubieboard4: " Chen-Yu Tsai
2016-11-02 13:32 ` [PATCH 0/3] ARM: dts: sun9i: Enable SDIO-based WiFi 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=20161028101154.7350-1-wens@csie.org \
--to=wens@csie.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maxime.ripard@free-electrons.com \
/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).