From: Kalle Valo <kvalo@codeaurora.org>
To: Govind Singh <govinds@codeaurora.org>
Cc: ath10k@lists.infradead.org, linux-wireless@vger.kernel.org,
Govind Singh <govinds@codeaurora.org>
Subject: Re: [PATCH] ath10k: Add WMI diag fw logging support for WCN3990
Date: Tue, 25 Jun 2019 13:17:47 +0000 (UTC) [thread overview]
Message-ID: <20190625131748.6913260E5F@smtp.codeaurora.org> (raw)
In-Reply-To: <20190401132202.29626-1-govinds@codeaurora.org>
Govind Singh <govinds@codeaurora.org> wrote:
> Integrated WiFi chipset ex:WCN399x supports fw logging
> using WMI copy engine and shared mem DIAG based fw logging.
> By default shared mem DIAG based fw logging is enabled.
> To support WMI copy engine based fw logging add QMI
> control message to enable WMI copy engine based fw logging.
>
> Enable WMI based fw logging using fw_diag_log module parameter.
>
> insmod ath10k_core.ko fw_diag_log=1
>
> DIAG utility(https://github.com/andersson/diag) implements extraction
> of diagnostics related messages between application processor and
> various subsystems while shared mem DIAG based fw logging is enabled.
>
> Testing: Tested on WCN3990/QCA6174 HW
> Tested FW: WLAN.HL.3.1-00959-QCAHLSWMTPLZ-1
>
> Signed-off-by: Govind Singh <govinds@codeaurora.org>
> Signed-off-by: Kalle Valo <kvalo@codeaurora.org>
Patch applied to ath-next branch of ath.git, thanks.
d9e47698965d ath10k: Add WMI diag fw logging support for WCN3990
--
https://patchwork.kernel.org/patch/10879943/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
prev parent reply other threads:[~2019-06-25 13:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-01 13:22 [PATCH] ath10k: Add WMI diag fw logging support for WCN3990 Govind Singh
2019-04-01 13:22 ` Govind Singh
2019-06-25 13:17 ` Kalle Valo
2019-06-25 13:17 ` Kalle Valo [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=20190625131748.6913260E5F@smtp.codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=ath10k@lists.infradead.org \
--cc=govinds@codeaurora.org \
--cc=linux-wireless@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.