setting 界面开始搜索的时候，通常也会同时进行le scan，这一点在inquiry流程之命令下发中已经讲述。此篇文章主要是分析一下对于controller 搜索到的广播包的处理。这里以Android O的bluedroid的代码作为分析对象。

  1. void btu_hci_msg_process(BT_HDR* p_msg) {
  2.   /* Determine the input message type. */
  3.   switch (p_msg->event & BT_EVT_MASK) {
  4.     case BT_EVT_TO_BTU_HCI_ACL:
  5.       /* All Acl Data goes to L2CAP */
  6.       l2c_rcv_acl_data(p_msg);
  7.       break;
  8.  
  9.     case BT_EVT_TO_BTU_L2C_SEG_XMIT:
  10.       /* L2CAP segment transmit complete */
  11.       l2c_link_segments_xmitted(p_msg);
  12.       break;
  13.  
  14.     case BT_EVT_TO_BTU_HCI_SCO:
  15. #if (BTM_SCO_INCLUDED == TRUE)
  16.       btm_route_sco_data(p_msg);
  17.       break;
  18. #endif
  19.  
  20.     case BT_EVT_TO_BTU_HCI_EVT:
  21.       btu_hcif_process_event((uint8_t)(p_msg->event & BT_SUB_EVT_MASK), p_msg);
  22.       osi_free(p_msg);
  23.       break;
  24.  
  25.     case BT_EVT_TO_BTU_HCI_CMD:
  26.       btu_hcif_send_cmd((uint8_t)(p_msg->event & BT_SUB_EVT_MASK), p_msg);
  27.       break;
  28.  
  29.     default:
  30.       osi_free(p_msg);
  31.       break;
  32.   }
  33. }

上面可以看出 btu_hci_msg_process 的所有的处理对象。hci event 的处理函数 是btu_hcif_process_event((uint8_t)(p_msg->event & BT_SUB_EVT_MASK), p_msg);

  1. void btu_hcif_process_event(UNUSED_ATTR uint8_t controller_id, BT_HDR* p_msg) {
  2.   uint8_t* p = (uint8_t*)(p_msg + ) + p_msg->offset;
  3.   uint8_t hci_evt_code, hci_evt_len;
  4.   uint8_t ble_sub_code;
  5.   STREAM_TO_UINT8(hci_evt_code, p);
  6.   STREAM_TO_UINT8(hci_evt_len, p);
  7.  
  8.   switch (hci_evt_code) {
  9.     case HCI_INQUIRY_COMP_EVT:
  10.       btu_hcif_inquiry_comp_evt(p);
  11.       break;
  12.     case HCI_INQUIRY_RESULT_EVT:
  13.       btu_hcif_inquiry_result_evt(p);
  14.       break;
  15.     case HCI_INQUIRY_RSSI_RESULT_EVT:
  16.       btu_hcif_inquiry_rssi_result_evt(p);
  17.       break;
  18. ...
  19.     case HCI_BLE_EVENT: { //le 相关的event
  20.       STREAM_TO_UINT8(ble_sub_code, p);
  21.  
  22.       uint8_t ble_evt_len = hci_evt_len - ;
  23.       switch (ble_sub_code) {  //判断子event
  24.         case HCI_BLE_ADV_PKT_RPT_EVT: /* result of inquiry */
  25.           HCI_TRACE_EVENT("HCI_BLE_ADV_PKT_RPT_EVT");
  26.           btm_ble_process_adv_pkt(ble_evt_len, p);//处理广播包
  27.           break;
  28.         case HCI_BLE_CONN_COMPLETE_EVT:
  29.           btu_ble_ll_conn_complete_evt(p, hci_evt_len);
  30.           break;
  31.         case HCI_BLE_LL_CONN_PARAM_UPD_EVT:
  32.           btu_ble_ll_conn_param_upd_evt(p, hci_evt_len);
  33.           break;
  34. ...

从上面可以看出 btu_hcif_process_event可以处理的event 的类型，并且可以看出处理广播包的函数 是 btm_ble_process_adv_pkt(ble_evt_len, p);从函数名称可以看出此时函数已经进入到btm 模块，其实现在btm_ble_gap.cc

  1. /**
  2.  * This function is called when advertising report event is received. It updates
  3.  * the inquiry database. If the inquiry database is full, the oldest entry is
  4.  * discarded.
  5.  */
  6. void btm_ble_process_adv_pkt(uint8_t data_len, uint8_t* data) {
  7.   BD_ADDR bda;
  8.   uint8_t* p = data;
  9.   uint8_t legacy_evt_type, addr_type, num_reports, pkt_data_len;
  10.   int8_t rssi;
  11.  
  12.   /* Extract the number of reports in this event. */
  13.   STREAM_TO_UINT8(num_reports, p);//一个包里面可能有多个event，但是通常只有一个event
  14.  
  15.   while (num_reports--) {
  16.  
  17.     /* Extract inquiry results */
  18.     STREAM_TO_UINT8(legacy_evt_type, p);//event_type
  19.     STREAM_TO_UINT8(addr_type, p);//地址类型
  20.     STREAM_TO_BDADDR(bda, p);//地址
  21.     STREAM_TO_UINT8(pkt_data_len, p);//数据长度
  22.  
  23.     uint8_t* pkt_data = p;
  24.     p += pkt_data_len; /* Advance to the the rssi byte */
  25.  
  26.     STREAM_TO_INT8(rssi, p);//此时指针指向数据末尾的rssi
  27.  
  28.     btm_ble_process_adv_addr(bda, addr_type);//处理地址相关
  29.  
  30.     uint16_t event_type;
  31.     if (legacy_evt_type == 0x00) {  // ADV_IND;
  32.       event_type = 0x0013;
  33.     } else if (legacy_evt_type == 0x01) {  // ADV_DIRECT_IND;
  34.       event_type = 0x0015;
  35.     } else if (legacy_evt_type == 0x02) {  // ADV_SCAN_IND;
  36.       event_type = 0x0012;
  37.     } else if (legacy_evt_type == 0x03) {  // ADV_NONCONN_IND;
  38.       event_type = 0x0010;
  39.     } else if (legacy_evt_type == 0x04) {  // SCAN_RSP;
  40.       // We can't distinguish between "SCAN_RSP to an ADV_IND", and "SCAN_RSP to
  41.       // an ADV_SCAN_IND", so always return "SCAN_RSP to an ADV_IND"
  42.       event_type = 0x001B;
  43.     }
  44.     btm_ble_process_adv_pkt_cont(
  45.         event_type, addr_type, bda, PHY_LE_1M, PHY_LE_NO_PACKET, NO_ADI_PRESENT,
  46.         TX_POWER_NOT_PRESENT, rssi, 0x00 /* no periodic adv */, pkt_data_len,
  47.         pkt_data);//开始处理数据包
  48.   }
  49. }

可以看出主要的 主要的处理流程是执行btm_ble_process_adv_pkt_cont，我们看看具体的实现：

  1. /*******************************************************************************
  2. **
  3. ** Function         btm_ble_process_adv_pkt_cont
  4. **
  5. ** Description      This function is called after random address resolution is
  6. **                  done, and proceed to process adv packet.
  7. **
  8. ** Parameters
  9. **
  10. ** Returns          void
  11. **
  12. *******************************************************************************/
  13. static void btm_ble_process_adv_pkt_cont(BD_ADDR bda, UINT8 addr_type, UINT8 evt_type, UINT8 *p)
  14. {
  15.     tINQ_DB_ENT          *p_i;
  16.     tBTM_INQUIRY_VAR_ST  *p_inq = &btm_cb.btm_inq_vars;
  17.     tBTM_INQ_RESULTS_CB  *p_inq_results_cb = p_inq->p_inq_results_cb;
  18.     tBTM_INQ_RESULTS_CB  *p_obs_results_cb = btm_cb.ble_ctr_cb.p_obs_results_cb;
  19.     tBTM_BLE_INQ_CB      *p_le_inq_cb = &btm_cb.ble_ctr_cb.inq_var;
  20.     BOOLEAN     update = TRUE;
  21.     UINT8       result = ;
  22.  
  23.     p_i = btm_inq_db_find (bda);
  24.     /* Check if this address has already been processed for this inquiry */
  25.     if (btm_inq_find_bdaddr(bda))//check 这个地址的设备是否已经被处理过
  26.     {
  27.         /* never been report as an LE device */
  28.         if (p_i &&
  29.             (!(p_i->inq_info.results.device_type & BT_DEVICE_TYPE_BLE) ||
  30.               /* scan repsonse to be updated */
  31.               (!p_i->scan_rsp)))//这里update的判断条件是device type是否已经定位以及是否有scan response
  32.         {
  33.             update = TRUE;
  34.         }
  35.         else if (BTM_BLE_IS_OBS_ACTIVE(btm_cb.ble_ctr_cb.scan_activity))
  36.         {
  37.             update = FALSE;
  38.         }
  39.         else
  40.         {
  41.             /* if yes, skip it */
  42.             return; /* assumption: one result per event */
  43.         }
  44.     }
  45.     /* If existing entry, use that, else get  a new one (possibly reusing the oldest) */
  46.     if (p_i == NULL)//没有entry，重新分配
  47.     {
  48.         if ((p_i = btm_inq_db_new (bda)) != NULL)
  49.         {
  50.             p_inq->inq_cmpl_info.num_resp++;
  51.         }
  52.         else
  53.             return;
  54.     }
  55.     else if (p_i->inq_count != p_inq->inq_counter) /* first time seen in this inquiry */ /*在这一次的inquiry 中第一次见到该设备*/
  56.     {
  57.         p_inq->inq_cmpl_info.num_resp++;
  58.     }
  59.     /* update the LE device information in inquiry database */
  60.     if (!btm_ble_update_inq_result(p_i, addr_type, evt_type, p))//更新数据库
  61.         return;
  62.  
  63.     if ((result = btm_ble_is_discoverable(bda, evt_type, p)) == )//检测adv包中标志位
  64.     {
  65.       LOG_WARN("%s device is no longer discoverable so discarding advertising packet pkt",
  66.           __func__);
  67.         return;
  68.     }
  69.     if (!update)
  70.         result &= ~BTM_BLE_INQ_RESULT;
  71. ...
  72.     /* background connection in selective connection mode */
  73.         BTM_TRACE_WARNING("btm_cb.ble_ctr_cb.bg_conn_type = %d libs_liu",btm_cb.ble_ctr_cb.bg_conn_type);
  74.     if (btm_cb.ble_ctr_cb.bg_conn_type == BTM_BLE_CONN_SELECTIVE)
  75.     {
  76.         if (result & BTM_BLE_SEL_CONN_RESULT)
  77.             btm_send_sel_conn_callback(bda, evt_type, p, addr_type);
  78.         else
  79.         {
  80.             BTM_TRACE_DEBUG("None LE device, can not initiate selective connection");
  81.         }
  82.     }
  83.     else
  84.     {
  85.         if (p_inq_results_cb && (result & BTM_BLE_INQ_RESULT))
  86.         {
  87.             (p_inq_results_cb)((tBTM_INQ_RESULTS *) &p_i->inq_info.results, p_le_inq_cb->adv_data_cache);//处理结果
  88.         }
  89.         if (p_obs_results_cb && (result & BTM_BLE_OBS_RESULT))
  90.         {
  91.             (p_obs_results_cb)((tBTM_INQ_RESULTS *) &p_i->inq_info.results, p_le_inq_cb->adv_data_cache);
  92.         }
  93.     }
  94. }

从上面处理流程来看，主要是做了四件事：

  1. 查询设备数据库，并且判断该广播信息已经被处理过。
  2. btm_ble_update_inq_result(p_i, addr_type, evt_type, p) 更新设备数据库中的设备信息
  3. btm_ble_is_discoverable(bda, evt_type, p)  判断设备信息标志位，判断是否是可以发现的类型。
  4. 调用p_inq_results_cb 来处理 设备信息。这个在BTM_StartInquiry的时候传入参数bta_dm_inq_results_cb，调用的也就是这个回调函数。

下面主要分析一下2，3，4三个点：

2.btm_ble_update_inq_result(p_i, addr_type, evt_type, p)

  1. /*******************************************************************************
  2. **
  3. ** Function         btm_ble_update_inq_result
  4. **
  5. ** Description      Update adv packet information into inquiry result.
  6. **
  7. ** Parameters
  8. **
  9. ** Returns          void
  10. **
  11. *******************************************************************************/
  12. BOOLEAN btm_ble_update_inq_result(tINQ_DB_ENT *p_i, UINT8 addr_type, UINT8 evt_type, UINT8 *p)
  13. {
  14.     BOOLEAN             to_report = TRUE;
  15.     tBTM_INQ_RESULTS     *p_cur = &p_i->inq_info.results;
  16.     UINT8               len;
  17.     UINT8               *p_flag;
  18.     tBTM_INQUIRY_VAR_ST  *p_inq = &btm_cb.btm_inq_vars;
  19.     UINT8                data_len, rssi;
  20.     tBTM_BLE_INQ_CB     *p_le_inq_cb = &btm_cb.ble_ctr_cb.inq_var;
  21.     UINT8 *p1;
  22.     UINT8               *p_uuid16;
  23.  
  24.     STREAM_TO_UINT8    (data_len, p);
  25.  
  26.     btm_ble_cache_adv_data(p_cur, data_len, p, evt_type);// cache adv data
  27.  
  28.     p1 = (p + data_len);
  29.     STREAM_TO_UINT8 (rssi, p1);
  30.  
  31.     /* Save the info */
  32.     p_cur->inq_result_type = BTM_INQ_RESULT_BLE;
  33.     p_cur->ble_addr_type    = addr_type;
  34.     p_cur->rssi = rssi;
  35.     /* active scan, always wait until get scan_rsp to report the result */
  36.     if ((btm_cb.ble_ctr_cb.inq_var.scan_type == BTM_BLE_SCAN_MODE_ACTI &&  //如果是active scan，那么要等scan response 上来之后才会一起report，一个单独的BTM_BLE_CONNECT_EVT或者BTM_BLE_DISCOVER_EVT是不会上报的
  37.          (evt_type == BTM_BLE_CONNECT_EVT || evt_type == BTM_BLE_DISCOVER_EVT)))
  38.     {
  39.         BTM_TRACE_DEBUG("btm_ble_update_inq_result scan_rsp=false, to_report=false,\
  40.                               scan_type_active=%d", btm_cb.ble_ctr_cb.inq_var.scan_type);
  41.         p_i->scan_rsp = FALSE;
  42.         to_report = FALSE;
  43.     }
  44.     else
  45.         p_i->scan_rsp = TRUE;//拿到scan response
  46.  
  47.     if (p_i->inq_count != p_inq->inq_counter)
  48.         p_cur->device_type = BT_DEVICE_TYPE_BLE;//这次inquiry的第一次处理
  49.     else
  50.         p_cur->device_type |= BT_DEVICE_TYPE_BLE;//if(p_i->inq_count == p_inq->inq_counter) indicated that has been updated ，至少是BLE
  51.  
  52.     if (evt_type != BTM_BLE_SCAN_RSP_EVT)
  53.         p_cur->ble_evt_type     = evt_type;
  54.  
  55.     p_i->inq_count = p_inq->inq_counter;   /* Mark entry for current inquiry */
  56.  
  57.     if (p_le_inq_cb->adv_len != )
  58.     {
  59.         if ((p_flag = BTM_CheckAdvData(p_le_inq_cb->adv_data_cache, BTM_BLE_AD_TYPE_FLAG, &len)) != NULL)//读取flag
  60.             p_cur->flag = * p_flag;
  61.     }
  62.  
  63.     if (p_le_inq_cb->adv_len != )
  64.     {
  65.         /* Check to see the BLE device has the Appearance UUID in the advertising data.  If it does
  66.          * then try to convert the appearance value to a class of device value Bluedroid can use.
  67.          * Otherwise fall back to trying to infer if it is a HID device based on the service class.
  68.          */
  69.         p_uuid16 = BTM_CheckAdvData(p_le_inq_cb->adv_data_cache, BTM_BLE_AD_TYPE_APPEARANCE, &len);
  70.         if (p_uuid16 && len == )
  71.         {
  72.             btm_ble_appearance_to_cod((UINT16)p_uuid16[] | (p_uuid16[] << ), p_cur->dev_class);
  73.         }
  74.         else
  75.         {
  76.             if ((p_uuid16 = BTM_CheckAdvData(p_le_inq_cb->adv_data_cache,
  77.                                              BTM_BLE_AD_TYPE_16SRV_CMPL, &len)) != NULL)
  78.             {
  79.                 UINT8 i;
  80.                 for (i = ; i +  <= len; i = i + )
  81.                 {
  82.                     /* if this BLE device support HID over LE, set HID Major in class of device */
  83.                     if ((p_uuid16[i] | (p_uuid16[i+] << )) == UUID_SERVCLASS_LE_HID)
  84.                     {
  85.                         p_cur->dev_class[] = ;
  86.                         p_cur->dev_class[] = BTM_COD_MAJOR_PERIPHERAL;
  87.                         p_cur->dev_class[] = ;
  88.                         break;
  89.                     }
  90.                 }
  91.             }
  92.         }
  93.     }
  94.  
  95.     /* if BR/EDR not supported is not set, assume is a DUMO device */
  96.     if ((p_cur->flag & BTM_BLE_BREDR_NOT_SPT) ==  &&
  97.          evt_type != BTM_BLE_CONNECT_DIR_EVT)
  98.     {
  99.         if (p_cur->ble_addr_type != BLE_ADDR_RANDOM)
  100.         {
  101.             BTM_TRACE_DEBUG("BR/EDR NOT support bit not set, treat as DUMO");
  102.             p_cur->device_type |= BT_DEVICE_TYPE_DUMO;
  103.         } else {
  104.             BTM_TRACE_DEBUG("Random address, treating device as LE only");
  105.         }
  106.     }
  107.     else
  108.     {
  109.         BTM_TRACE_DEBUG("BR/EDR NOT SUPPORT bit set, LE only device");
  110.     }
  111.     return to_report;
  112. }

这里主要就是更新设备的信息。读取adv 包中的 flag等值，判断这个包是否要上报，以及更新device type。另外会根据BTM_BLE_AD_TYPE_APPEARANCE = 0x19 来判断device class-->btm_ble_appearance_to_cod

3.btm_ble_is_discoverable(bda, evt_type, p)

  1. /*******************************************************************************
  2. **
  3. ** Function         btm_ble_is_discoverable
  4. **
  5. ** Description      check ADV flag to make sure device is discoverable and match
  6. **                  the search condition
  7. **
  8. ** Parameters
  9. **
  10. ** Returns          void
  11. **
  12. *******************************************************************************/
  13. UINT8 btm_ble_is_discoverable(BD_ADDR bda, UINT8 evt_type, UINT8 *p)
  14. {
  15.     UINT8               *p_flag, flag = , rt = ;
  16.     UINT8                data_len;
  17.     tBTM_INQ_PARMS      *p_cond = &btm_cb.btm_inq_vars.inqparms;
  18.     tBTM_BLE_INQ_CB     *p_le_inq_cb = &btm_cb.ble_ctr_cb.inq_var;
  19.  
  20.     /* for observer, always "discoverable */
  21.     if (BTM_BLE_IS_OBS_ACTIVE(btm_cb.ble_ctr_cb.scan_activity))//这里注意，如果是observation，那么总是可以发现的
  22.         rt |= BTM_BLE_OBS_RESULT;
  23.  
  24.     if (BTM_BLE_IS_SEL_CONN_ACTIVE(btm_cb.ble_ctr_cb.scan_activity) &&
  25.         (evt_type == BTM_BLE_CONNECT_EVT || evt_type == BTM_BLE_CONNECT_DIR_EVT))
  26.         rt |= BTM_BLE_SEL_CONN_RESULT;
  27.  
  28.     if (p_le_inq_cb->adv_len != )
  29.     {
  30.         if ((p_flag = BTM_CheckAdvData(p_le_inq_cb->adv_data_cache,
  31.             BTM_BLE_AD_TYPE_FLAG, &data_len)) != NULL)//读取标志位并且判断
  32.         {
  33.             flag = * p_flag;
  34.  
  35.             if ((btm_cb.btm_inq_vars.inq_active & BTM_BLE_GENERAL_INQUIRY) &&
  36.                 (flag & (BTM_BLE_LIMIT_DISC_FLAG|BTM_BLE_GEN_DISC_FLAG)) != )
  37.             {
  38.                 BTM_TRACE_DEBUG("Find Generable Discoverable device");
  39.                 rt |= BTM_BLE_INQ_RESULT;
  40.             }
  41.  
  42.             else if (btm_cb.btm_inq_vars.inq_active & BTM_BLE_LIMITED_INQUIRY &&
  43.                      (flag & BTM_BLE_LIMIT_DISC_FLAG) != )
  44.             {
  45.                 BTM_TRACE_DEBUG("Find limited discoverable device");
  46.                 rt |= BTM_BLE_INQ_RESULT;
  47.             }
  48.         }
  49.     }
  50.     return rt;
  51. }

上面代码主要作用就是解析adv包中的标志位，然后做解析。并且决定是否要继续处理这个包，如果rt = 0 ，那么就不会继续处理这个包。这里注意如果是observation ，那么这个包总是可以发现的。

4.bta_dm_inq_results_cb

下面来分析这个 最重要的函数：

  1. /*******************************************************************************
  2. **
  3. ** Function         bta_dm_inq_results_cb
  4. **
  5. ** Description      Inquiry results callback from BTM
  6. **
  7. ** Returns          void
  8. **
  9. *******************************************************************************/
  10. static void bta_dm_inq_results_cb (tBTM_INQ_RESULTS *p_inq, UINT8 *p_eir)
  11. {
  12.  
  13.     tBTA_DM_SEARCH     result;//使用这个结果上报结果
  14.     tBTM_INQ_INFO      *p_inq_info;
  15.     UINT16             service_class;
  16.  
  17.     bdcpy(result.inq_res.bd_addr, p_inq->remote_bd_addr);//填充address
  18.     memcpy(result.inq_res.dev_class, p_inq->dev_class, DEV_CLASS_LEN);//填充device class
  19.     BTM_COD_SERVICE_CLASS(service_class, p_inq->dev_class);
  20.     result.inq_res.is_limited = (service_class & BTM_COD_SERVICE_LMTD_DISCOVER)?TRUE:FALSE;
  21.     result.inq_res.rssi = p_inq->rssi;//rssi
  22.  
  23. #if (BLE_INCLUDED == TRUE)
  24.     result.inq_res.ble_addr_type    = p_inq->ble_addr_type;
  25.     result.inq_res.inq_result_type  = p_inq->inq_result_type;
  26.     result.inq_res.device_type      = p_inq->device_type;
  27.     result.inq_res.flag             = p_inq->flag;//填充flag
  28. #endif
  29.  
  30.     /* application will parse EIR to find out remote device name */
  31.     result.inq_res.p_eir = p_eir;
  32.  
  33.     if((p_inq_info = BTM_InqDbRead(p_inq->remote_bd_addr)) != NULL)
  34.     {
  35.         /* initialize remt_name_not_required to FALSE so that we get the name by default */
  36.         result.inq_res.remt_name_not_required = FALSE;
  37.     }
  38.  
  39.     if(bta_dm_search_cb.p_search_cback)//回调
  40.         bta_dm_search_cb.p_search_cback(BTA_DM_INQ_RES_EVT, &result);
  41.  
  42.     if(p_inq_info)
  43.     {
  44.         /* application indicates if it knows the remote name, inside the callback
  45.          copy that to the inquiry data base*/
  46.         if(result.inq_res.remt_name_not_required)
  47.             p_inq_info->appl_knows_rem_name = TRUE;//如果application已经知道名字
  48.  
  49.     }
  50.  
  51. }

这里的逻辑也比较简单，构造了一个tBTA_DM_SEARCH来上报事件，上报的事件的函数就是bta_dm_search_cb.p_search_cback = bte_search_devices_evt，我们来看看其具体的实现：

  1. /*******************************************************************************
  2. **
  3. ** Function         bte_search_devices_evt
  4. **
  5. ** Description      Switches context from BTE to BTIF for DM search events
  6. **
  7. ** Returns          void
  8. **
  9. *******************************************************************************/
  10. static void bte_search_devices_evt(tBTA_DM_SEARCH_EVT event, tBTA_DM_SEARCH *p_data)
  11. {
  12.     UINT16 param_len = ;
  13.     if (p_data)
  14.         param_len += sizeof(tBTA_DM_SEARCH);
  15.     /* Allocate buffer to hold the pointers (deep copy). The pointers will point to the end of the tBTA_DM_SEARCH */
  16.     switch (event)
  17.     {
  18.         case BTA_DM_INQ_RES_EVT:
  19.         {
  20.             if (p_data->inq_res.p_eir)
  21.                 param_len += HCI_EXT_INQ_RESPONSE_LEN;
  22.         }
  23.         break;
  24. ...
  25.     /* if remote name is available in EIR, set teh flag so that stack doesnt trigger RNR */
  26.     if (event == BTA_DM_INQ_RES_EVT){
  27.         p_data->inq_res.remt_name_not_required = check_eir_remote_name(p_data, NULL, NULL);//这里check data 里面是否有名字，如果有的话，设置result 的标志位，协议栈就不会去查询名字
  28.         }
  29.     btif_transfer_context (btif_dm_search_devices_evt , (UINT16) event, (void *)p_data, param_len,
  30.         (param_len > sizeof(tBTA_DM_SEARCH)) ? search_devices_copy_cb : NULL);
  31. }

这里主要就是check 名字。然后transfer 到btif 线程去执行，我们继续看：

  1. /******************************************************************************
  2. **
  3. ** Function         btif_dm_search_devices_evt
  4. **
  5. ** Description      Executes search devices callback events in btif context
  6. **
  7. ** Returns          void
  8. **
  9. ******************************************************************************/
  10. static void btif_dm_search_devices_evt (UINT16 event, char *p_param)
  11. {
  12.     tBTA_DM_SEARCH *p_search_data;
  13.     BTIF_TRACE_EVENT("%s event=%s", __FUNCTION__, dump_dm_search_event(event));
  14.  
  15.     switch (event)
  16.     {
  17. ...
  18.  case BTA_DM_INQ_RES_EVT:
  19.         {
  20.             /* inquiry result */
  21.             UINT32 cod;
  22.             bt_bdname_t bdname;
  23.             bt_bdaddr_t bdaddr;
  24.             UINT8 remote_name_len;
  25.             tBTA_SERVICE_MASK services = ;
  26.             bdstr_t bdstr;
  27.  
  28.             p_search_data = (tBTA_DM_SEARCH *)p_param;//获得数据
  29.             bdcpy(bdaddr.address, p_search_data->inq_res.bd_addr);//获得地址
  30.  
  31.             bdname.name[] = ;
  32.  
  33.             cod = devclass2uint (p_search_data->inq_res.dev_class);//cod
  34.  
  35.             if (!check_eir_remote_name(p_search_data, bdname.name, &remote_name_len))
  36.                 check_cached_remote_name(p_search_data, bdname.name, &remote_name_len);//如果data里面没有名字，那么就查找cache里面的名字
  37.  
  38.             /* Check EIR for remote name and services */
  39.             if (p_search_data->inq_res.p_eir)
  40.             {
  41.                 BTA_GetEirService(p_search_data->inq_res.p_eir, &services);
  42.                 BTIF_TRACE_DEBUG("%s()EIR BTA services = %08X", __FUNCTION__, (UINT32)services);
  43.                 /* TODO:  Get the service list and check to see which uuids we got and send it back to the client. */
  44.             }
  45.  
  46.             {
  47.                 bt_property_t properties[];
  48.                 bt_device_type_t dev_type;
  49.                 uint32_t num_properties = ;
  50.                 bt_status_t status;
  51.                 int addr_type = ;
  52.  
  53.                 memset(properties, , sizeof(properties));
  54.                 /* BD_ADDR */
  55.                 BTIF_STORAGE_FILL_PROPERTY(&properties[num_properties],
  56.                                     BT_PROPERTY_BDADDR, sizeof(bdaddr), &bdaddr);//保存地址
  57.                 num_properties++;
  58.                 /* BD_NAME */
  59.                 /* Don't send BDNAME if it is empty */
  60.                 if (bdname.name[])
  61.                 {
  62.                     BTIF_STORAGE_FILL_PROPERTY(&properties[num_properties],
  63.                                                BT_PROPERTY_BDNAME,
  64.                                                strlen((char *)bdname.name), &bdname);//保存名字
  65.                     num_properties++;
  66.                 }
  67.  
  68.                 /* DEV_CLASS */
  69.                 BTIF_STORAGE_FILL_PROPERTY(&properties[num_properties],
  70.                                     BT_PROPERTY_CLASS_OF_DEVICE, sizeof(cod), &cod);//保存cod
  71.                 num_properties++;
  72.                 /* DEV_TYPE */
  73. #if (defined(BLE_INCLUDED) && (BLE_INCLUDED == TRUE))
  74.                 /* FixMe: Assumption is that bluetooth.h and BTE enums match */
  75.  
  76.                 /* Verify if the device is dual mode in NVRAM */
  77.                 int stored_device_type = ;
  78.                 if (btif_get_device_type(bdaddr.address, &stored_device_type) &&
  79.                     ((stored_device_type == BT_DEVICE_TYPE_BLE &&
  80.                         p_search_data->inq_res.device_type == BT_DEVICE_TYPE_BREDR) ||
  81.                      (stored_device_type == BT_DEVICE_TYPE_BREDR &&
  82.                         p_search_data->inq_res.device_type == BT_DEVICE_TYPE_BLE))) {
  83.                     dev_type = BT_DEVICE_TYPE_DUMO;
  84.                 } else {
  85.                     dev_type = p_search_data->inq_res.device_type;
  86.                 }
  87.  
  88.                 if (p_search_data->inq_res.device_type == BT_DEVICE_TYPE_BLE)
  89.                     addr_type = p_search_data->inq_res.ble_addr_type;
  90. #else
  91.                 dev_type = BT_DEVICE_TYPE_BREDR;
  92. #endif
  93.                 BTIF_STORAGE_FILL_PROPERTY(&properties[num_properties],
  94.                                     BT_PROPERTY_TYPE_OF_DEVICE, sizeof(dev_type), &dev_type);//保存dev type
  95.                 num_properties++;
  96.                 /* RSSI */
  97.                 BTIF_STORAGE_FILL_PROPERTY(&properties[num_properties],
  98.                                     BT_PROPERTY_REMOTE_RSSI, sizeof(int8_t),
  99.                                     &(p_search_data->inq_res.rssi));//保存rssi
  100.                 num_properties++;
  101.  
  102.                 status = btif_storage_add_remote_device(&bdaddr, num_properties, properties);//将各个属性保存在文件系统中
  103.  
  104. #if (defined(BLE_INCLUDED) && (BLE_INCLUDED == TRUE))
  105.                 status = btif_storage_set_remote_addr_type(&bdaddr, addr_type);
  106.                 ASSERTC(status == BT_STATUS_SUCCESS, "failed to save remote addr type (inquiry)", status);
  107. #endif
  108.                 /* Callback to notify upper layer of device */
  109.                 HAL_CBACK(bt_hal_cbacks, device_found_cb,
  110.                                  num_properties, properties);//向上汇报
  111.             }
  112.         }
  113.         break;
  114. ...

这里注意btif_storage_add_remote_device 是将各个属性保存在系统的配置文件中。然后 通过HAL_CBACK(bt_hal_cbacks, device_found_cb,num_properties, properties); 来上面五个属性：设备地址、设备名字、设备类、设备类型、设备rssi

协议栈对于ble 设备广播包的处理就分析到这里。

蓝牙inquiry流程之Advertising Report的更多相关文章

  1. 蓝牙inquiry流程之HCI_Inquiry_Result_With_RSSI和HCI Extended Inquiry Result处理

    首先介绍一下和inquiry的相关的流程. inquiry是从协议栈下发的一个HCI命令.其格式如下: 这里简单介绍下第二个参数,是inquiry的持续时间, 从上图看出 inquiry持续的时间是 ...

  2. 蓝牙inquiry流程之Inquiry Complete处理

    inquiry流程一般持续有12s多,当inquiry完成的时候,设备端会上报一个Event: Inquiry Complete 上来,那协议栈是如何把这个事件上传到应用层的呢?本篇文章来分析一下其具 ...

  3. activiti自定义流程之Spring整合activiti-modeler5.16实例（九）：历史任务查询

    注:(1)环境搭建:activiti自定义流程之Spring整合activiti-modeler5.16实例(一):环境搭建        (2)创建流程模型:activiti自定义流程之Spring ...

  4. activiti自定义流程之Spring整合activiti-modeler5.16实例（八）：完成个人任务

    注:(1)环境搭建:activiti自定义流程之Spring整合activiti-modeler5.16实例(一):环境搭建        (2)创建流程模型:activiti自定义流程之Spring ...

  5. activiti自定义流程之Spring整合activiti-modeler5.16实例（七）：任务列表展示

    注:(1)环境搭建:activiti自定义流程之Spring整合activiti-modeler5.16实例(一):环境搭建        (2)创建流程模型:activiti自定义流程之Spring ...

  6. activiti自定义流程之Spring整合activiti-modeler5.16实例（六）：启动流程

    注:(1)环境搭建:activiti自定义流程之Spring整合activiti-modeler5.16实例(一):环境搭建        (2)创建流程模型:activiti自定义流程之Spring ...

  7. activiti自定义流程之Spring整合activiti-modeler5.16实例（五）：流程定义列表

    注:(1)环境搭建:activiti自定义流程之Spring整合activiti-modeler5.16实例(一):环境搭建        (2)创建流程模型:activiti自定义流程之Spring ...

  8. activiti自定义流程之Spring整合activiti-modeler5.16实例（四）：部署流程定义

    注:(1)环境搭建:activiti自定义流程之Spring整合activiti-modeler5.16实例(一):环境搭建        (2)创建流程模型:activiti自定义流程之Spring ...

  9. activiti自定义流程之Spring整合activiti-modeler5.16实例（三）：流程模型列表展示

    注:(1)环境搭建:activiti自定义流程之Spring整合activiti-modeler5.16实例(一):环境搭建        (2)创建流程模型:activiti自定义流程之Spring ...

随机推荐

  1. LeetCode题解之Binary Number with Alternating Bits

    1.题目描述 2.问题分析 将数值转换为二进制,然后将前面的 0 去掉,再遍历一边二进制字符串,对每个字符和其后部的字符进行比较. 3.代码 bool hasAlternatingBits(int n ...

  2. md5sum 和 sha256sum用于 验证软件完整性

    md5sum 和 sha256sum 都用来用来校验软件安装包的完整性,本次我们将讲解如何使用两个命令进行软件安装包的校验: sha 是什么?        sha 为 安全散列算法(英语:Secur ...

  3. 点击一个div ,把div里的某个参数的值，传到一个input里面

    ​​​

  4. 处理AsyncTask的内存泄漏问题

    强引用AsyncTask导致了内存泄漏如下图 1.原因:activity销毁之后,AsyncTask线程可能依旧在执行,导致内存泄漏. 2.解决方法:查了一下大概有两个,一个是将函数声明为static ...

  5. tcp/ip 数据进入协议栈时的封装及分用过程图

  6. Android与js交互拍照上传资料

    应用场景:h5通知android端拍照,选相册,然后将图片路径上传成功之后,获取到网络路径,将此路径返还给h5界面,并展示出来. android与js快速交互 效果图如下:   1.在Activity ...

  7. Node.js实战(十一)之Buffer

    JavaScript 语言自身只有字符串数据类型,没有二进制数据类型. 但在处理像TCP流或文件流时,必须使用到二进制数据.因此在 Node.js中,定义了一个 Buffer 类,该类用来创建一个专门 ...

  8. Node.js实战(六)之Npm

    NPM是随同NodeJS一起安装的包管理工具,能解决NodeJS代码部署上的很多问题,常见的使用场景有以下几种: 允许用户从NPM服务器下载别人编写的第三方包到本地使用. 允许用户从NPM服务器下载并 ...

  9. vue计算属性和vue实力的属性和方法

    生命周期 <!DOCTYPE html> <html lang="en"> <head> <meta charset="UTF- ...

  10. 竟然是它：# vi /etc/resolv.conf

    有数据库主机: 前端tomcat应用连接慢,开发人员本地pl/sql连接也超慢: 检查了系统i/o ,nethogs,top,检查了数据listener.ora,awr,wait_event,sql ...