Lines Matching refs:scan
1981 /** Set scan control flags */
2023 /* for adaptive scan mode using 3 bits (21 - 23 bits) */
2234 /* stop the scan with the corresponding scan_id */
2242 /* Cancelling specific scan */
2245 ath11k_warn(ar->ab, "invalid scan cancel param %d",
2357 "WMI chan scan list chan[%d] = %u, chan_info->info %8x\n",
3358 "failed to send spectral scan config wmi cmd\n");
3363 "WMI spectral scan config cmd vdev_id 0x%x\n",
4398 switch (ar->scan.state) {
4402 ath11k_warn(ar->ab, "received scan started event in an invalid scan state: %s (%d)\n",
4403 ath11k_scan_state_str(ar->scan.state),
4404 ar->scan.state);
4407 ar->scan.state = ATH11K_SCAN_RUNNING;
4408 complete(&ar->scan.started);
4417 switch (ar->scan.state) {
4421 ath11k_warn(ar->ab, "received scan start failed event in an invalid scan state: %s (%d)\n",
4422 ath11k_scan_state_str(ar->scan.state),
4423 ar->scan.state);
4426 complete(&ar->scan.started);
4436 switch (ar->scan.state) {
4439 /* One suspected reason scan can be completed while starting is
4440 * if firmware fails to deliver all scan events to the host,
4442 * with spectral scan phyerr events starving wmi transport
4443 * pipe. In such case the "scan completed" event should be (and
4444 * is) ignored by the host as it may be just firmware's scan
4447 ath11k_warn(ar->ab, "received scan completed event in an invalid scan state: %s (%d)\n",
4448 ath11k_scan_state_str(ar->scan.state),
4449 ar->scan.state);
4462 switch (ar->scan.state) {
4465 ath11k_warn(ar->ab, "received scan bss chan event in an invalid scan state: %s (%d)\n",
4466 ath11k_scan_state_str(ar->scan.state),
4467 ar->scan.state);
4480 switch (ar->scan.state) {
4483 ath11k_warn(ar->ab, "received scan foreign chan event in an invalid scan state: %s (%d)\n",
4484 ath11k_scan_state_str(ar->scan.state),
4485 ar->scan.state);
4552 ath11k_warn(ab, "failed to fetch scan ev");
5792 if (ar->scan.state == ATH11K_SCAN_ABORTING &&
5793 ar->scan.vdev_id == vdev_id) {
5809 ath11k_warn(ab, "failed to extract scan event");
5815 /* In case the scan was cancelled, ex. during interface teardown,
5818 * search 'ar' if the corresponding 'ar' scan is ABORTING and the
5819 * aborting scan's vdev id matches this event info.
5828 ath11k_warn(ab, "Received scan event for unknown vdev");
5836 "scan event %s type %d reason %d freq %d req_id %d scan_id %d vdev_id %d state %s (%d)\n",
5840 ath11k_scan_state_str(ar->scan.state), ar->scan.state);
5856 ath11k_warn(ab, "received scan start failure event\n");
6005 switch (ar->scan.state) {
6008 ath11k_warn(ab, "received chan info event without a scan request, ignoring\n");