From: Wei Ni <wni@nvidia.com>
To: swarren@wwwdotorg.org, brudley@broadcom.com, rvossen@broadcom.com
Cc: krakesh@nvidia.com, ldewangan@nvidia.com,
linux-tegra@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org,
brcm80211-dev-list@broadcom.com, Wei Ni <wni@nvidia.com>
Subject: [PATCH 4/6] ARM: dt: t20 ventana: set pinmux and power for wlan
Date: Mon, 27 Aug 2012 18:25:12 +0800 [thread overview]
Message-ID: <1346063114-30361-5-git-send-email-wni@nvidia.com> (raw)
In-Reply-To: <1346063114-30361-1-git-send-email-wni@nvidia.com>
Configure pinmux as required for WiFi.
Enable the SDHCI1 controller, which is connectted to the WiFi module.
Signed-off-by: Wei Ni <wni@nvidia.com>
---
arch/arm/boot/dts/tegra20-ventana.dts | 15 +++++++++++++++
1 files changed, 15 insertions(+), 0 deletions(-)
diff --git a/arch/arm/boot/dts/tegra20-ventana.dts b/arch/arm/boot/dts/tegra20-ventana.dts
index 4ec6b4c..3cbe54c 100644
--- a/arch/arm/boot/dts/tegra20-ventana.dts
+++ b/arch/arm/boot/dts/tegra20-ventana.dts
@@ -237,6 +237,16 @@
"ld23_22";
nvidia,pull = <1>;
};
+ drive_sdio1 {
+ nvidia,pins = "drive_sdio1";
+ nvidia,high-speed-mode = <0>;
+ nvidia,schmitt = <1>;
+ nvidia,low-power-mode = <3>;
+ nvidia,pull-down-strength = <31>;
+ nvidia,pull-up-strength = <31>;
+ nvidia,slew-rate-rising = <3>;
+ nvidia,slew-rate-falling = <3>;
+ };
};
};
@@ -454,6 +464,11 @@
status = "okay";
};
+ sdhci@c8000000 {
+ status = "okay";
+ power-gpios = <&gpio 86 0>; /* gpio PK6 */
+ };
+
sdhci@c8000400 {
status = "okay";
cd-gpios = <&gpio 69 0>; /* gpio PI5 */
--
1.7.1
next prev parent reply other threads:[~2012-08-27 10:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-27 10:25 [PATCH 0/6] ARM: tegra: enable wlan for t20 and t30 Wei Ni
[not found] ` <1346063114-30361-1-git-send-email-wni-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2012-08-27 10:25 ` [PATCH 1/6] ARM: tegra: set up wlan clocks for tegra dt Wei Ni
2012-08-27 10:25 ` [PATCH 2/6] brcmfmac: Handling the interrupt in ISR directly for non-OOB Wei Ni
[not found] ` <1346063114-30361-3-git-send-email-wni-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2012-08-27 16:24 ` Arend van Spriel
2012-08-27 20:06 ` Stephen Warren
[not found] ` <503BD345.6030501-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2012-08-28 11:13 ` Wei Ni
2012-08-28 16:45 ` Franky Lin
[not found] ` <503CF5B3.8040201-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>
2012-08-28 22:39 ` Stephen Warren
2012-08-28 23:01 ` Franky Lin
[not found] ` <503D4DD9.2060808-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>
2012-08-28 23:04 ` Stephen Warren
[not found] ` <503D4E7F.9010205-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2012-08-28 23:10 ` Franky Lin
[not found] ` <503B9F31.5050502-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>
2012-08-28 6:08 ` Wei Ni
2012-08-27 10:25 ` [PATCH 3/6] ARM: dt: t20 seaboard: turn on the power for wlan Wei Ni
2012-08-27 10:25 ` Wei Ni [this message]
2012-08-27 10:25 ` [PATCH 5/6] ARM: dt: t30 cardhu: set pinmux and " Wei Ni
2012-08-27 10:25 ` [PATCH 6/6] ARM: tegra: enable wireless in defconfig Wei Ni
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=1346063114-30361-5-git-send-email-wni@nvidia.com \
--to=wni@nvidia.com \
--cc=brcm80211-dev-list@broadcom.com \
--cc=brudley@broadcom.com \
--cc=krakesh@nvidia.com \
--cc=ldewangan@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=rvossen@broadcom.com \
--cc=swarren@wwwdotorg.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).