From: Heiko Stuebner <heiko@sntech.de>
To: krzysztof.kozlowski+dt@linaro.org, piotr.oniszczuk@gmail.com,
robh+dt@kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-rockchip@lists.infradead.org,
Andy Yan <andyshrk@163.com>
Cc: Andy Yan <andyshrk@163.com>
Subject: Re: [PATCH 2/2] arm64: dts: rockchip: Enable wifi module AP6398s for rk3566 box demo
Date: Wed, 28 Dec 2022 20:21:32 +0100 [thread overview]
Message-ID: <17226287.uLZWGnKmhe@phil> (raw)
In-Reply-To: <20221225114953.3518595-1-andyshrk@163.com>
Hi Andy,
Am Sonntag, 25. Dezember 2022, 12:49:53 CET schrieb Andy Yan:
> There is a AP6398s wifi/bt module on this board.
> Fix the sdmmc1 dt node to make wifi work.
>
> Fixes: 2e0537b16b25 ("arm64: dts: rockchip: Add dts for rockchip rk3566 box demo board")
>
> Signed-off-by: Andy Yan <andyshrk@163.com>
> ---
>
> .../boot/dts/rockchip/rk3566-box-demo.dts | 26 ++++++++++++++++---
> 1 file changed, 22 insertions(+), 4 deletions(-)
>
> diff --git a/arch/arm64/boot/dts/rockchip/rk3566-box-demo.dts b/arch/arm64/boot/dts/rockchip/rk3566-box-demo.dts
> index d956496d5221..6c0c24226b52 100644
> --- a/arch/arm64/boot/dts/rockchip/rk3566-box-demo.dts
> +++ b/arch/arm64/boot/dts/rockchip/rk3566-box-demo.dts
> @@ -324,8 +324,12 @@ wifi_enable_h: wifi-enable-h {
> rockchip,pins = <2 RK_PB1 RK_FUNC_GPIO &pcfg_pull_none>;
> };
>
> + wifi_host_wake_h: wifi-host-wake-l {
> + rockchip,pins = <2 RK_PB2 RK_FUNC_GPIO &pcfg_pull_none>;
> + };
> +
> wifi_32k: wifi-32k {
> - rockchip,pins = <0 RK_PB0 2 &pcfg_pull_none>;
> + rockchip,pins = <2 RK_PC6 1 &pcfg_pull_none>;
> };
> };
>
> @@ -391,16 +395,30 @@ &sdmmc0 {
> };
>
> &sdmmc1 {
> + /* WiFi & BT combo module AMPAK AP6398S */
> + #address-cells = <1>;
> + #size-cells = <0>;
> bus-width = <4>;
> + clock-frequency = <150000000>;
> + cap-sdio-irq;
> cap-sd-highspeed;
> - disable-wp;
> + sd-uhs-sdr104;
> + keep-power-in-suspend;
> mmc-pwrseq = <&sdio_pwrseq>;
> non-removable;
> pinctrl-names = "default";
> pinctrl-0 = <&sdmmc1_bus4 &sdmmc1_cmd &sdmmc1_clk>;
> - vmmc-supply = <&vcc_3v3>;
> - vqmmc-supply = <&vcca_1v8>;
why are you removing the mmc-supplies here?
The supplies needed for mmc to work should very much be present
I think, especially to also make sure something else doesn't
turn them off.
Heiko
> status = "okay";
> +
> + brcmf: wifi@1 {
> + compatible = "brcm,bcm4329-fmac";
> + reg = <1>;
> + interrupt-parent = <&gpio2>;
> + interrupts = <RK_PB2 GPIO_ACTIVE_HIGH>;
> + interrupt-names = "host-wake";
> + pinctrl-names = "default";
> + pinctrl-0 = <&wifi_host_wake_h>;
> + };
> };
>
> &spdif {
>
next prev parent reply other threads:[~2022-12-28 19:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-25 11:49 [PATCH 0/2] rk3566 box demo io domain and network fix Andy Yan
2022-12-25 11:49 ` [PATCH 1/2] arm64: dts: rockchip: rk3566-box-demo: add io domain setting Andy Yan
2022-12-25 11:49 ` [PATCH 2/2] arm64: dts: rockchip: Enable wifi module AP6398s for rk3566 box demo Andy Yan
2022-12-28 19:21 ` Heiko Stuebner [this message]
2022-12-29 11:55 ` Andy Yan
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=17226287.uLZWGnKmhe@phil \
--to=heiko@sntech.de \
--cc=andyshrk@163.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=piotr.oniszczuk@gmail.com \
--cc=robh+dt@kernel.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).