Please, advice me what can I do with a same problem like in a post http://e2e.ti.com/support/low_power_rf/f/307/t/181835.aspx.
I have a next environment:
- BeagleBoard-xM C2.
- Linux 2.6.37.
- TiWi-BLE module (COM6L-BLE) from LS Reseach.
- Drivers from compat backports-3.11-rc3-1.
- I have configured pins correctly, because I successfully brought up wlan0 interface first time.
So, symptoms are the next:
First "modprobe":
modprobe wlcore_sdio
[ 28.873321] bus: 'sdio': add driver wl1271_sdio
[ 28.878265] bus: 'sdio': driver_probe_device: matched device mmc1:0001:1 with driver wl1271_sdio
[ 28.887603] bus: 'sdio': really_probe: probing driver wl1271_sdio with device mmc1:0001:1
[ 28.906890] wl1271_probe
[ 28.910491] dev->bus->probe(dev) failed
[ 28.914672] bus: 'sdio': driver_probe_device: matched device mmc1:0001:2 with driver wl1271_sdio
[ 28.924163] bus: 'sdio': really_probe: probing driver wl1271_sdio with device mmc1:0001:2
[ 29.084991] wl1271_probe
[ 29.088684] wl1271_sdio mmc1:0001:2: sdio PM caps = 0x0
[ 29.099395] Registering platform device 'wl12xx'. Parent at mmc1:0001:2
[ 29.106597] device: 'wl12xx': device_add
[ 29.110839] bus: 'platform': add device wl12xx
[ 29.115844] PM: Adding info for platform:wl12xx
But after that
rmmod wlcore_sdio
modprobe wlcore_sdio
I have errors:
[ 493.726196] bus: 'sdio': add driver wl1271_sdio
[ 493.731140] bus: 'sdio': driver_probe_device: matched device mmc1:0001:1 with driver wl1271_sdio
[ 493.740478] bus: 'sdio': really_probe: probing driver wl1271_sdio with device mmc1:0001:1
[ 493.753112] dev->bus->probe(dev) failed
[ 493.757049] wl1271_sdio: probe of mmc1:0001:1 failed with error -110
[ 493.764465] bus: 'sdio': driver_probe_device: matched device mmc1:0001:2 with driver wl1271_sdio
[ 493.773773] bus: 'sdio': really_probe: probing driver wl1271_sdio with device mmc1:0001:2
[ 493.797058] dev->bus->probe(dev) failed
[ 493.801116] wl1271_sdio: probe of mmc1:0001:2 failed with error -110
It even not enter to wl1271_probe.
Interrupts before rmmod wlcore_sdio:
root@dm37x-evm:~# cat /proc/interrupts
CPU0
7: 0 INTC TWL4030-PIH
11: 0 INTC prcm
12: 831 INTC DMA
20: 0 INTC gpmc
24: 0 INTC omap-iommu.0
25: 3 INTC OMAP DSS
37: 5389 INTC gp timer
56: 431 INTC omap_i2c
57: 0 INTC omap_i2c
61: 0 INTC omap_i2c
72: 0 INTC serial idle
73: 0 INTC serial idle
74: 280 INTC serial idle, OMAP UART2
77: 18416 INTC ehci_hcd:usb1
80: 0 INTC serial idle
83: 2441 INTC mmc0
86: 207 INTC mmc1
164: 0 GPIO user
297: 0 GPIO wl12xx
376: 0 twl4030 twl4030_pwrbutton
379: 0 twl4030 rtc0
384: 0 twl4030 mmc0
After:
root@dm37x-evm:~# cat /proc/interrupts
CPU0
7: 0 INTC TWL4030-PIH
11: 0 INTC prcm
12: 831 INTC DMA
20: 0 INTC gpmc
24: 0 INTC omap-iommu.0
25: 3 INTC OMAP DSS
37: 7419 INTC gp timer
56: 431 INTC omap_i2c
57: 0 INTC omap_i2c
61: 0 INTC omap_i2c
72: 0 INTC serial idle
73: 0 INTC serial idle
74: 375 INTC serial idle, OMAP UART2
77: 18630 INTC ehci_hcd:usb1
80: 0 INTC serial idle
83: 2441 INTC mmc0
86: 207 INTC mmc1
164: 0 GPIO user
376: 0 twl4030 twl4030_pwrbutton
379: 0 twl4030 rtc0
384: 0 twl4030 mmc0
So, I have no wl12xx interrupt:
297: 0 GPIO wl12xx
Link in solution is dead:
poo kalimada said:Me and Divya share the same setup, after applying the PM runtime patch from the following link
"http://lists.meego.com/pipermail/meego-kernel/2010-October/000674.html"