Skip to content
Permalink
Kiran-K/Blueto…
Switch branches/tags

Commits on Jun 8, 2021

  1. Bluetooth: Add support for msbc coding format

    In Enhanced_Setup_Synchronous_Command, add support for msbc
    coding format
    
    Signed-off-by: Kiran K <kiran.k@intel.com>
    Reviewed-by: Chethan T N <chethan.tumkur.narayan@intel.com>
    Reviewed-by: Srivatsa Ravishankar <ravishankar.srivatsa@intel.com>
    kirankrishnappa-intel authored and intel-lab-lkp committed Jun 8, 2021
  2. Bluetooth: Add support for HCI_Enhanced_Setup_Synchronous_Connection …

    …command
    
    < HCI Command: Enhanced Setup Synchronous Connection (0x01|0x003d) plen 59
            Handle: 256
            Transmit bandwidth: 8000
            Receive bandwidth: 8000
            Max latency: 13
            Packet type: 0x0380
              3-EV3 may not be used
              2-EV5 may not be used
              3-EV5 may not be used
            Retransmission effort: Optimize for link quality (0x02)
    > HCI Event: Command Status (0x0f) plen 4
          Enhanced Setup Synchronous Connection (0x01|0x003d) ncmd 1
            Status: Success (0x00)
    > HCI Event: Synchronous Connect Complete (0x2c) plen 17
            Status: Success (0x00)
            Handle: 257
            Address: CC:98:8B:92:04:FD (SONY Visual Products Inc.)
            Link type: eSCO (0x02)
            Transmission interval: 0x0c
            Retransmission window: 0x06
            RX packet length: 60
            TX packet length: 60
            Air mode: Transparent (0x03)
    
    Signed-off-by: Kiran K <kiran.k@intel.com>
    Reviewed-by: Chethan T N <chethan.tumkur.narayan@intel.com>
    Reviewed-by: Srivatsa Ravishankar <ravishankar.srivatsa@intel.com>
    kirankrishnappa-intel authored and intel-lab-lkp committed Jun 8, 2021
  3. Bluetooth: Add BT_CODEC option for setsockopt over SCO

    Add BT_CODEC option on setsockopt system call to allow user space
    audio modules to set codec. Driver also sets data path if non-HCI is
    selected.
    
    Signed-off-by: Kiran K <kiran.k@intel.com>
    Reviewed-by: Chethan T N <chethan.tumkur.narayan@intel.com>
    Reviewed-by: Srivatsa Ravishankar <ravishankar.srivatsa@intel.com>
    kirankrishnappa-intel authored and intel-lab-lkp committed Jun 8, 2021
  4. Bluetooth: btintel: define callback to set data path

    Adds callback function which is called to set the data path
    for HFP offload case before opening SCO connection
    
    Signed-off-by: Kiran K <kiran.k@intel.com>
    Reviewed-by: Chethan T N <chethan.tumkur.narayan@intel.com>
    Reviewed-by: Srivatsa Ravishankar <ravishankar.srivatsa@intel.com>
    kirankrishnappa-intel authored and intel-lab-lkp committed Jun 8, 2021
  5. Bluetooth: Add a callback function to set data path

    In HFP offload usecase, Intel controllers require offload use
    case id (NBS or WBS) to be set before opening SCO connection. Define
    a new callback which gets called on setsockopt SCO socket. User space
    audio module is expected to set codec via setsockopt(sk, BT_CODEC, ....)
    before opening SCO connection.
    
    Signed-off-by: Kiran K <kiran.k@intel.com>
    Reviewed-by: Chethan T N <chethan.tumkur.narayan@intel.com>
    Reviewed-by: Srivatsa Ravishankar <ravishankar.srivatsa@intel.com>
    kirankrishnappa-intel authored and intel-lab-lkp committed Jun 8, 2021
  6. Bluetooth: Add BT_CODEC option for getsockopt for SCO socket

    Add BT_CODEC option for getsockopt systemcall over SCO socket
    to expose the codecs supported by controller
    
    Signed-off-by: Kiran K <kiran.k@intel.com>
    Reviewed-by: Chethan T N <chethan.tumkur.narayan@intel.com>
    Reviewed-by: Srivatsa Ravishankar <ravishankar.srivatsa@intel.com>
    kirankrishnappa-intel authored and intel-lab-lkp committed Jun 8, 2021
  7. Bluetooth: btintel: set get_data_path callback

    Read supported offload usecases and set get_data_path callback if
    controller suppports offload codecs.
    
    Signed-off-by: Kiran K <kiran.k@intel.com>
    Reviewed-by: Chethan T N <chethan.tumkur.narayan@intel.com>
    Reviewed-by: Srivatsa Ravishankar <ravishankar.srivatsa@intel.com>
    kirankrishnappa-intel authored and intel-lab-lkp committed Jun 8, 2021
  8. Bluetooth: Add a callback function to retireve data path

    There is no standard HCI command to retrieve data path for transport.
    Add a new callback function to retrieve data path which is used
    in offload usecase. This needs to be set at setup stage if controller
    supports offload codecs
    
    Signed-off-by: Kiran K <kiran.k@intel.com>
    Reviewed-by: Chethan T N <chethan.tumkur.narayan@intel.com>
    Reviewed-by: Srivatsa Ravishankar <ravishankar.srivatsa@intel.com>
    kirankrishnappa-intel authored and intel-lab-lkp committed Jun 8, 2021
  9. Bluetooth: Add support for Read Local Supported Codecs V2

    Use V2 version of read local supported command is controller
    supports
    
    snoop:
    > HCI Event: Command Complete (0x0e) plen 20
          Read Local Supported Codecs V2 (0x04|0x000d) ncmd 1
            Status: Success (0x00)
            Number of supported codecs: 7
              Codec: u-law log (0x00)
              Logical Transport Type: 0x02
                Codec supported over BR/EDR SCO and eSCO
              Codec: A-law log (0x01)
              Logical Transport Type: 0x02
                Codec supported over BR/EDR SCO and eSCO
              Codec: CVSD (0x02)
              Logical Transport Type: 0x02
                Codec supported over BR/EDR SCO and eSCO
              Codec: Transparent (0x03)
              Logical Transport Type: 0x02
                Codec supported over BR/EDR SCO and eSCO
              Codec: Linear PCM (0x04)
              Logical Transport Type: 0x02
                Codec supported over BR/EDR SCO and eSCO
              Codec: Reserved (0x08)
              Logical Transport Type: 0x03
                Codec supported over BR/EDR ACL
                Codec supported over BR/EDR SCO and eSCO
              Codec: mSBC (0x05)
              Logical Transport Type: 0x03
                Codec supported over BR/EDR ACL
                Codec supported over BR/EDR SCO and eSCO
            Number of vendor codecs: 0
    ......
    < HCI Command: Read Local Suppor.. (0x04|0x000e) plen 7
            Codec: mSBC (0x05)
            Logical Transport Type: 0x00
            Direction: Input (Host to Controller) (0x00)
    > HCI Event: Command Complete (0x0e) plen 12
          Read Local Supported Codec Capabilities (0x04|0x000e) ncmd 1
            Status: Success (0x00)
            Number of codec capabilities: 1
             Capabilities #0:
            00 00 11 15 02 33
    
    Signed-off-by: Kiran K <kiran.k@intel.com>
    Signed-off-by: Chethan T N <chethan.tumkur.narayan@intel.com>
    Signed-off-by: Srivatsa Ravishankar <ravishankar.srivatsa@intel.com>
    kirankrishnappa-intel authored and intel-lab-lkp committed Jun 8, 2021
  10. Bluetooth: enumerate local supported codec and cache details

    Move reading of supported local codecs into a separate init function,
    query codecs capabilities and cache the data
    
    Signed-off-by: Kiran K <kiran.k@intel.com>
    Signed-off-by: Chethan T N <chethan.tumkur.narayan@intel.com>
    Signed-off-by: Srivatsa Ravishankar <ravishankar.srivatsa@intel.com>
    Reported-by: kernel test robot <lkp@intel.com>
    kirankrishnappa-intel authored and intel-lab-lkp committed Jun 8, 2021

Commits on Jun 4, 2021

  1. Bluetooth: use inclusive language when filtering devices

    This patch replaces some non-inclusive terms based on the appropriate
    language mapping table compiled by the Bluetooth SIG:
    https://specificationrefs.bluetooth.com/language-mapping/Appropriate_Language_Mapping_Table.pdf
    
    Specifically, these terms are replaced:
    blacklist -> reject list
    whitelist -> accept list
    
    Signed-off-by: Archie Pusaka <apusaka@chromium.org>
    Reviewed-by: Miao-chen Chou <mcchou@chromium.org>
    Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
    apusaka authored and holtmann committed Jun 4, 2021
  2. Bluetooth: use inclusive language when tracking connections

    This patch replaces some non-inclusive terms based on the appropriate
    language mapping table compiled by the Bluetooth SIG:
    https://specificationrefs.bluetooth.com/language-mapping/Appropriate_Language_Mapping_Table.pdf
    
    Specifically, these terms are replaced:
    master -> central
    slave  -> peripheral
    
    Signed-off-by: Archie Pusaka <apusaka@chromium.org>
    Reviewed-by: Miao-chen Chou <mcchou@chromium.org>
    Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
    apusaka authored and holtmann committed Jun 4, 2021
  3. Bluetooth: use inclusive language in HCI role comments

    This patch replaces some non-inclusive terms based on the appropriate
    language mapping table compiled by the Bluetooth SIG:
    https://specificationrefs.bluetooth.com/language-mapping/Appropriate_Language_Mapping_Table.pdf
    
    Specifically, these terms are replaced:
    master -> initiator (for smp) or central (everything else)
    slave  -> responder (for smp) or peripheral (everything else)
    
    The #define preprocessor terms are unchanged for now to not disturb
    dependent APIs.
    
    Signed-off-by: Archie Pusaka <apusaka@chromium.org>
    Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
    apusaka authored and holtmann committed Jun 4, 2021

Commits on Jun 3, 2021

  1. Bluetooth: smp: Use the correct print format

    According to Documentation/core-api/printk-formats.rst,
    Use the correct print format. Printing an unsigned int value should use %u
    instead of %d. Otherwise printk() might end up displaying negative numbers.
    
    Signed-off-by: Kai Ye <yekai13@huawei.com>
    Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
    yekai123123 authored and holtmann committed Jun 3, 2021
  2. Bluetooth: sco: Use the correct print format

    According to Documentation/core-api/printk-formats.rst,
    Use the correct print format. Printing an unsigned int value should use %u
    instead of %d. Otherwise printk() might end up displaying negative numbers.
    
    Signed-off-by: Kai Ye <yekai13@huawei.com>
    Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
    yekai123123 authored and holtmann committed Jun 3, 2021
  3. Bluetooth: msft: Use the correct print format

    According to Documentation/core-api/printk-formats.rst,
    Use the correct print format. Printing an unsigned int value should use %u
    instead of %d. Otherwise printk() might end up displaying negative numbers.
    
    Signed-off-by: Kai Ye <yekai13@huawei.com>
    Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
    yekai123123 authored and holtmann committed Jun 3, 2021
  4. Bluetooth: mgmt: Use the correct print format

    According to Documentation/core-api/printk-formats.rst,
    Use the correct print format. Printing an unsigned int value should use %u
    instead of %d. Otherwise printk() might end up displaying negative numbers.
    
    Signed-off-by: Kai Ye <yekai13@huawei.com>
    Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
    yekai123123 authored and holtmann committed Jun 3, 2021
  5. Bluetooth: amp: Use the correct print format

    According to Documentation/core-api/printk-formats.rst,
    Use the correct print format. Printing an unsigned int value should use %u
    instead of %d. Otherwise printk() might end up displaying negative numbers.
    
    Signed-off-by: Kai Ye <yekai13@huawei.com>
    Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
    yekai123123 authored and holtmann committed Jun 3, 2021
  6. Bluetooth: a2mp: Use the correct print format

    According to Documentation/core-api/printk-formats.rst,
    Use the correct print format. Printing an unsigned int value should use %u
    instead of %d. Otherwise printk() might end up displaying negative numbers.
    
    Signed-off-by: Kai Ye <yekai13@huawei.com>
    Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
    yekai123123 authored and holtmann committed Jun 3, 2021
  7. Bluetooth: 6lowpan: Use the correct print format

    According to Documentation/core-api/printk-formats.rst,
    Use the correct print format. Printing an unsigned int value should use %u
    instead of %d. Otherwise printk() might end up displaying negative numbers.
    
    Signed-off-by: Kai Ye <yekai13@huawei.com>
    Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
    yekai123123 authored and holtmann committed Jun 3, 2021
  8. Bluetooth: hidp: Use the correct print format

    According to Documentation/core-api/printk-formats.rst,
    Use the correct print format. Printing an unsigned int value should use %u
    instead of %d. Otherwise printk() might end up displaying negative numbers.
    
    Signed-off-by: Kai Ye <yekai13@huawei.com>
    Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
    yekai123123 authored and holtmann committed Jun 3, 2021
  9. Bluetooth: cmtp: Use the correct print format

    According to Documentation/core-api/printk-formats.rst,
    Use the correct print format. Printing an unsigned int value should use %u
    instead of %d. Otherwise printk() might end up displaying negative numbers.
    
    Signed-off-by: Kai Ye <yekai13@huawei.com>
    Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
    yekai123123 authored and holtmann committed Jun 3, 2021
  10. Bluetooth: bnep: Use the correct print format

    According to Documentation/core-api/printk-formats.rst,
    Use the correct print format. Printing an unsigned int value should use %u
    instead of %d. Otherwise printk() might end up displaying negative numbers.
    
    Signed-off-by: Kai Ye <yekai13@huawei.com>
    Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
    yekai123123 authored and holtmann committed Jun 3, 2021

Commits on Jun 2, 2021

  1. Bluetooth: Fix spelling mistakes

    Fix some spelling mistakes in comments:
    udpate  ==> update
    retreive  ==> retrieve
    accidentially  ==> accidentally
    correspondig  ==> corresponding
    adddress  ==> address
    estabilish  ==> establish
    commplete  ==> complete
    Unkown  ==> Unknown
    triggerd  ==> triggered
    transtion  ==> transition
    
    Signed-off-by: Zheng Yongjun <zhengyongjun3@huawei.com>
    Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
    Zheng Yongjun authored and holtmann committed Jun 2, 2021
  2. Bluetooth: btusb: Add a new USB ID for RTL8822CE

    Some models of the RTL8822ce utilize a different USB ID. Add this
    new one to the Bluetooth driver.
    
    Signed-off-by: Larry Finger <Larry.Finger@lwfinger.net>
    Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
    lwfinger authored and holtmann committed Jun 2, 2021
  3. Bluetooth: btusb: fix bt fiwmare downloading failure issue for qca bt…

    …soc.
    
    This is btsoc timing issue, after host start to downloading bt firmware,
    ep2 need time to switch from function acl to function dfu, so host add
    20ms delay as workaround.
    
    Signed-off-by: Tim Jiang <tjiang@codeaurora.org>
    Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
    tjiang123 authored and holtmann committed Jun 2, 2021
  4. Bluetooth: btusb: use default nvm if boardID is 0 for wcn6855.

    if boardID is 0, will use the default nvm file without surfix.
    
    Signed-off-by: Tim Jiang <tjiang@codeaurora.org>
    Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
    tjiang123 authored and holtmann committed Jun 2, 2021
  5. Bluetooth: btmtkuart: using pm_runtime_resume_and_get instead of pm_r…

    …untime_get_sync
    
    Using pm_runtime_resume_and_get is more appropriate
    for simplifing code
    
    Signed-off-by: Zhang Qilong <zhangqilong3@huawei.com>
    Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
    Zhang Qilong authored and holtmann committed Jun 2, 2021
  6. Bluetooth: use inclusive language in comments

    This patch replaces some non-inclusive terms based on the appropriate
    language mapping table compiled by the Bluetooth SIG:
    https://specificationrefs.bluetooth.com/language-mapping/Appropriate_Language_Mapping_Table.pdf
    
    Specifically, these terms are replaced:
    slave       -> peripheral
    blacklisted -> blocked
    
    Signed-off-by: Archie Pusaka <apusaka@chromium.org>
    Reviewed-by: Miao-chen Chou <mcchou@chromium.org>
    Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
    apusaka authored and holtmann committed Jun 2, 2021
  7. Bluetooth: use inclusive language in SMP

    This patch replaces some non-inclusive terms based on the appropriate
    language mapping table compiled by the Bluetooth SIG:
    https://specificationrefs.bluetooth.com/language-mapping/Appropriate_Language_Mapping_Table.pdf
    
    Specifically, these terms are replaced:
    master -> initiator
    slave  -> responder
    
    Signed-off-by: Archie Pusaka <apusaka@chromium.org>
    Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
    apusaka authored and holtmann committed Jun 2, 2021
  8. Bluetooth: use inclusive language in HCI LE features

    This patch replaces some non-inclusive terms based on the appropriate
    language mapping table compiled by the Bluetooth SIG:
    https://specificationrefs.bluetooth.com/language-mapping/Appropriate_Language_Mapping_Table.pdf
    
    Specifically, these terms are replaced:
    master -> central
    slave  -> peripheral
    
    Signed-off-by: Archie Pusaka <apusaka@chromium.org>
    Reviewed-by: Miao-chen Chou <mcchou@chromium.org>
    Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
    apusaka authored and holtmann committed Jun 2, 2021
  9. Bluetooth: use inclusive language to describe CPB

    This patch replaces some non-inclusive terms based on the appropriate
    language mapping table compiled by the Bluetooth SIG:
    https://specificationrefs.bluetooth.com/language-mapping/Appropriate_Language_Mapping_Table.pdf
    
    Specifically, these terms are replaced when describing the
    connectionless peripheral broadcast feature:
    master -> central
    slave  -> peripheral
    
    Signed-off-by: Archie Pusaka <apusaka@chromium.org>
    Reviewed-by: Miao-chen Chou <mcchou@chromium.org>
    Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
    apusaka authored and holtmann committed Jun 2, 2021
  10. Bluetooth: use inclusive language in hci_core.h

    This patch replaces some non-inclusive terms based on the appropriate
    language mapping table compiled by the Bluetooth SIG:
    https://specificationrefs.bluetooth.com/language-mapping/Appropriate_Language_Mapping_Table.pdf
    
    Specifically, these terms are replaced:
    master -> central
    slave  -> peripheral
    
    These attributes are not used elsewhere in the code.
    
    Signed-off-by: Archie Pusaka <apusaka@chromium.org>
    Reviewed-by: Miao-chen Chou <mcchou@chromium.org>
    Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
    apusaka authored and holtmann committed Jun 2, 2021
  11. Bluetooth: mgmt: Fix slab-out-of-bounds in tlv_data_is_valid

    This fixes parsing of LTV entries when the length is 0.
    
    Found with:
    
    tools/mgmt-tester -s "Add Advertising - Success (ScRsp only)"
    
    Add Advertising - Success (ScRsp only) - run
      Sending Add Advertising (0x003e)
      Test condition added, total 1
    [   11.004577] ==================================================================
    [   11.005292] BUG: KASAN: slab-out-of-bounds in tlv_data_is_valid+0x87/0xe0
    [   11.005984] Read of size 1 at addr ffff888002c695b0 by task mgmt-tester/87
    [   11.006711]
    [   11.007176]
    [   11.007429] Allocated by task 87:
    [   11.008151]
    [   11.008438] The buggy address belongs to the object at ffff888002c69580
    [   11.008438]  which belongs to the cache kmalloc-64 of size 64
    [   11.010526] The buggy address is located 48 bytes inside of
    [   11.010526]  64-byte region [ffff888002c69580, ffff888002c695c0)
    [   11.012423] The buggy address belongs to the page:
    [   11.013291]
    [   11.013544] Memory state around the buggy address:
    [   11.014359]  ffff888002c69480: fa fb fb fb fb fb fb fb fc fc fc fc fc fc fc fc
    [   11.015453]  ffff888002c69500: fb fb fb fb fb fb fb fb fc fc fc fc fc fc fc fc
    [   11.016232] >ffff888002c69580: 00 00 00 00 00 00 fc fc fc fc fc fc fc fc fc fc
    [   11.017010]                                      ^
    [   11.017547]  ffff888002c69600: 00 00 00 00 00 00 fc fc fc fc fc fc fc fc fc fc
    [   11.018296]  ffff888002c69680: fb fb fb fb fb fb fb fb fc fc fc fc fc fc fc fc
    [   11.019116] ==================================================================
    
    Fixes: 2bb3687 ("Bluetooth: Unify advertising instance flags check")
    Signed-off-by: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
    Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
    Vudentz authored and holtmann committed Jun 2, 2021
  12. Bluetooth: btrtl: rename USB fw for RTL8761

    According Realteks own BT drivers firmware RTL8761B is for UART
    and RTL8761BU is for USB.
    
    Change existing 8761B to UART and add an 8761BU entry for USB
    
    Signed-off-by: Joakim Tjernlund <Joakim.Tjernlund@infinera.com>
    Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
    joakim-tjernlund authored and holtmann committed Jun 2, 2021
Older