Yixun Lan <yixun.lan@xxxxxxxxxxx> writes: > The Meson-AXG S400 board is shipped with AP6255 wifi module, > which is actually using the brcmfmac 43455 driver. > > Signed-off-by: Yixun Lan <yixun.lan@xxxxxxxxxxx> > --- > .../arm64/boot/dts/amlogic/meson-axg-s400.dts | 44 ++++++++++++++++++- > 1 file changed, 43 insertions(+), 1 deletion(-) > > diff --git a/arch/arm64/boot/dts/amlogic/meson-axg-s400.dts b/arch/arm64/boot/dts/amlogic/meson-axg-s400.dts > index f67d4e47e641..b3e1bdca32bb 100644 > --- a/arch/arm64/boot/dts/amlogic/meson-axg-s400.dts > +++ b/arch/arm64/boot/dts/amlogic/meson-axg-s400.dts > @@ -51,7 +51,16 @@ > > sdio_pwrseq: sdio-pwrseq { > compatible = "mmc-pwrseq-simple"; > - reset-gpios = <&gpio GPIOX_6 GPIO_ACTIVE_LOW>; > + reset-gpios = <&gpio GPIOX_7 GPIO_ACTIVE_LOW>; You didn't mention this GPIO change in the changelog. Is it intentional? Kevin > + clocks = <&wifi32k>; > + clock-names = "ext_clock"; > + }; > + > + wifi32k: wifi32k { > + compatible = "pwm-clock"; > + #clock-cells = <0>; > + clock-frequency = <32768>; > + pwms = <&pwm_ab 0 30518 0>; /* PWM_A at 32.768KHz */ > }; > }; > > @@ -86,6 +95,12 @@ > pinctrl-names = "default"; > }; > > +&pwm_ab { > + status = "okay"; > + pinctrl-0 = <&pwm_a_x20_pins>; > + pinctrl-names = "default"; > +}; > + > /* emmc storage */ > &sd_emmc_c { > status = "okay"; > @@ -105,3 +120,30 @@ > vmmc-supply = <&vcc_3v3>; > vqmmc-supply = <&vddio_boot>; > }; > + > +/* wifi module */ > +&sd_emmc_b { > + status = "okay"; > + #address-cells = <1>; > + #size-cells = <0>; > + > + pinctrl-0 = <&sdio_pins>; > + pinctrl-1 = <&sdio_clk_gate_pins>; > + pinctrl-names = "default", "clk-gate"; > + > + bus-width = <4>; > + cap-sd-highspeed; > + max-frequency = <100000000>; > + non-removable; > + disable-wp; > + > + mmc-pwrseq = <&sdio_pwrseq>; > + > + vmmc-supply = <&vddao_3v3>; > + vqmmc-supply = <&vddio_boot>; > + > + brcmf: wifi@1 { > + reg = <1>; > + compatible = "brcm,bcm4329-fmac"; > + }; > +}; -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html