ATH11K Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Oh <peter.oh@eero.com>
To: Sowmiya Sree Elavalagan <ssreeela@codeaurora.org>,
	ath11k@lists.infradead.org
Cc: Govindaraj Saminathan <gsamin@codeaurora.org>,
	linux-wireless@vger.kernel.org
Subject: Re: [PATCH v3] ath11k: cold boot calibration support
Date: Thu, 17 Sep 2020 12:54:51 -0700	[thread overview]
Message-ID: <b0d42c5e-8aac-cea2-bc6d-3a6341689d05@eero.com> (raw)
In-Reply-To: <1600163991-2093-1-git-send-email-ssreeela@codeaurora.org>


On 9/15/20 2:59 AM, Sowmiya Sree Elavalagan wrote:
> From: Govindaraj Saminathan <gsamin@codeaurora.org>
>
> cold boot calibration is the process to calibrate all the channels
> during the boot-up to avoid the calibration delay during the
> channel change.
> During the boot-up, firmware started with mode “cold_boot_calibration”
> Firmware calibrate all channels and generate CalDb(DDR).
> Subsequent WIFI ON will reuse the same CalDb.
Can you clarify the definition of "WIFI ON"?
> Firmware restarted with Mission mode to continue the normal operation.

Please change the mission mode to normal according to 
ATH11K_FIRMWARE_MODE_NORMAL.

Which code it sets back to normal mode from cold boot mode? I don't see it.

> +static int ath11k_qmi_process_coldboot_calibration(struct ath11k_base *ab)
> +{
> +	int timeout;
> +	int ret;
> +
> +	ret = ath11k_qmi_wlanfw_mode_send(ab, ATH11K_FIRMWARE_MODE_COLD_BOOT);
> +	if (ret < 0) {
> +		ath11k_warn(ab, "qmi failed to send wlan fw mode:%d\n", ret);
> +		return ret;
> +	}
> +
> +	ath11k_dbg(ab, ATH11K_DBG_QMI, "Coldboot calibration wait started\n");
> +
> +	timeout = wait_event_timeout(ab->qmi.cold_boot_waitq,
> +				     (ab->qmi.cal_done  == 1),
> +				     ATH11K_COLD_BOOT_FW_RESET_DELAY);
> +	if (timeout <= 0) {
> +		ath11k_warn(ab, "Coldboot Calibration timed out\n");
> +		return -ETIMEDOUT;

Does it make ath11k firmware stay in cold boot mode when timeout happens?

If so, is it worthy to have WLAN usuable due to cold boot calibration 
failure?

As I understand, initial calibration on current operation channel will 
be done regardless of cold boot calibration

> +	}
> +
> +	ath11k_dbg(ab, ATH11K_DBG_QMI, "Coldboot calibration wait ended\n");
> +
> +	return 0;
> +}
> +
>   static int
>   ath11k_qmi_driver_event_post(struct ath11k_qmi *qmi,
>   			     enum ath11k_qmi_event_type type,
> @@ -2597,9 +2643,16 @@ static void ath11k_qmi_driver_event_work(struct work_struct *work)
>   				break;
>   			}
>   
> -			ath11k_core_qmi_firmware_ready(ab);
> -			ab->qmi.cal_done = 1;
> -			set_bit(ATH11K_FLAG_REGISTERED, &ab->dev_flags);
> +			if (ath11k_cold_boot_cal && ab->qmi.cal_done == 0 &&
> +			    ab->hw_params.cold_boot_calib) {
> +				ath11k_qmi_process_coldboot_calibration(ab);
> +			} else {
> +				clear_bit(ATH11K_FLAG_CRASH_FLUSH,
> +					  &ab->dev_flags);
> +				clear_bit(ATH11K_FLAG_RECOVERY, &ab->dev_flags);
Please split this patch into a separate patch. It's not directly related 
to cold boot.
> +				ath11k_core_qmi_firmware_ready(ab);
> +				set_bit(ATH11K_FLAG_REGISTERED, &ab->dev_flags);
> +			}
>   
>   			break;
>   		case ATH11K_QMI_EVENT_COLD_BOOT_CAL_DONE:

Thanks,

Peter


-- 
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k

  parent reply	other threads:[~2020-09-17 19:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-15  9:59 [PATCH v3] ath11k: cold boot calibration support Sowmiya Sree Elavalagan
2020-09-15 19:51 ` kernel test robot
2020-09-21 13:40   ` Kalle Valo
2020-09-22  5:07     ` [kbuild-all] " Rong Chen
2020-09-22  5:54       ` Kalle Valo
2020-09-22  6:29         ` Rong Chen
2020-09-17 19:54 ` Peter Oh [this message]
2020-10-15 11:37   ` ssreeela
2020-09-21 13:42 ` Kalle Valo

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=b0d42c5e-8aac-cea2-bc6d-3a6341689d05@eero.com \
    --to=peter.oh@eero.com \
    --cc=ath11k@lists.infradead.org \
    --cc=gsamin@codeaurora.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=ssreeela@codeaurora.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox