changes needed in Linux kernel to get WiFi+Bluetooth in life

This forum is for users of Microchip MPUs and who are interested in using Linux OS.

Moderator: nferre

pragneshpatel
Posts: 3
Joined: Fri Dec 04, 2020 12:52 pm

changes needed in Linux kernel to get WiFi+Bluetooth in life

Fri Dec 04, 2020 1:01 pm

Hi :D :D :D
our team has build sama5d3_xplained based board currently we are stuck at wifi+bt section.

we are using "Cypress CYW4343W" chipset below link given.
link https://wireless.murata.com/type-1dx.html

We are using buildroot-at91 (https://github.com/linux4sam/buildroot-at91).

now what changes needed in Linux kernel to get WiFi+Bluetooth in life.
blue_z
Location: USA
Posts: 2151
Joined: Thu Apr 19, 2007 10:15 pm

Re: changes needed in Linux kernel to get WiFi+Bluetooth in life

Tue Dec 08, 2020 12:19 am

What have you tried?
pragneshpatel
Posts: 3
Joined: Fri Dec 04, 2020 12:52 pm

Re: changes needed in Linux kernel to get WiFi+Bluetooth in life

Tue Dec 08, 2020 3:03 pm

First we chnaged/added dts "at91-sama5d3_xplained.dts" file

Code: Select all

mmc1: mmc@f8000000 {
	pinctrl-0 = <&pinctrl_mmc1_clk_cmd_dat0 &pinctrl_mmc1_dat1_3 &pinctrl_mmc1_cd>;
	pinctrl-names = "default", "opendrain", "sleep";
	vmmc-supply = <&vcc_3v3_reg>;
	vqmmc-supply = <&vcc_3v3_reg>;
	mmc-pwrseq = <&wifi_pwrseq>;
	#address-cells = <1>;
	#size-cells = <0>;
	status = "disabled";
	slot@0 {
		reg = <0>;
		bus-width = <4>;
		cd-gpios = <&pioE 1 GPIO_ACTIVE_LOW>;
		non-removable;
		st,neg-edge;
	};
	brcmf: bcrmf@0 {
		reg = <0>;
		compatible = "brcm,bcm4329-fmac";
	};				
};
Then below link section "3 Configuration" applied
https://wiki.st.com/stm32mpu/wiki/WLAN_overview

actually, I am not getting the mmc1 sdio interface.
blue_z
Location: USA
Posts: 2151
Joined: Thu Apr 19, 2007 10:15 pm

Re: changes needed in Linux kernel to get WiFi+Bluetooth in life

Thu Dec 10, 2020 1:02 am

pragneshpatel wrote: First we chnaged/added dts "at91-sama5d3_xplained.dts" file

Code: Select all

mmc1: mmc@f8000000 {
        ...  
    	status = "disabled";
	slot@0 {
	        reg = <0>;
		...
	};
	brcmf: bcrmf@0 {
	        reg = <0>;
		...  
	};				
};
...
actually, I am not getting the mmc1 sdio interface.
When you disable a node, then you cannot expect that device to be active.
You also have two child nodes (slot and brcmf) at the same address (@0), which will conflict.
Why are you (unnecessarily) replicating mmc node properties such as #address-cells and #size-cells?

Regards

Return to “LINUX”

Who is online

Users browsing this forum: No registered users and 6 guests