lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Message-ID: <20200227184025.GB3353@tuxdriver.com>
Date:   Thu, 27 Feb 2020 13:40:25 -0500
From:   "John W. Linville" <linville@...driver.com>
To:     "Singh, Varunpratap" <Varunpratap.Singh@...rtwirelesscompute.com>
Cc:     "grant.likely@...aro.org" <grant.likely@...aro.org>,
        "robh+dt@...nel.org" <robh+dt@...nel.org>,
        "linux-wireless@...r.kernel.org" <linux-wireless@...r.kernel.org>,
        "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
        "Nagaraj, Vinay" <Vinay.Nagaraj@...rtwirelesscompute.com>
Subject: Re: Query: CNSS WLAN.

Varun,

Unfortunately, your questions is well outside of my areas of skill and
expertise. Hopefully Grant or someone else in your distribution list
will be more helpful.

Best regards!

John

On Thu, Feb 27, 2020 at 03:25:16PM +0000, Singh, Varunpratap wrote:
> Hi John,
> 
> I am trying to bring up two wifi-modules simultaneously, on Qualcomm Snapdragon SD820 processor and the Kernel version is 3.18.
> I connected the modules on PCIe_0 & PCIe_1.
> 
> As per my understanding the following device tree structure is responsible for driver probing.
> qcom,cnss {
>         compatible = "qcom,cnss";
>         wlan-bootstrap-gpio = <&tlmm 46 0>;
>         vdd-wlan-en-supply = <&wlan_en_vreg>;
>         vdd-wlan-supply = <&rome_vreg>;
>         vdd-wlan-io-supply = <&pm8994_s4>;
>         vdd-wlan-xtal-supply = <&pm8994_l30>;
>         vdd-wlan-core-supply = <&pm8994_s3>;
>         wlan-ant-switch-supply = <&pm8994_l18_pin_ctrl>;
>         qcom,wlan-en-vreg-support;
>         qcom,enable-bootstrap-gpio;
>         qcom,notify-modem-status;
>         pinctrl-names = "bootstrap_active", "bootstrap_sleep";
>         pinctrl-0 = <&cnss_bootstrap_active>;
>         pinctrl-1 = <&cnss_bootstrap_sleep>;
>         qcom,wlan-rc-num = <0>;
>         qcom,wlan-ramdump-dynamic = <0x200000>;
> 
>         qcom,msm-bus,name = "msm-cnss";
>         qcom,msm-bus,num-cases = <4>;
>         qcom,msm-bus,num-paths = <1>;
>         qcom,msm-bus,vectors-KBps =
>         /* No vote */
>                 <45 512 0 0>,
>                 /* Up to 200 Mbps */
>                 <45 512 41421 1520000>,
>                 /* Up to 400 Mbps */
>                 <45 512 96650 1520000>,
>                 /* Up to 800 Mbps */
>                 <45 512 207108 14432000>;
> };
> 
> Currently if I change the "qcom,wlan-rc-num = <0>;" to "qcom,wlan-rc-num = <1>;" the module connected on PCIe_1 will start working and vice-versa. But as per the requirement we need two probe getting succeeded i.e both the modules should be registered. Please, suggest how can I create two different nodes under cnss structure.
> 
> Any suggestion will be valuable.
> 
> 
> 
> With Regards,
> Varun Pratap Singh
> Software Engineer.

-- 
John W. Linville		Someday the world will need a hero, and you
linville@...driver.com			might be all we have.  Be ready.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ