From: Devarsh Thakkar <devarsht@ti.com>
To: Aparna M <a-m1@ti.com>, <nm@ti.com>, <vigneshr@ti.com>,
<kishon@ti.com>, <kristo@kernel.org>, <robh+dt@kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Cc: <praneeth@ti.com>, <nikhil.nd@ti.com>
Subject: Re: [RESEND PATCH v3] arm64: dts: ti: k3-am642-sk: Enable WLAN connected to SDHCI0
Date: Thu, 28 Apr 2022 14:52:43 +0530 [thread overview]
Message-ID: <4d9da502-52b5-e5c1-7675-93c4341fb446@ti.com> (raw)
In-Reply-To: <20220414133612.13365-1-a-m1@ti.com>
On 14/04/22 19:06, Aparna M wrote:
> From: Kishon Vijay Abraham I <kishon@ti.com>
>
> WL1837 module is connected to SDHCI0 in AM642 SK. Enable it here.
> This will enable the WiFi functionaliy on the board.
>
> Signed-off-by: Kishon Vijay Abraham I <kishon@ti.com>
> Signed-off-by: Vignesh Raghavendra <vigneshr@ti.com>
> Signed-off-by: Nikhil Devshatwar <nikhil.nd@ti.com>
> Signed-off-by: Aparna M <a-m1@ti.com>
Tested-by: Devarsh Thakkar <devarsht@ti.com>
> ---
>
> v3 RESEND: rebased on top of v5.18-rc2
> v2 -> v3: Use generic node names for the regulators as per DT Specs
> v1 -> v2: Add "From" tag in commit message
>
> arch/arm64/boot/dts/ti/k3-am642-sk.dts | 62 ++++++++++++++++++++++++++
> 1 file changed, 62 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/ti/k3-am642-sk.dts b/arch/arm64/boot/dts/ti/k3-am642-sk.dts
> index 1d7db8bf3a5c..59f506cbd275 100644
> --- a/arch/arm64/boot/dts/ti/k3-am642-sk.dts
> +++ b/arch/arm64/boot/dts/ti/k3-am642-sk.dts
> @@ -125,6 +125,31 @@
> vin-supply = <&vcc_3v3_sys>;
> gpio = <&exp1 3 GPIO_ACTIVE_HIGH>;
> };
> +
> + com8_ls_en: regulator-1 {
> + compatible = "regulator-fixed";
> + regulator-name = "com8_ls_en";
> + regulator-min-microvolt = <3300000>;
> + regulator-max-microvolt = <3300000>;
> + regulator-always-on;
> + regulator-boot-on;
> + pinctrl-0 = <&main_com8_ls_en_pins_default>;
> + pinctrl-names = "default";
> + gpio = <&main_gpio0 62 GPIO_ACTIVE_LOW>;
> + };
> +
> + wlan_en: regulator-2 {
> + /* output of SN74AVC4T245RSVR */
> + compatible = "regulator-fixed";
> + regulator-name = "wlan_en";
> + regulator-min-microvolt = <1800000>;
> + regulator-max-microvolt = <1800000>;
> + enable-active-high;
> + pinctrl-0 = <&main_wlan_en_pins_default>;
> + pinctrl-names = "default";
> + vin-supply = <&com8_ls_en>;
> + gpio = <&main_gpio0 48 GPIO_ACTIVE_HIGH>;
> + };
> };
>
> &main_pmx0 {
> @@ -216,6 +241,23 @@
> AM64X_IOPAD(0x0270, PIN_INPUT, 0) /* (D18) ECAP0_IN_APWM_OUT */
> >;
> };
> + main_wlan_en_pins_default: main-wlan-en-pins-default {
> + pinctrl-single,pins = <
> + AM64X_IOPAD(0x00c4, PIN_OUTPUT_PULLUP, 7) /* (V8) GPIO0_48 */
> + >;
> + };
> +
> + main_com8_ls_en_pins_default: main-com8-ls-en-pins-default {
> + pinctrl-single,pins = <
> + AM64X_IOPAD(0x00fc, PIN_OUTPUT, 7) /* (U7) PRG1_PRU0_GPO17.GPIO0_62 */
> + >;
> + };
> +
> + main_wlan_pins_default: main-wlan-pins-default {
> + pinctrl-single,pins = <
> + AM64X_IOPAD(0x00bc, PIN_INPUT, 7) /* (U8) GPIO0_46 */
> + >;
> + };
> };
>
> &mcu_uart0 {
> @@ -293,6 +335,26 @@
> status = "reserved";
> };
>
> +&sdhci0 {
> + vmmc-supply = <&wlan_en>;
> + bus-width = <4>;
> + non-removable;
> + cap-power-off-card;
> + keep-power-in-suspend;
> + ti,driver-strength-ohm = <50>;
> +
> + #address-cells = <1>;
> + #size-cells = <0>;
> + wlcore: wlcore@2 {
> + compatible = "ti,wl1837";
> + reg = <2>;
> + pinctrl-0 = <&main_wlan_pins_default>;
> + pinctrl-names = "default";
> + interrupt-parent = <&main_gpio0>;
> + interrupts = <46 IRQ_TYPE_EDGE_FALLING>;
> + };
> +};
> +
> &sdhci1 {
> /* SD/MMC */
> vmmc-supply = <&vdd_mmc1>;
prev parent reply other threads:[~2022-04-28 9:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-14 13:36 Aparna M
2022-04-19 16:53 ` Bryan Brattlof
2022-04-27 15:18 ` Vignesh Raghavendra
2022-04-28 9:22 ` Devarsh Thakkar [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=4d9da502-52b5-e5c1-7675-93c4341fb446@ti.com \
--to=devarsht@ti.com \
--cc=a-m1@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=kishon@ti.com \
--cc=kristo@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nikhil.nd@ti.com \
--cc=nm@ti.com \
--cc=praneeth@ti.com \
--cc=robh+dt@kernel.org \
--cc=vigneshr@ti.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
all inboxes | Powered by JetHome®