3rd party broadcom driver enablement

Annamalai Lakshmanan88

we have 3rd party WLAN component from Broadcom, They provide the driver as KO file. we using Linux kernel 3.8 as a base and jacinto 6 is the platform.

the WLAN SDIO lines are connected to MMC1. There is a GPIO wake line connected to the SOC pin. what are the necessary kernel changes required to enable this component. how to indicate the middleware layers about the SOC connection with the WLAN components and the GPIO pin.

over 8 years ago

0 Cvetolin Shulev-XID over 8 years ago

TI__Guru 65405 points

Hi Annamalai,

It is necessary to handle GPIO wakeup event. You can find more details from the linked thread:
e2e.ti.com/.../348520
Also see the a very simple driver example (not especially for Jacinto 6) that enables GPIO lines as wakeup sources:
lwn.net/.../

BR
Tsvetolin Shulev

0 Annamalai Lakshmanan88 over 8 years ago in reply to Cvetolin Shulev-XID

Mastermind 6285 points

Hi Shulev,thanks for your comments.
1) Should we also handle the information that MMC1 is connected with the WLAN SDIO pins, please provide information if 'yes', like in device tree or user space, some sample implementation?
thanksAnnamalai

0 Cvetolin Shulev-XID over 8 years ago in reply to Annamalai Lakshmanan88

TI__Guru 65405 points

Here is an example from Linux documentation about device tree GPIO wakeup configuration:
www.kernel.org/.../gpio-keys.txt

BR
Tsvetolin Shulev

0 Annamalai Lakshmanan88 over 8 years ago in reply to Cvetolin Shulev-XID

Mastermind 6285 points

thanks for your information regarding GPIO, But apart from GPIO, the SDIO lines are connected to MMC1 controller of the SOC. how do we notify the WiFi driver to send commands to MMC1, what is the link to notify that MMC1 is only being used do you have any clarity on this part. as WiFi is only a 3rd party driver it needs information on which MMC controller is being operated to function normally.

Processors

Processors forum

3rd party broadcom driver enablement