ATH10K Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Manikanta Pubbisetty <mpubbise@codeaurora.org>
To: ath10k@lists.infradead.org
Subject: Re: [PATCH] ath11k:print firmware info during boot
Date: Tue, 07 May 2019 15:17:00 +0530	[thread overview]
Message-ID: <3b0b9bd0cf348b7aa30bb6d42b834021@codeaurora.org> (raw)
In-Reply-To: <1557222253-22745-1-git-send-email-mpubbise@codeaurora.org>

On 2019-05-07 15:14, Manikanta Pubbisetty wrote:
> Print fw info like version, time stamp and fw build info
> during boot.
> 
> Signed-off-by: Manikanta Pubbisetty <mpubbise@codeaurora.org>
> ---
>  drivers/net/wireless/ath/ath11k/qmi.c | 20 ++++++++++++++++----
>  drivers/net/wireless/ath/ath11k/qmi.h |  1 +
>  2 files changed, 17 insertions(+), 4 deletions(-)
> 
> diff --git a/drivers/net/wireless/ath/ath11k/qmi.c
> b/drivers/net/wireless/ath/ath11k/qmi.c
> index aca717c..f1b272d 100644
> --- a/drivers/net/wireless/ath/ath11k/qmi.c
> +++ b/drivers/net/wireless/ath/ath11k/qmi.c
> @@ -1774,14 +1774,26 @@ static int
> ath11k_qmi_request_target_cap(struct ath11k_base *ab)
>  	if (resp.soc_info_valid)
>  		ab->qmi.target.soc_id = resp.soc_info.soc_id;
> 
> -	if (resp.fw_version_info_valid)
> +	if (resp.fw_version_info_valid) {
>  		ab->qmi.target.fw_version = resp.fw_version_info.fw_version;
> +		strlcpy(ab->qmi.target.fw_build_timestamp,
> +			resp.fw_version_info.fw_build_timestamp,
> +			sizeof(ab->qmi.target.fw_build_timestamp));
> +	}
> +
> +	if (resp.fw_build_id_valid)
> +		strlcpy(ab->qmi.target.fw_build_id, resp.fw_build_id,
> +			sizeof(ab->qmi.target.fw_build_id));
> 
>  	ath11k_info(ab, "qmi target: chip_id: 0x%x, chip_family: 0x%x,"
> -			"board_id: 0x%x, soc_id: 0x%x, fw_version: 0x%x\n",
> +			"board_id: 0x%x, soc_id: 0x%x\n",
>  		    ab->qmi.target.chip_id, ab->qmi.target.chip_family,
> -		    ab->qmi.target.board_id, ab->qmi.target.soc_id,
> -		    ab->qmi.target.fw_version);
> +		    ab->qmi.target.board_id, ab->qmi.target.soc_id);
> +
> +	ath11k_info(ab, "qmi fw_version: 0x%x fw_build_timestamp: %s 
> fw_build_id: %s",
> +		    ab->qmi.target.fw_version,
> +		    ab->qmi.target.fw_build_timestamp,
> +		    ab->qmi.target.fw_build_id);
> 
>  out:
>  	return ret;
> diff --git a/drivers/net/wireless/ath/ath11k/qmi.h
> b/drivers/net/wireless/ath/ath11k/qmi.h
> index b017596..1781236 100644
> --- a/drivers/net/wireless/ath/ath11k/qmi.h
> +++ b/drivers/net/wireless/ath/ath11k/qmi.h
> @@ -98,6 +98,7 @@ struct target_info {
>  	u32 soc_id;
>  	u32 fw_version;
>  	char fw_build_timestamp[ATH11K_QMI_WLANFW_MAX_TIMESTAMP_LEN_V01 + 1];
> +	char fw_build_id[ATH11K_QMI_WLANFW_MAX_BUILD_ID_LEN_V01 + 1];
>  };
> 
>  struct ath11k_qmi {


Send to wrong mailing list, please ignore the patch.

Thanks,
Manikanta

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

      reply	other threads:[~2019-05-07  9:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-07  9:44 [PATCH] ath11k:print firmware info during boot Manikanta Pubbisetty
2019-05-07  9:47 ` Manikanta Pubbisetty [this message]

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=3b0b9bd0cf348b7aa30bb6d42b834021@codeaurora.org \
    --to=mpubbise@codeaurora.org \
    --cc=ath10k@lists.infradead.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