This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

SDIO-Bluetooth on OMAP-L138

Other Parts Discussed in Thread: OMAP-L138, WL1271

Hello.

I have a shiney new OMAP-L138 EVM board. The OMAP-L138 includes an SDIO interface and the EVM board provides access to the SDIO interface. I am attempting to use a Bluetooth radio via the SDIO interface. I'm using DaVinci-PSP-SDK-03.20.00.06 (linux 2.6.31). I've built the kernel with bluetooth and sdio support.

Here's a non-radio question, but I would be greatful for any feedback... When I insert the SDIO card, I would expect udev to register some event, but I see none ($ udevadm monitor --env). Am I correct that udev should detect the insertion?

I have several kernel modules that are relavent, but some remain a mystery. Here is an abriviated list of kernel modules from lsmod:

btsdio                  4752  0
hci_vhci                5288  0
mmc_block              10392  0
davinci_mmc             9828  0
sdhci_pltfm             3064  0
sdhci                  16812  1 sdhci_pltfm
mmc_core               55988  5 btsdio,sdio_uart,mmc_block,davinci_mmc,sdhci

Can you please help me understand which of these drivers are required?

Is the sdhci_pltfm driver necessary?

I wish my questions were more pointed, but I think I'm missing some pretty basic information.

If I wanted to create device nodes under /dev, what major and minor numbers would I use for sdio? The devices.txt file in the Documentation folder indicates that an MMC device is a block device with major number 179. Does sdio use the same major number?

Does anyone have experience using SDIO-Bluetooth that they wish to share?

 

Thank you very much,

Chris