• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 40 subscribers
  • Views 501 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

WL183x Bluetooth Configuration

Brad Griffis
Guru*** 125430 points
Other Parts Discussed in Thread: WL1831

WL1831 with non-TI host processor

Linux 4.1 kernel

  1. When I'm using backports to build the Wi-Fi portion, are the Bluetooth-related drivers also part of backports or are they expected to come from the "native" kernel?  I see firmware mentioned in the build scripts, but I don't see anything related to drivers for Bluetooth.
  2. What kernel config options need to be configured for  BT?  
    1. One thing that confuses me is CONFIG_BT_WILINK.  All of our boards have a section called "btwilink" which appears to be defined in drivers/bluetooth/btwilink.c, though it looks like that's only built if CONFIG_BT_WILINK is defined, and I don't see that defined in any of the TI configurations from our SDK.  Is CONFIG_BT_WILINK needed?  If not, is the "btwilink" portion needed in dts?
    2. Other ones that I'm not sure how they should be configured include CONFIG_BT, CONFIG_BT_BREDR, CONFIG_BT_HS, CONFIG_BT_LE, CONFIG_WL_TI?

Thanks,
Brad

  • 0
    TI__Mastermind 20285 points

    Hi brad,

    All the BT related switches in the kernel including btwilink are used for Bluez.

    Cybercom stack is in user space (similar to blutopia in that sense) so it doesnt really neef any of those.

    The handle the. UART port directly and load the init script from their application.

    BR

    Eyal