Re: [beagleboard] Wl12xx
Hi Raghu,
you should use &mmc3.
Because of other work, currently we are not working on that. still we need
to debug SDIO communication on hardware line.
Regards,
Dileep
On Wed, Sep 16, 2015 at 4:55 PM, wrote:
> Hi Dileep,
>
> I am also trying to bring up wl12xx based on BBB kernel. Is there any
> update on this ?
>
> Do we need to use &mmc2 or & mmc3 ?
>
> Thanks & Regard
> Raghu Ramaraj
>
>
>
>
>
> On Saturday, August 29, 2015 at 12:56:08 AM UTC+5:30, lisarden wrote:
>>
>> Enable dummy regulators in the kernel
>> 28 Авг 2015 г. 14:30 пользователь "Iain Hunter"
>> написал:
>>
>>> Hi
>>>
>>> This is not good. You have tried to start mmc3 but it failed to get a
>>> regulator, so may not have continued its initialisation - i don't know how
>>> driver behaves in this case.
>>> omap_hsmmc 4781.mmc: unable to get vmmc regulator -517
>>>
>>> So suggestion would be to trace omap_hsmmc driver to understand why it
>>> fails to get a regulator.
>>> Iain
>>>
>>> On 28 August 2015 at 04:34, Dileep wrote:
>>>
Hi lain,
I have configured MMC3 for SDIO communiction. but still sdio
communication is not up.
If clock is not enabled by default for MMC3 how can it be done in
device tree,
dmesg log shows:
[4.259093] omap_hsmmc 4781.mmc: unable to get vmmc regulator
-517
Device tree configurations.
wl12xx_vmmc: fixedregulator@2 {
pinctrl-names = "default";
pinctrl-0 = <&wl12xx_gpio>;
compatible = "regulator-fixed";
regulator-name = "vwl1271";
regulator-min-microvolt = <180>;
regulator-max-microvolt = <180>;
gpio = <&gpio0 27 0>;
startup-delay-us = <7>;
enable-active-high;
};
mmc3_pins: pinmux_mmc3_pins {
pinctrl-single,pins = <
0x3C (PIN_INPUT_PULLUP | MUX_MODE3) /* mmc2_dat3 */
0x38 (PIN_INPUT_PULLUP | MUX_MODE3) /* mmc2_dat2 */
0x34 (PIN_INPUT_PULLUP | MUX_MODE3) /* mmc2_dat1 */
0x30 (PIN_INPUT_PULLUP | MUX_MODE3) /* mmc2_dat0 */
0x8c (PIN_INPUT_PULLUP | MUX_MODE3) /* mmc2_clk */
0x88 (PIN_INPUT_PULLUP | MUX_MODE3) /* mmc2_cmd */
>;
};
&mmc3 {
/* these are on the crossbar and are outlined in the
xbar-event-map element */
dmas = <&edma 32 &edma 33>;
dma-names = "tx", "rx";
status = "okay";
vmmc-supply = <&wl12xx_vmmc>;
ti,non-removable;
bus-width = <4>;
cap-power-off-card;
pinctrl-names = "default";
pinctrl-0 = <&mmc3_pins>;
#address-cells = <1>;
#size-cells = <0>;
wlcore: wlcore@2 {
compatible = "ti,wl1271";
reg = <2>;
interrupt-parent = <&gpio0>;
interrupts = <26 0x4>; /* gpio 31 */
ref-clock-frequency = <3840>;
};
};
&edma {
ti,edma-xbar-event-map = /bits/ 16 <1 32 2 33>;
};
On Thu, Aug 27, 2015 at 10:03 PM, Iain Hunter
wrote:
> Did you use device tree in the end or modify a board.c?
> If so that looks like the mmc port is not being probed correctly as it
> is not defined. You should at least get some activity on mmc to try and
> read the type of "sd card" on this bus. This should identify as a wl12xx
> and then load the drivers when you insmod wlcore_sdio
> Iain
>
> On 26 August 2015 at 09:56, Dileep wrote:
>
>> Hi,
>>
>> When i add wl12xx module, none of the functions from wl12xx and
>> wlcore are getting called.
>>
>> logs:
>> root@arm:~# modprobe wlcore_sdio
>> [ 48.682409]
>> [ 48.682409] ** wl1271_init
>> [ 48.690385]
>> [ 48.690385] ** sdio_register_driver
>> [ 48.708615]
>> [ 48.708615] ** sdio_register_driver : wl1271_sdio
>>
>> root@arm:~# modprobe wl12xx
>> [ 57.901415]
>> [ 57.901415] ** Country : COUNTRY=00 *
>> [ 57.908006] cfg80211: Calling CRDA to update world regulatory
>> domain
>> [ 58.061324]
>> [ 58.061324] ** ieee80211_init
>> [ 58.067658]
>> [ 58.067658] ** ieee80211_init 1
>> [ 58.076820]
>> [ 58.076820] ** ieee80211_init 2
>> [ 58.086826]
>> [ 58.086826] ** ieee80211_init 3
>> root@arm:~# [ 58.207791] cfg80211: World regulatory domain updated:
>> [ 58.213206] cfg80211: DFS Master region: unset
>> [ 58.217588] cfg80211: (start_freq - end_freq @ bandwidth),
>> (max_antenna_gain, max_eirp), (dfs_cac_time)
>> [ 58.229554] cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz),
>> (N/A,
Re: [beagleboard] Wl12xx
Hi Dileep,
I am also trying to bring up wl12xx based on BBB kernel. Is there any
update on this ?
Do we need to use &mmc2 or & mmc3 ?
Thanks & Regard
Raghu Ramaraj
On Saturday, August 29, 2015 at 12:56:08 AM UTC+5:30, lisarden wrote:
>
> Enable dummy regulators in the kernel
> 28 Авг 2015 г. 14:30 пользователь "Iain Hunter" > написал:
>
>> Hi
>>
>> This is not good. You have tried to start mmc3 but it failed to get a
>> regulator, so may not have continued its initialisation - i don't know how
>> driver behaves in this case.
>> omap_hsmmc 4781.mmc: unable to get vmmc regulator -517
>>
>> So suggestion would be to trace omap_hsmmc driver to understand why it
>> fails to get a regulator.
>> Iain
>>
>> On 28 August 2015 at 04:34, Dileep >
>> wrote:
>>
>>> Hi lain,
>>>
>>> I have configured MMC3 for SDIO communiction. but still sdio
>>> communication is not up.
>>>
>>> If clock is not enabled by default for MMC3 how can it be done in device
>>> tree,
>>>
>>> dmesg log shows:
>>> [4.259093] omap_hsmmc 4781.mmc: unable to get vmmc regulator -517
>>>
>>>
>>> Device tree configurations.
>>>
>>> wl12xx_vmmc: fixedregulator@2 {
>>> pinctrl-names = "default";
>>> pinctrl-0 = <&wl12xx_gpio>;
>>> compatible = "regulator-fixed";
>>> regulator-name = "vwl1271";
>>> regulator-min-microvolt = <180>;
>>> regulator-max-microvolt = <180>;
>>> gpio = <&gpio0 27 0>;
>>> startup-delay-us = <7>;
>>> enable-active-high;
>>> };
>>>
>>> mmc3_pins: pinmux_mmc3_pins {
>>> pinctrl-single,pins = <
>>> 0x3C (PIN_INPUT_PULLUP | MUX_MODE3) /* mmc2_dat3 */
>>> 0x38 (PIN_INPUT_PULLUP | MUX_MODE3) /* mmc2_dat2 */
>>> 0x34 (PIN_INPUT_PULLUP | MUX_MODE3) /* mmc2_dat1 */
>>> 0x30 (PIN_INPUT_PULLUP | MUX_MODE3) /* mmc2_dat0 */
>>> 0x8c (PIN_INPUT_PULLUP | MUX_MODE3) /* mmc2_clk */
>>> 0x88 (PIN_INPUT_PULLUP | MUX_MODE3) /* mmc2_cmd */
>>> >;
>>> };
>>>
>>> &mmc3 {
>>> /* these are on the crossbar and are outlined in the
>>> xbar-event-map element */
>>> dmas = <&edma 32 &edma 33>;
>>> dma-names = "tx", "rx";
>>>
>>> status = "okay";
>>> vmmc-supply = <&wl12xx_vmmc>;
>>> ti,non-removable;
>>> bus-width = <4>;
>>> cap-power-off-card;
>>> pinctrl-names = "default";
>>> pinctrl-0 = <&mmc3_pins>;
>>>
>>> #address-cells = <1>;
>>> #size-cells = <0>;
>>> wlcore: wlcore@2 {
>>> compatible = "ti,wl1271";
>>> reg = <2>;
>>> interrupt-parent = <&gpio0>;
>>> interrupts = <26 0x4>; /* gpio 31 */
>>> ref-clock-frequency = <3840>;
>>> };
>>> };
>>>
>>> &edma {
>>> ti,edma-xbar-event-map = /bits/ 16 <1 32 2 33>;
>>> };
>>>
>>> On Thu, Aug 27, 2015 at 10:03 PM, Iain Hunter >> > wrote:
>>>
Did you use device tree in the end or modify a board.c?
If so that looks like the mmc port is not being probed correctly as it
is not defined. You should at least get some activity on mmc to try and
read the type of "sd card" on this bus. This should identify as a wl12xx
and then load the drivers when you insmod wlcore_sdio
Iain
On 26 August 2015 at 09:56, Dileep >
wrote:
> Hi,
>
> When i add wl12xx module, none of the functions from wl12xx and wlcore
> are getting called.
>
> logs:
> root@arm:~# modprobe wlcore_sdio
> [ 48.682409]
> [ 48.682409] ** wl1271_init
> [ 48.690385]
> [ 48.690385] ** sdio_register_driver
> [ 48.708615]
> [ 48.708615] ** sdio_register_driver : wl1271_sdio
>
> root@arm:~# modprobe wl12xx
> [ 57.901415]
> [ 57.901415] ** Country : COUNTRY=00 *
> [ 57.908006] cfg80211: Calling CRDA to update world regulatory domain
> [ 58.061324]
> [ 58.061324] ** ieee80211_init
> [ 58.067658]
> [ 58.067658] ** ieee80211_init 1
> [ 58.076820]
> [ 58.076820] ** ieee80211_init 2
> [ 58.086826]
> [ 58.086826] ** ieee80211_init 3
> root@arm:~# [ 58.207791] cfg80211: World regulatory domain updated:
> [ 58.213206] cfg80211: DFS Master region: unset
> [ 58.217588] cfg80211: (start_freq - end_freq @ bandwidth),
> (max_antenna_gain, max_eirp), (dfs_cac_time)
> [ 58.229554] cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz),
> (N/A, 2000 mBm), (N/A)
> [ 58.237609] cfg80211: (2457000 KHz - 2482000 KHz @ 4 KHz),
> (N/A, 2000 mBm), (N/A)
> [ 58.246721] cfg80211: (2474000 KHz - 2494000 KHz @ 2 KHz),
> (N/A, 2000 mBm), (N/A)
> [ 58.255431] cfg80211: (517 KHz - 525 KHz @ 8 KHz,
> 16 KHz AUTO), (N/A, 2000 mBm)
Re: [beagleboard] Wl12xx
Enable dummy regulators in the kernel
28 Авг 2015 г. 14:30 пользователь "Iain Hunter"
написал:
> Hi
>
> This is not good. You have tried to start mmc3 but it failed to get a
> regulator, so may not have continued its initialisation - i don't know how
> driver behaves in this case.
> omap_hsmmc 4781.mmc: unable to get vmmc regulator -517
>
> So suggestion would be to trace omap_hsmmc driver to understand why it
> fails to get a regulator.
> Iain
>
> On 28 August 2015 at 04:34, Dileep wrote:
>
>> Hi lain,
>>
>> I have configured MMC3 for SDIO communiction. but still sdio
>> communication is not up.
>>
>> If clock is not enabled by default for MMC3 how can it be done in device
>> tree,
>>
>> dmesg log shows:
>> [4.259093] omap_hsmmc 4781.mmc: unable to get vmmc regulator -517
>>
>>
>> Device tree configurations.
>>
>> wl12xx_vmmc: fixedregulator@2 {
>> pinctrl-names = "default";
>> pinctrl-0 = <&wl12xx_gpio>;
>> compatible = "regulator-fixed";
>> regulator-name = "vwl1271";
>> regulator-min-microvolt = <180>;
>> regulator-max-microvolt = <180>;
>> gpio = <&gpio0 27 0>;
>> startup-delay-us = <7>;
>> enable-active-high;
>> };
>>
>> mmc3_pins: pinmux_mmc3_pins {
>> pinctrl-single,pins = <
>> 0x3C (PIN_INPUT_PULLUP | MUX_MODE3) /* mmc2_dat3 */
>> 0x38 (PIN_INPUT_PULLUP | MUX_MODE3) /* mmc2_dat2 */
>> 0x34 (PIN_INPUT_PULLUP | MUX_MODE3) /* mmc2_dat1 */
>> 0x30 (PIN_INPUT_PULLUP | MUX_MODE3) /* mmc2_dat0 */
>> 0x8c (PIN_INPUT_PULLUP | MUX_MODE3) /* mmc2_clk */
>> 0x88 (PIN_INPUT_PULLUP | MUX_MODE3) /* mmc2_cmd */
>> >;
>> };
>>
>> &mmc3 {
>> /* these are on the crossbar and are outlined in the
>> xbar-event-map element */
>> dmas = <&edma 32 &edma 33>;
>> dma-names = "tx", "rx";
>>
>> status = "okay";
>> vmmc-supply = <&wl12xx_vmmc>;
>> ti,non-removable;
>> bus-width = <4>;
>> cap-power-off-card;
>> pinctrl-names = "default";
>> pinctrl-0 = <&mmc3_pins>;
>>
>> #address-cells = <1>;
>> #size-cells = <0>;
>> wlcore: wlcore@2 {
>> compatible = "ti,wl1271";
>> reg = <2>;
>> interrupt-parent = <&gpio0>;
>> interrupts = <26 0x4>; /* gpio 31 */
>> ref-clock-frequency = <3840>;
>> };
>> };
>>
>> &edma {
>> ti,edma-xbar-event-map = /bits/ 16 <1 32 2 33>;
>> };
>>
>> On Thu, Aug 27, 2015 at 10:03 PM, Iain Hunter
>> wrote:
>>
>>> Did you use device tree in the end or modify a board.c?
>>> If so that looks like the mmc port is not being probed correctly as it
>>> is not defined. You should at least get some activity on mmc to try and
>>> read the type of "sd card" on this bus. This should identify as a wl12xx
>>> and then load the drivers when you insmod wlcore_sdio
>>> Iain
>>>
>>> On 26 August 2015 at 09:56, Dileep wrote:
>>>
Hi,
When i add wl12xx module, none of the functions from wl12xx and wlcore
are getting called.
logs:
root@arm:~# modprobe wlcore_sdio
[ 48.682409]
[ 48.682409] ** wl1271_init
[ 48.690385]
[ 48.690385] ** sdio_register_driver
[ 48.708615]
[ 48.708615] ** sdio_register_driver : wl1271_sdio
root@arm:~# modprobe wl12xx
[ 57.901415]
[ 57.901415] ** Country : COUNTRY=00 *
[ 57.908006] cfg80211: Calling CRDA to update world regulatory domain
[ 58.061324]
[ 58.061324] ** ieee80211_init
[ 58.067658]
[ 58.067658] ** ieee80211_init 1
[ 58.076820]
[ 58.076820] ** ieee80211_init 2
[ 58.086826]
[ 58.086826] ** ieee80211_init 3
root@arm:~# [ 58.207791] cfg80211: World regulatory domain updated:
[ 58.213206] cfg80211: DFS Master region: unset
[ 58.217588] cfg80211: (start_freq - end_freq @ bandwidth),
(max_antenna_gain, max_eirp), (dfs_cac_time)
[ 58.229554] cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz),
(N/A, 2000 mBm), (N/A)
[ 58.237609] cfg80211: (2457000 KHz - 2482000 KHz @ 4 KHz),
(N/A, 2000 mBm), (N/A)
[ 58.246721] cfg80211: (2474000 KHz - 2494000 KHz @ 2 KHz),
(N/A, 2000 mBm), (N/A)
[ 58.255431] cfg80211: (517 KHz - 525 KHz @ 8 KHz,
16 KHz AUTO), (N/A, 2000 mBm), (N/A)
[ 58.265659] cfg80211: (525 KHz - 533 KHz @ 8 KHz,
16 KHz AUTO), (N/A, 2000 mBm), (0 s)
[ 58.275796] cfg80211: (549 KHz - 573 KHz @ 16 KHz),
(N/A, 2000 mBm), (0 s)
[ 58.284697] cfg80211: (5735000 KHz - 5835000 KHz @ 8 KHz),
(N/A, 2000 mBm), (N/A)
[ 58.293341] cfg80211: (5724 KHz - 6372 KHz @ 216 KHz),
(N/A, 0 mBm)
Re: [beagleboard] Wl12xx
Hi
This is not good. You have tried to start mmc3 but it failed to get a
regulator, so may not have continued its initialisation - i don't know how
driver behaves in this case.
omap_hsmmc 4781.mmc: unable to get vmmc regulator -517
So suggestion would be to trace omap_hsmmc driver to understand why it
fails to get a regulator.
Iain
On 28 August 2015 at 04:34, Dileep wrote:
> Hi lain,
>
> I have configured MMC3 for SDIO communiction. but still sdio communication
> is not up.
>
> If clock is not enabled by default for MMC3 how can it be done in device
> tree,
>
> dmesg log shows:
> [4.259093] omap_hsmmc 4781.mmc: unable to get vmmc regulator -517
>
>
> Device tree configurations.
>
> wl12xx_vmmc: fixedregulator@2 {
> pinctrl-names = "default";
> pinctrl-0 = <&wl12xx_gpio>;
> compatible = "regulator-fixed";
> regulator-name = "vwl1271";
> regulator-min-microvolt = <180>;
> regulator-max-microvolt = <180>;
> gpio = <&gpio0 27 0>;
> startup-delay-us = <7>;
> enable-active-high;
> };
>
> mmc3_pins: pinmux_mmc3_pins {
> pinctrl-single,pins = <
> 0x3C (PIN_INPUT_PULLUP | MUX_MODE3) /* mmc2_dat3 */
> 0x38 (PIN_INPUT_PULLUP | MUX_MODE3) /* mmc2_dat2 */
> 0x34 (PIN_INPUT_PULLUP | MUX_MODE3) /* mmc2_dat1 */
> 0x30 (PIN_INPUT_PULLUP | MUX_MODE3) /* mmc2_dat0 */
> 0x8c (PIN_INPUT_PULLUP | MUX_MODE3) /* mmc2_clk */
> 0x88 (PIN_INPUT_PULLUP | MUX_MODE3) /* mmc2_cmd */
> >;
> };
>
> &mmc3 {
> /* these are on the crossbar and are outlined in the
> xbar-event-map element */
> dmas = <&edma 32 &edma 33>;
> dma-names = "tx", "rx";
>
> status = "okay";
> vmmc-supply = <&wl12xx_vmmc>;
> ti,non-removable;
> bus-width = <4>;
> cap-power-off-card;
> pinctrl-names = "default";
> pinctrl-0 = <&mmc3_pins>;
>
> #address-cells = <1>;
> #size-cells = <0>;
> wlcore: wlcore@2 {
> compatible = "ti,wl1271";
> reg = <2>;
> interrupt-parent = <&gpio0>;
> interrupts = <26 0x4>; /* gpio 31 */
> ref-clock-frequency = <3840>;
> };
> };
>
> &edma {
> ti,edma-xbar-event-map = /bits/ 16 <1 32 2 33>;
> };
>
> On Thu, Aug 27, 2015 at 10:03 PM, Iain Hunter
> wrote:
>
>> Did you use device tree in the end or modify a board.c?
>> If so that looks like the mmc port is not being probed correctly as it is
>> not defined. You should at least get some activity on mmc to try and read
>> the type of "sd card" on this bus. This should identify as a wl12xx and
>> then load the drivers when you insmod wlcore_sdio
>> Iain
>>
>> On 26 August 2015 at 09:56, Dileep wrote:
>>
>>> Hi,
>>>
>>> When i add wl12xx module, none of the functions from wl12xx and wlcore
>>> are getting called.
>>>
>>> logs:
>>> root@arm:~# modprobe wlcore_sdio
>>> [ 48.682409]
>>> [ 48.682409] ** wl1271_init
>>> [ 48.690385]
>>> [ 48.690385] ** sdio_register_driver
>>> [ 48.708615]
>>> [ 48.708615] ** sdio_register_driver : wl1271_sdio
>>> root@arm:~# modprobe wl12xx
>>> [ 57.901415]
>>> [ 57.901415] ** Country : COUNTRY=00 *
>>> [ 57.908006] cfg80211: Calling CRDA to update world regulatory domain
>>> [ 58.061324]
>>> [ 58.061324] ** ieee80211_init
>>> [ 58.067658]
>>> [ 58.067658] ** ieee80211_init 1
>>> [ 58.076820]
>>> [ 58.076820] ** ieee80211_init 2
>>> [ 58.086826]
>>> [ 58.086826] ** ieee80211_init 3
>>> root@arm:~# [ 58.207791] cfg80211: World regulatory domain updated:
>>> [ 58.213206] cfg80211: DFS Master region: unset
>>> [ 58.217588] cfg80211: (start_freq - end_freq @ bandwidth),
>>> (max_antenna_gain, max_eirp), (dfs_cac_time)
>>> [ 58.229554] cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz),
>>> (N/A, 2000 mBm), (N/A)
>>> [ 58.237609] cfg80211: (2457000 KHz - 2482000 KHz @ 4 KHz),
>>> (N/A, 2000 mBm), (N/A)
>>> [ 58.246721] cfg80211: (2474000 KHz - 2494000 KHz @ 2 KHz),
>>> (N/A, 2000 mBm), (N/A)
>>> [ 58.255431] cfg80211: (517 KHz - 525 KHz @ 8 KHz,
>>> 16 KHz AUTO), (N/A, 2000 mBm), (N/A)
>>> [ 58.265659] cfg80211: (525 KHz - 533 KHz @ 8 KHz,
>>> 16 KHz AUTO), (N/A, 2000 mBm), (0 s)
>>> [ 58.275796] cfg80211: (549 KHz - 573 KHz @ 16 KHz),
>>> (N/A, 2000 mBm), (0 s)
>>> [ 58.284697] cfg80211: (5735000 KHz - 5835000 KHz @ 8 KHz),
>>> (N/A, 2000 mBm), (N/A)
>>> [ 58.293341] cfg80211: (5724 KHz - 6372 KHz @ 216 KHz),
>>> (N/A, 0 mBm), (N/A)
>>>
>>> root@arm:~# lsmod
>>> Module Size Used by
>>> wl12xx 64379 0
>>> wlcore213095 1 wl12xx
>>> mac80211 631232 2 wl12xx,wlcore
>>> cfg80211 518978 2 mac802
Re: [beagleboard] Wl12xx
Hi lain,
I have configured MMC3 for SDIO communiction. but still sdio communication
is not up.
If clock is not enabled by default for MMC3 how can it be done in device
tree,
dmesg log shows:
[4.259093] omap_hsmmc 4781.mmc: unable to get vmmc regulator -517
Device tree configurations.
wl12xx_vmmc: fixedregulator@2 {
pinctrl-names = "default";
pinctrl-0 = <&wl12xx_gpio>;
compatible = "regulator-fixed";
regulator-name = "vwl1271";
regulator-min-microvolt = <180>;
regulator-max-microvolt = <180>;
gpio = <&gpio0 27 0>;
startup-delay-us = <7>;
enable-active-high;
};
mmc3_pins: pinmux_mmc3_pins {
pinctrl-single,pins = <
0x3C (PIN_INPUT_PULLUP | MUX_MODE3) /* mmc2_dat3 */
0x38 (PIN_INPUT_PULLUP | MUX_MODE3) /* mmc2_dat2 */
0x34 (PIN_INPUT_PULLUP | MUX_MODE3) /* mmc2_dat1 */
0x30 (PIN_INPUT_PULLUP | MUX_MODE3) /* mmc2_dat0 */
0x8c (PIN_INPUT_PULLUP | MUX_MODE3) /* mmc2_clk */
0x88 (PIN_INPUT_PULLUP | MUX_MODE3) /* mmc2_cmd */
>;
};
&mmc3 {
/* these are on the crossbar and are outlined in the
xbar-event-map element */
dmas = <&edma 32 &edma 33>;
dma-names = "tx", "rx";
status = "okay";
vmmc-supply = <&wl12xx_vmmc>;
ti,non-removable;
bus-width = <4>;
cap-power-off-card;
pinctrl-names = "default";
pinctrl-0 = <&mmc3_pins>;
#address-cells = <1>;
#size-cells = <0>;
wlcore: wlcore@2 {
compatible = "ti,wl1271";
reg = <2>;
interrupt-parent = <&gpio0>;
interrupts = <26 0x4>; /* gpio 31 */
ref-clock-frequency = <3840>;
};
};
&edma {
ti,edma-xbar-event-map = /bits/ 16 <1 32 2 33>;
};
On Thu, Aug 27, 2015 at 10:03 PM, Iain Hunter wrote:
> Did you use device tree in the end or modify a board.c?
> If so that looks like the mmc port is not being probed correctly as it is
> not defined. You should at least get some activity on mmc to try and read
> the type of "sd card" on this bus. This should identify as a wl12xx and
> then load the drivers when you insmod wlcore_sdio
> Iain
>
> On 26 August 2015 at 09:56, Dileep wrote:
>
>> Hi,
>>
>> When i add wl12xx module, none of the functions from wl12xx and wlcore
>> are getting called.
>>
>> logs:
>> root@arm:~# modprobe wlcore_sdio
>> [ 48.682409]
>> [ 48.682409] ** wl1271_init
>> [ 48.690385]
>> [ 48.690385] ** sdio_register_driver
>> [ 48.708615]
>> [ 48.708615] ** sdio_register_driver : wl1271_sdio
>> root@arm:~# modprobe wl12xx
>> [ 57.901415]
>> [ 57.901415] ** Country : COUNTRY=00 *
>> [ 57.908006] cfg80211: Calling CRDA to update world regulatory domain
>> [ 58.061324]
>> [ 58.061324] ** ieee80211_init
>> [ 58.067658]
>> [ 58.067658] ** ieee80211_init 1
>> [ 58.076820]
>> [ 58.076820] ** ieee80211_init 2
>> [ 58.086826]
>> [ 58.086826] ** ieee80211_init 3
>> root@arm:~# [ 58.207791] cfg80211: World regulatory domain updated:
>> [ 58.213206] cfg80211: DFS Master region: unset
>> [ 58.217588] cfg80211: (start_freq - end_freq @ bandwidth),
>> (max_antenna_gain, max_eirp), (dfs_cac_time)
>> [ 58.229554] cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), (N/A,
>> 2000 mBm), (N/A)
>> [ 58.237609] cfg80211: (2457000 KHz - 2482000 KHz @ 4 KHz), (N/A,
>> 2000 mBm), (N/A)
>> [ 58.246721] cfg80211: (2474000 KHz - 2494000 KHz @ 2 KHz), (N/A,
>> 2000 mBm), (N/A)
>> [ 58.255431] cfg80211: (517 KHz - 525 KHz @ 8 KHz, 16
>> KHz AUTO), (N/A, 2000 mBm), (N/A)
>> [ 58.265659] cfg80211: (525 KHz - 533 KHz @ 8 KHz, 16
>> KHz AUTO), (N/A, 2000 mBm), (0 s)
>> [ 58.275796] cfg80211: (549 KHz - 573 KHz @ 16 KHz),
>> (N/A, 2000 mBm), (0 s)
>> [ 58.284697] cfg80211: (5735000 KHz - 5835000 KHz @ 8 KHz), (N/A,
>> 2000 mBm), (N/A)
>> [ 58.293341] cfg80211: (5724 KHz - 6372 KHz @ 216 KHz),
>> (N/A, 0 mBm), (N/A)
>>
>> root@arm:~# lsmod
>> Module Size Used by
>> wl12xx 64379 0
>> wlcore213095 1 wl12xx
>> mac80211 631232 2 wl12xx,wlcore
>> cfg80211 518978 2 mac80211,wlcore
>> rfkill 20618 1 cfg80211
>> wlcore_sdio 8050 0
>> snd_soc_evm 7798 0
>> omap_rng5144 0
>> rng_core8712 1 omap_rng
>> tilcdc 31000 0
>> snd_soc_tlv320aic32x416689 1
>> snd_soc_davinci_mcasp18424 2
>> snd_soc_edma1166 1 snd_soc_davinci_mcasp
>> uio_pdrv_genirq 3625 0
>> uio 9898 1 uio_pdrv_genirq
>> root@arm:~#
>>
>>
>> On Thu, Aug 20, 2015 at 4:18 PM, Iain Hunter
>> wrote:
>>
>>> Hi,
>>> As a follow up I agree
Re: [beagleboard] Wl12xx
Did you use device tree in the end or modify a board.c? If so that looks like the mmc port is not being probed correctly as it is not defined. You should at least get some activity on mmc to try and read the type of "sd card" on this bus. This should identify as a wl12xx and then load the drivers when you insmod wlcore_sdio Iain On 26 August 2015 at 09:56, Dileep wrote: > Hi, > > When i add wl12xx module, none of the functions from wl12xx and wlcore are > getting called. > > logs: > root@arm:~# modprobe wlcore_sdio > [ 48.682409] > [ 48.682409] ** wl1271_init > [ 48.690385] > [ 48.690385] ** sdio_register_driver > [ 48.708615] > [ 48.708615] ** sdio_register_driver : wl1271_sdio > root@arm:~# modprobe wl12xx > [ 57.901415] > [ 57.901415] ** Country : COUNTRY=00 * > [ 57.908006] cfg80211: Calling CRDA to update world regulatory domain > [ 58.061324] > [ 58.061324] ** ieee80211_init > [ 58.067658] > [ 58.067658] ** ieee80211_init 1 > [ 58.076820] > [ 58.076820] ** ieee80211_init 2 > [ 58.086826] > [ 58.086826] ** ieee80211_init 3 > root@arm:~# [ 58.207791] cfg80211: World regulatory domain updated: > [ 58.213206] cfg80211: DFS Master region: unset > [ 58.217588] cfg80211: (start_freq - end_freq @ bandwidth), > (max_antenna_gain, max_eirp), (dfs_cac_time) > [ 58.229554] cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), (N/A, > 2000 mBm), (N/A) > [ 58.237609] cfg80211: (2457000 KHz - 2482000 KHz @ 4 KHz), (N/A, > 2000 mBm), (N/A) > [ 58.246721] cfg80211: (2474000 KHz - 2494000 KHz @ 2 KHz), (N/A, > 2000 mBm), (N/A) > [ 58.255431] cfg80211: (517 KHz - 525 KHz @ 8 KHz, 16 > KHz AUTO), (N/A, 2000 mBm), (N/A) > [ 58.265659] cfg80211: (525 KHz - 533 KHz @ 8 KHz, 16 > KHz AUTO), (N/A, 2000 mBm), (0 s) > [ 58.275796] cfg80211: (549 KHz - 573 KHz @ 16 KHz), (N/A, > 2000 mBm), (0 s) > [ 58.284697] cfg80211: (5735000 KHz - 5835000 KHz @ 8 KHz), (N/A, > 2000 mBm), (N/A) > [ 58.293341] cfg80211: (5724 KHz - 6372 KHz @ 216 KHz), > (N/A, 0 mBm), (N/A) > > root@arm:~# lsmod > Module Size Used by > wl12xx 64379 0 > wlcore213095 1 wl12xx > mac80211 631232 2 wl12xx,wlcore > cfg80211 518978 2 mac80211,wlcore > rfkill 20618 1 cfg80211 > wlcore_sdio 8050 0 > snd_soc_evm 7798 0 > omap_rng5144 0 > rng_core8712 1 omap_rng > tilcdc 31000 0 > snd_soc_tlv320aic32x416689 1 > snd_soc_davinci_mcasp18424 2 > snd_soc_edma1166 1 snd_soc_davinci_mcasp > uio_pdrv_genirq 3625 0 > uio 9898 1 uio_pdrv_genirq > root@arm:~# > > > On Thu, Aug 20, 2015 at 4:18 PM, Iain Hunter wrote: > >> Hi, >> As a follow up I agree with the previous statement that wl127x drivers >> have no device tree support. So you'll need to merge device tree support >> from wl18xx drivers. As far as I can remember there are no major changes to >> parameters passed by device tree to WiFi driver from wl127x to wl18xx. As >> long as you successfully pass the wl12xx probe function without an error >> you should be ok. Caveat is that I've not done this exercise. >> Iain >> On 19 Aug 2015 15:56, wrote: >> >>> Hi, >>> Which wilink device are you building for? >>> The wl18xx family is now fully supported in 4.1 kernel. There is a >>> device tree file for the wl1835 cape in the kernel that is best place to >>> look. >>> If you are looking at wl127x or wl128x then device tree will be similar >>> but you'll need to build the Wi-Fi drivers out of tree. >>> For the wl1835 cape look at the ti processor wiki for a page to describe >>> full build and configuration on 4.1 kernel. >>> Iain >>> >>> -- >>> For more options, visit http://beagleboard.org/discuss >>> --- >>> You received this message because you are subscribed to a topic in the >>> Google Groups "BeagleBoard" group. >>> To unsubscribe from this topic, visit >>> https://groups.google.com/d/topic/beagleboard/_Edxe-s1MxQ/unsubscribe. >>> To unsubscribe from this group and all its topics, send an email to >>> beagleboard+unsubscr...@googlegroups.com. >>> For more options, visit https://groups.google.com/d/optout. >>> >> -- >> For more options, visit http://beagleboard.org/discuss >> --- >> You received this message because you are subscribed to a topic in the >> Google Groups "BeagleBoard" group. >> To unsubscribe from this topic, visit >> https://groups.google.com/d/topic/beagleboard/_Edxe-s1MxQ/unsubscribe. >> To unsubscribe from this group and all its topics, send an email to >> beagleboard+unsubscr...@googlegroups.com. >> For more options, visit https://groups.google.com/d/optout. >> > > -- > For more opti
Re: [beagleboard] Wl12xx
Hi, When i add wl12xx module, none of the functions from wl12xx and wlcore are getting called. logs: root@arm:~# modprobe wlcore_sdio [ 48.682409] [ 48.682409] ** wl1271_init [ 48.690385] [ 48.690385] ** sdio_register_driver [ 48.708615] [ 48.708615] ** sdio_register_driver : wl1271_sdio root@arm:~# modprobe wl12xx [ 57.901415] [ 57.901415] ** Country : COUNTRY=00 * [ 57.908006] cfg80211: Calling CRDA to update world regulatory domain [ 58.061324] [ 58.061324] ** ieee80211_init [ 58.067658] [ 58.067658] ** ieee80211_init 1 [ 58.076820] [ 58.076820] ** ieee80211_init 2 [ 58.086826] [ 58.086826] ** ieee80211_init 3 root@arm:~# [ 58.207791] cfg80211: World regulatory domain updated: [ 58.213206] cfg80211: DFS Master region: unset [ 58.217588] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time) [ 58.229554] cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A) [ 58.237609] cfg80211: (2457000 KHz - 2482000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A) [ 58.246721] cfg80211: (2474000 KHz - 2494000 KHz @ 2 KHz), (N/A, 2000 mBm), (N/A) [ 58.255431] cfg80211: (517 KHz - 525 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2000 mBm), (N/A) [ 58.265659] cfg80211: (525 KHz - 533 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2000 mBm), (0 s) [ 58.275796] cfg80211: (549 KHz - 573 KHz @ 16 KHz), (N/A, 2000 mBm), (0 s) [ 58.284697] cfg80211: (5735000 KHz - 5835000 KHz @ 8 KHz), (N/A, 2000 mBm), (N/A) [ 58.293341] cfg80211: (5724 KHz - 6372 KHz @ 216 KHz), (N/A, 0 mBm), (N/A) root@arm:~# lsmod Module Size Used by wl12xx 64379 0 wlcore213095 1 wl12xx mac80211 631232 2 wl12xx,wlcore cfg80211 518978 2 mac80211,wlcore rfkill 20618 1 cfg80211 wlcore_sdio 8050 0 snd_soc_evm 7798 0 omap_rng5144 0 rng_core8712 1 omap_rng tilcdc 31000 0 snd_soc_tlv320aic32x416689 1 snd_soc_davinci_mcasp18424 2 snd_soc_edma1166 1 snd_soc_davinci_mcasp uio_pdrv_genirq 3625 0 uio 9898 1 uio_pdrv_genirq root@arm:~# On Thu, Aug 20, 2015 at 4:18 PM, Iain Hunter wrote: > Hi, > As a follow up I agree with the previous statement that wl127x drivers > have no device tree support. So you'll need to merge device tree support > from wl18xx drivers. As far as I can remember there are no major changes to > parameters passed by device tree to WiFi driver from wl127x to wl18xx. As > long as you successfully pass the wl12xx probe function without an error > you should be ok. Caveat is that I've not done this exercise. > Iain > On 19 Aug 2015 15:56, wrote: > >> Hi, >> Which wilink device are you building for? >> The wl18xx family is now fully supported in 4.1 kernel. There is a device >> tree file for the wl1835 cape in the kernel that is best place to look. >> If you are looking at wl127x or wl128x then device tree will be similar >> but you'll need to build the Wi-Fi drivers out of tree. >> For the wl1835 cape look at the ti processor wiki for a page to describe >> full build and configuration on 4.1 kernel. >> Iain >> >> -- >> For more options, visit http://beagleboard.org/discuss >> --- >> You received this message because you are subscribed to a topic in the >> Google Groups "BeagleBoard" group. >> To unsubscribe from this topic, visit >> https://groups.google.com/d/topic/beagleboard/_Edxe-s1MxQ/unsubscribe. >> To unsubscribe from this group and all its topics, send an email to >> beagleboard+unsubscr...@googlegroups.com. >> For more options, visit https://groups.google.com/d/optout. >> > -- > For more options, visit http://beagleboard.org/discuss > --- > You received this message because you are subscribed to a topic in the > Google Groups "BeagleBoard" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/beagleboard/_Edxe-s1MxQ/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > beagleboard+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Wl12xx
Hi, As a follow up I agree with the previous statement that wl127x drivers have no device tree support. So you'll need to merge device tree support from wl18xx drivers. As far as I can remember there are no major changes to parameters passed by device tree to WiFi driver from wl127x to wl18xx. As long as you successfully pass the wl12xx probe function without an error you should be ok. Caveat is that I've not done this exercise. Iain On 19 Aug 2015 15:56, wrote: > Hi, > Which wilink device are you building for? > The wl18xx family is now fully supported in 4.1 kernel. There is a device > tree file for the wl1835 cape in the kernel that is best place to look. > If you are looking at wl127x or wl128x then device tree will be similar > but you'll need to build the Wi-Fi drivers out of tree. > For the wl1835 cape look at the ti processor wiki for a page to describe > full build and configuration on 4.1 kernel. > Iain > > -- > For more options, visit http://beagleboard.org/discuss > --- > You received this message because you are subscribed to a topic in the > Google Groups "BeagleBoard" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/beagleboard/_Edxe-s1MxQ/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > beagleboard+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Wl12xx
Hi, Which wilink device are you building for? The wl18xx family is now fully supported in 4.1 kernel. There is a device tree file for the wl1835 cape in the kernel that is best place to look. If you are looking at wl127x or wl128x then device tree will be similar but you'll need to build the Wi-Fi drivers out of tree. For the wl1835 cape look at the ti processor wiki for a page to describe full build and configuration on 4.1 kernel. Iain -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Wl12xx
why not? this package enables wl12 for TI's am335x EVMSK and uses the
device tree
http://www.ti.com/tool/PROCESSOR-SDK-AM335X
2015-08-19 16:49 GMT+03:00 Dileep :
> Wl12xx will not support device tree. Need to find out other procedure to
> enable in some board init function
>
> On Wed, Aug 19, 2015 at 7:03 PM, Maxim Podbereznyy
> wrote:
>
>> I don't see a wl12 boot message when the firmware is successfully loaded
>>
>> 2015-08-19 16:32 GMT+03:00 Maxim Podbereznyy :
>>
>>> did you place t-connectivity directory to /lib/firmware?
>>>
>>> 2015-08-19 9:05 GMT+03:00 Dileep D R :
>>>
Hi,
Interfacing wifi module (wl12xx ti chipset) with beaglebone black.
Unable to bring up wlan0 interface, please guide me for proper device tree
configuration.
After booting excecuted
modprobe wlcore_sdio
modprobe wl12xx
Below are my configurations.
Kernel : 4.1
Rootfs : Debian
Device Tree:
/ {
vwlan_en_reg: regulator-vwlan-en {
compatible = "regulator-fixed";
regulator-name = "vwlan_en";
regulator-min-microvolt = <180>;
regulator-max-microvolt = <180>;
gpio = <&gpio0 27 0>;
enable-active-high;
startup-delay-us = <7>;
pinctrl-names = "default";
pinctrl-0 = <&wlan_enable_pins>;
};
};
&am33xx_pinmux {
wlan_pins: pinmux_wlan_pins {
pinctrl-single,pins = <
0x28 (PIN_INPUT_PULLUP | MUX_MODE7)/* gpio0_26 WL_IRQ */
>;
};
wlan_enable_pins: pinmux_wlan_enable_pins {
pinctrl-single,pins = <
0x2c (PIN_OUTPUT_PULLUP | MUX_MODE7) /* gpio0_27 WL_EN */
>;
};
mmc2_pins: pinmux_mmc2_pins {
pinctrl-single,pins = <
0x3C (PIN_INPUT_PULLUP | MUX_MODE3) /* mmc2_dat3 */
0x38 (PIN_INPUT_PULLUP | MUX_MODE3) /* mmc2_dat2 */
0x34 (PIN_INPUT_PULLUP | MUX_MODE3) /* mmc2_dat1 */
0x30 (PIN_INPUT_PULLUP | MUX_MODE3) /* mmc2_dat0 */
0x8c (PIN_INPUT_PULLUP | MUX_MODE3) /* mmc2_clk */
0x88 (PIN_INPUT_PULLUP | MUX_MODE3) /* mmc2_cmd */
>;
};
};
&i2c2 {
pinctrl-names = "default";
pinctrl-0 = <&i2c2_pins>;
status = "okay";
clock-frequency = <10>;
/* ODIN-W160 EEPROM */
eeprom@5D {
compatible = "at,24c64";
reg = <0x5D>;
pagesize = <32>;
};
};
&mmc2 {
non-removable; /* TI specific feature */
bus-width = <4>;
cap-power-off-card; /* TI specific feature */
vmmc-supply = <&vwlan_en_reg>;
pinctrl-names = "default";
pinctrl-0 = <&mmc2_pins &wlan_pins>;
status = "okay";
#address-cells = <1>;
#size-cells = <0>;
wlcore: wlcore@0 {
compatible = "ti,wl1273";
reg = <2>;
interrupt-parent = <&gpio0>;
interrupts = <26 0x4>;
ref-clock-frequency = <3840>;
};
};
dmesg log:
[0.00] Booting Linux on physical CPU 0x0
[0.00] Initializing cgroup subsys cpuset
[0.00] Initializing cgroup subsys cpu
[0.00] Initializing cgroup subsys cpuacct
[0.00] Linux version 4.1.3+ (dileep@ubuntu) (gcc version 4.6.3
(Ubuntu/Linaro 4.6.3-1ubuntu5) ) #2 SMP PREEMPT Tue Aug 18 16:54:12 IST
2015
[0.00] CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7),
cr=10c5387d
[0.00] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing
instruction cache
[0.00] Machine model: TI AM335x BeagleBone Black
[0.00] cma: Reserved 24 MiB at 0x9e00
[0.00] Memory policy: Data cache writeback
[0.00] On node 0 totalpages: 130560
[0.00] free_area_init_node: node 0, pgdat c0f4c700,
node_mem_map df96d000
[0.00] Normal zone: 1152 pages used for memmap
[0.00] Normal zone: 0 pages reserved
[0.00] Normal zone: 130560 pages, LIFO batch:31
[0.00] CPU: All CPU(s) started in SVC mode.
[0.00] AM335X ES2.1 (sgx neon )
[0.00] PERCPU: Embedded 13 pages/cpu @df925000 s22336 r8192
d22720 u53248
[0.00] pcpu-alloc: s22336 r8192 d22720 u53248 alloc=13*4096
[0.00] pcpu-alloc: [0] 0
[0.00] Built 1 zonelists in Zone order, mobility grouping on.
Total pages: 129408
[0.00] Kernel command line: console=ttyO0,115200n8
root=/dev/nfs rw
nfsroot=192.168.0.101:/home/dileep/BeagleBone/rootfs_debian
ip=192.168.0.105:eth0
[0.00] PID hash t
Re: [beagleboard] Wl12xx
Wl12xx will not support device tree. Need to find out other procedure to
enable in some board init function
On Wed, Aug 19, 2015 at 7:03 PM, Maxim Podbereznyy
wrote:
> I don't see a wl12 boot message when the firmware is successfully loaded
>
> 2015-08-19 16:32 GMT+03:00 Maxim Podbereznyy :
>
>> did you place t-connectivity directory to /lib/firmware?
>>
>> 2015-08-19 9:05 GMT+03:00 Dileep D R :
>>
>>>
>>> Hi,
>>>
>>> Interfacing wifi module (wl12xx ti chipset) with beaglebone black.
>>> Unable to bring up wlan0 interface, please guide me for proper device tree
>>> configuration.
>>>
>>> After booting excecuted
>>> modprobe wlcore_sdio
>>> modprobe wl12xx
>>>
>>>
>>> Below are my configurations.
>>>
>>> Kernel : 4.1
>>> Rootfs : Debian
>>>
>>> Device Tree:
>>>
>>> / {
>>> vwlan_en_reg: regulator-vwlan-en {
>>> compatible = "regulator-fixed";
>>> regulator-name = "vwlan_en";
>>> regulator-min-microvolt = <180>;
>>> regulator-max-microvolt = <180>;
>>> gpio = <&gpio0 27 0>;
>>> enable-active-high;
>>> startup-delay-us = <7>;
>>> pinctrl-names = "default";
>>> pinctrl-0 = <&wlan_enable_pins>;
>>> };
>>> };
>>>
>>> &am33xx_pinmux {
>>>
>>> wlan_pins: pinmux_wlan_pins {
>>> pinctrl-single,pins = <
>>> 0x28 (PIN_INPUT_PULLUP | MUX_MODE7)/* gpio0_26 WL_IRQ */
>>> >;
>>> };
>>>
>>> wlan_enable_pins: pinmux_wlan_enable_pins {
>>> pinctrl-single,pins = <
>>> 0x2c (PIN_OUTPUT_PULLUP | MUX_MODE7) /* gpio0_27 WL_EN */
>>> >;
>>> };
>>>
>>> mmc2_pins: pinmux_mmc2_pins {
>>> pinctrl-single,pins = <
>>> 0x3C (PIN_INPUT_PULLUP | MUX_MODE3) /* mmc2_dat3 */
>>> 0x38 (PIN_INPUT_PULLUP | MUX_MODE3) /* mmc2_dat2 */
>>> 0x34 (PIN_INPUT_PULLUP | MUX_MODE3) /* mmc2_dat1 */
>>> 0x30 (PIN_INPUT_PULLUP | MUX_MODE3) /* mmc2_dat0 */
>>> 0x8c (PIN_INPUT_PULLUP | MUX_MODE3) /* mmc2_clk */
>>> 0x88 (PIN_INPUT_PULLUP | MUX_MODE3) /* mmc2_cmd */
>>> >;
>>> };
>>> };
>>>
>>> &i2c2 {
>>> pinctrl-names = "default";
>>> pinctrl-0 = <&i2c2_pins>;
>>>
>>> status = "okay";
>>> clock-frequency = <10>;
>>>
>>> /* ODIN-W160 EEPROM */
>>> eeprom@5D {
>>> compatible = "at,24c64";
>>> reg = <0x5D>;
>>> pagesize = <32>;
>>> };
>>> };
>>>
>>> &mmc2 {
>>> non-removable; /* TI specific feature */
>>> bus-width = <4>;
>>> cap-power-off-card; /* TI specific feature */
>>> vmmc-supply = <&vwlan_en_reg>;
>>> pinctrl-names = "default";
>>> pinctrl-0 = <&mmc2_pins &wlan_pins>;
>>> status = "okay";
>>>
>>> #address-cells = <1>;
>>> #size-cells = <0>;
>>> wlcore: wlcore@0 {
>>> compatible = "ti,wl1273";
>>> reg = <2>;
>>> interrupt-parent = <&gpio0>;
>>> interrupts = <26 0x4>;
>>> ref-clock-frequency = <3840>;
>>> };
>>> };
>>>
>>> dmesg log:
>>>
>>> [0.00] Booting Linux on physical CPU 0x0
>>> [0.00] Initializing cgroup subsys cpuset
>>> [0.00] Initializing cgroup subsys cpu
>>> [0.00] Initializing cgroup subsys cpuacct
>>> [0.00] Linux version 4.1.3+ (dileep@ubuntu) (gcc version 4.6.3
>>> (Ubuntu/Linaro 4.6.3-1ubuntu5) ) #2 SMP PREEMPT Tue Aug 18 16:54:12 IST 2015
>>> [0.00] CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7),
>>> cr=10c5387d
>>> [0.00] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing
>>> instruction cache
>>> [0.00] Machine model: TI AM335x BeagleBone Black
>>> [0.00] cma: Reserved 24 MiB at 0x9e00
>>> [0.00] Memory policy: Data cache writeback
>>> [0.00] On node 0 totalpages: 130560
>>> [0.00] free_area_init_node: node 0, pgdat c0f4c700, node_mem_map
>>> df96d000
>>> [0.00] Normal zone: 1152 pages used for memmap
>>> [0.00] Normal zone: 0 pages reserved
>>> [0.00] Normal zone: 130560 pages, LIFO batch:31
>>> [0.00] CPU: All CPU(s) started in SVC mode.
>>> [0.00] AM335X ES2.1 (sgx neon )
>>> [0.00] PERCPU: Embedded 13 pages/cpu @df925000 s22336 r8192
>>> d22720 u53248
>>> [0.00] pcpu-alloc: s22336 r8192 d22720 u53248 alloc=13*4096
>>> [0.00] pcpu-alloc: [0] 0
>>> [0.00] Built 1 zonelists in Zone order, mobility grouping on.
>>> Total pages: 129408
>>> [0.00] Kernel command line: console=ttyO0,115200n8 root=/dev/nfs
>>> rw nfsroot=192.168.0.101:/home/dileep/BeagleBone/rootfs_debian
>>> ip=192.168.0.105:eth0
>>> [0.00] PID hash table entries: 2048 (order: 1, 8192 bytes)
>>> [0.00] Dentry cache hash table entries: 65536 (order: 6, 262144
>>> bytes)
>>> [0.00] Inode-cache hash table entries: 32768 (order: 5, 131072
>>> bytes)
>>> [0.00] Memory: 475580K/522240K available (10502K kernel code,
>>> 881K rwdata, 3680K rodata, 67
Re: [beagleboard] Wl12xx
I don't see a wl12 boot message when the firmware is successfully loaded
2015-08-19 16:32 GMT+03:00 Maxim Podbereznyy :
> did you place t-connectivity directory to /lib/firmware?
>
> 2015-08-19 9:05 GMT+03:00 Dileep D R :
>
>>
>> Hi,
>>
>> Interfacing wifi module (wl12xx ti chipset) with beaglebone black. Unable
>> to bring up wlan0 interface, please guide me for proper device tree
>> configuration.
>>
>> After booting excecuted
>> modprobe wlcore_sdio
>> modprobe wl12xx
>>
>>
>> Below are my configurations.
>>
>> Kernel : 4.1
>> Rootfs : Debian
>>
>> Device Tree:
>>
>> / {
>> vwlan_en_reg: regulator-vwlan-en {
>> compatible = "regulator-fixed";
>> regulator-name = "vwlan_en";
>> regulator-min-microvolt = <180>;
>> regulator-max-microvolt = <180>;
>> gpio = <&gpio0 27 0>;
>> enable-active-high;
>> startup-delay-us = <7>;
>> pinctrl-names = "default";
>> pinctrl-0 = <&wlan_enable_pins>;
>> };
>> };
>>
>> &am33xx_pinmux {
>>
>> wlan_pins: pinmux_wlan_pins {
>> pinctrl-single,pins = <
>> 0x28 (PIN_INPUT_PULLUP | MUX_MODE7)/* gpio0_26 WL_IRQ */
>> >;
>> };
>>
>> wlan_enable_pins: pinmux_wlan_enable_pins {
>> pinctrl-single,pins = <
>> 0x2c (PIN_OUTPUT_PULLUP | MUX_MODE7) /* gpio0_27 WL_EN */
>> >;
>> };
>>
>> mmc2_pins: pinmux_mmc2_pins {
>> pinctrl-single,pins = <
>> 0x3C (PIN_INPUT_PULLUP | MUX_MODE3) /* mmc2_dat3 */
>> 0x38 (PIN_INPUT_PULLUP | MUX_MODE3) /* mmc2_dat2 */
>> 0x34 (PIN_INPUT_PULLUP | MUX_MODE3) /* mmc2_dat1 */
>> 0x30 (PIN_INPUT_PULLUP | MUX_MODE3) /* mmc2_dat0 */
>> 0x8c (PIN_INPUT_PULLUP | MUX_MODE3) /* mmc2_clk */
>> 0x88 (PIN_INPUT_PULLUP | MUX_MODE3) /* mmc2_cmd */
>> >;
>> };
>> };
>>
>> &i2c2 {
>> pinctrl-names = "default";
>> pinctrl-0 = <&i2c2_pins>;
>>
>> status = "okay";
>> clock-frequency = <10>;
>>
>> /* ODIN-W160 EEPROM */
>> eeprom@5D {
>> compatible = "at,24c64";
>> reg = <0x5D>;
>> pagesize = <32>;
>> };
>> };
>>
>> &mmc2 {
>> non-removable; /* TI specific feature */
>> bus-width = <4>;
>> cap-power-off-card; /* TI specific feature */
>> vmmc-supply = <&vwlan_en_reg>;
>> pinctrl-names = "default";
>> pinctrl-0 = <&mmc2_pins &wlan_pins>;
>> status = "okay";
>>
>> #address-cells = <1>;
>> #size-cells = <0>;
>> wlcore: wlcore@0 {
>> compatible = "ti,wl1273";
>> reg = <2>;
>> interrupt-parent = <&gpio0>;
>> interrupts = <26 0x4>;
>> ref-clock-frequency = <3840>;
>> };
>> };
>>
>> dmesg log:
>>
>> [0.00] Booting Linux on physical CPU 0x0
>> [0.00] Initializing cgroup subsys cpuset
>> [0.00] Initializing cgroup subsys cpu
>> [0.00] Initializing cgroup subsys cpuacct
>> [0.00] Linux version 4.1.3+ (dileep@ubuntu) (gcc version 4.6.3
>> (Ubuntu/Linaro 4.6.3-1ubuntu5) ) #2 SMP PREEMPT Tue Aug 18 16:54:12 IST 2015
>> [0.00] CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7),
>> cr=10c5387d
>> [0.00] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing
>> instruction cache
>> [0.00] Machine model: TI AM335x BeagleBone Black
>> [0.00] cma: Reserved 24 MiB at 0x9e00
>> [0.00] Memory policy: Data cache writeback
>> [0.00] On node 0 totalpages: 130560
>> [0.00] free_area_init_node: node 0, pgdat c0f4c700, node_mem_map
>> df96d000
>> [0.00] Normal zone: 1152 pages used for memmap
>> [0.00] Normal zone: 0 pages reserved
>> [0.00] Normal zone: 130560 pages, LIFO batch:31
>> [0.00] CPU: All CPU(s) started in SVC mode.
>> [0.00] AM335X ES2.1 (sgx neon )
>> [0.00] PERCPU: Embedded 13 pages/cpu @df925000 s22336 r8192
>> d22720 u53248
>> [0.00] pcpu-alloc: s22336 r8192 d22720 u53248 alloc=13*4096
>> [0.00] pcpu-alloc: [0] 0
>> [0.00] Built 1 zonelists in Zone order, mobility grouping on.
>> Total pages: 129408
>> [0.00] Kernel command line: console=ttyO0,115200n8 root=/dev/nfs
>> rw nfsroot=192.168.0.101:/home/dileep/BeagleBone/rootfs_debian
>> ip=192.168.0.105:eth0
>> [0.00] PID hash table entries: 2048 (order: 1, 8192 bytes)
>> [0.00] Dentry cache hash table entries: 65536 (order: 6, 262144
>> bytes)
>> [0.00] Inode-cache hash table entries: 32768 (order: 5, 131072
>> bytes)
>> [0.00] Memory: 475580K/522240K available (10502K kernel code,
>> 881K rwdata, 3680K rodata, 672K init, 901K bss, 22084K reserved, 24576K
>> cma-reserved, 0K highmem)
>> [0.00] Virtual kernel memory layout:
>> vector : 0x - 0x1000 ( 4 kB)
>> fixmap : 0xffc0 - 0xfff0 (3072 kB)
>> vmalloc : 0xe080 - 0xff00 ( 488 MB)
>> lowmem : 0xc000 - 0xe
Re: [beagleboard] Wl12xx
did you place t-connectivity directory to /lib/firmware?
2015-08-19 9:05 GMT+03:00 Dileep D R :
>
> Hi,
>
> Interfacing wifi module (wl12xx ti chipset) with beaglebone black. Unable
> to bring up wlan0 interface, please guide me for proper device tree
> configuration.
>
> After booting excecuted
> modprobe wlcore_sdio
> modprobe wl12xx
>
>
> Below are my configurations.
>
> Kernel : 4.1
> Rootfs : Debian
>
> Device Tree:
>
> / {
> vwlan_en_reg: regulator-vwlan-en {
> compatible = "regulator-fixed";
> regulator-name = "vwlan_en";
> regulator-min-microvolt = <180>;
> regulator-max-microvolt = <180>;
> gpio = <&gpio0 27 0>;
> enable-active-high;
> startup-delay-us = <7>;
> pinctrl-names = "default";
> pinctrl-0 = <&wlan_enable_pins>;
> };
> };
>
> &am33xx_pinmux {
>
> wlan_pins: pinmux_wlan_pins {
> pinctrl-single,pins = <
> 0x28 (PIN_INPUT_PULLUP | MUX_MODE7)/* gpio0_26 WL_IRQ */
> >;
> };
>
> wlan_enable_pins: pinmux_wlan_enable_pins {
> pinctrl-single,pins = <
> 0x2c (PIN_OUTPUT_PULLUP | MUX_MODE7) /* gpio0_27 WL_EN */
> >;
> };
>
> mmc2_pins: pinmux_mmc2_pins {
> pinctrl-single,pins = <
> 0x3C (PIN_INPUT_PULLUP | MUX_MODE3) /* mmc2_dat3 */
> 0x38 (PIN_INPUT_PULLUP | MUX_MODE3) /* mmc2_dat2 */
> 0x34 (PIN_INPUT_PULLUP | MUX_MODE3) /* mmc2_dat1 */
> 0x30 (PIN_INPUT_PULLUP | MUX_MODE3) /* mmc2_dat0 */
> 0x8c (PIN_INPUT_PULLUP | MUX_MODE3) /* mmc2_clk */
> 0x88 (PIN_INPUT_PULLUP | MUX_MODE3) /* mmc2_cmd */
> >;
> };
> };
>
> &i2c2 {
> pinctrl-names = "default";
> pinctrl-0 = <&i2c2_pins>;
>
> status = "okay";
> clock-frequency = <10>;
>
> /* ODIN-W160 EEPROM */
> eeprom@5D {
> compatible = "at,24c64";
> reg = <0x5D>;
> pagesize = <32>;
> };
> };
>
> &mmc2 {
> non-removable; /* TI specific feature */
> bus-width = <4>;
> cap-power-off-card; /* TI specific feature */
> vmmc-supply = <&vwlan_en_reg>;
> pinctrl-names = "default";
> pinctrl-0 = <&mmc2_pins &wlan_pins>;
> status = "okay";
>
> #address-cells = <1>;
> #size-cells = <0>;
> wlcore: wlcore@0 {
> compatible = "ti,wl1273";
> reg = <2>;
> interrupt-parent = <&gpio0>;
> interrupts = <26 0x4>;
> ref-clock-frequency = <3840>;
> };
> };
>
> dmesg log:
>
> [0.00] Booting Linux on physical CPU 0x0
> [0.00] Initializing cgroup subsys cpuset
> [0.00] Initializing cgroup subsys cpu
> [0.00] Initializing cgroup subsys cpuacct
> [0.00] Linux version 4.1.3+ (dileep@ubuntu) (gcc version 4.6.3
> (Ubuntu/Linaro 4.6.3-1ubuntu5) ) #2 SMP PREEMPT Tue Aug 18 16:54:12 IST 2015
> [0.00] CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7),
> cr=10c5387d
> [0.00] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing
> instruction cache
> [0.00] Machine model: TI AM335x BeagleBone Black
> [0.00] cma: Reserved 24 MiB at 0x9e00
> [0.00] Memory policy: Data cache writeback
> [0.00] On node 0 totalpages: 130560
> [0.00] free_area_init_node: node 0, pgdat c0f4c700, node_mem_map
> df96d000
> [0.00] Normal zone: 1152 pages used for memmap
> [0.00] Normal zone: 0 pages reserved
> [0.00] Normal zone: 130560 pages, LIFO batch:31
> [0.00] CPU: All CPU(s) started in SVC mode.
> [0.00] AM335X ES2.1 (sgx neon )
> [0.00] PERCPU: Embedded 13 pages/cpu @df925000 s22336 r8192 d22720
> u53248
> [0.00] pcpu-alloc: s22336 r8192 d22720 u53248 alloc=13*4096
> [0.00] pcpu-alloc: [0] 0
> [0.00] Built 1 zonelists in Zone order, mobility grouping on.
> Total pages: 129408
> [0.00] Kernel command line: console=ttyO0,115200n8 root=/dev/nfs
> rw nfsroot=192.168.0.101:/home/dileep/BeagleBone/rootfs_debian
> ip=192.168.0.105:eth0
> [0.00] PID hash table entries: 2048 (order: 1, 8192 bytes)
> [0.00] Dentry cache hash table entries: 65536 (order: 6, 262144
> bytes)
> [0.00] Inode-cache hash table entries: 32768 (order: 5, 131072
> bytes)
> [0.00] Memory: 475580K/522240K available (10502K kernel code, 881K
> rwdata, 3680K rodata, 672K init, 901K bss, 22084K reserved, 24576K
> cma-reserved, 0K highmem)
> [0.00] Virtual kernel memory layout:
> vector : 0x - 0x1000 ( 4 kB)
> fixmap : 0xffc0 - 0xfff0 (3072 kB)
> vmalloc : 0xe080 - 0xff00 ( 488 MB)
> lowmem : 0xc000 - 0xe000 ( 512 MB)
> pkmap : 0xbfe0 - 0xc000 ( 2 MB)
> modules : 0xbf00 - 0xbfe0 ( 14 MB)
> .text : 0xc0008000 - 0xc0de1d40 (14184 kB)
> .init : 0xc0de2000 - 0xc0e8a000 ( 672 kB)
> .data : 0xc0e8a000 - 0xc0f
