From: Sven Eckelmann <sven@narfation.org>
To: Anilkumar Kolli <akolli@codeaurora.org>
Cc: ath10k@lists.infradead.org, linux-wireless@vger.kernel.org,
Sathishkumar Muruganandam <murugana@codeaurora.org>
Subject: Re: [PATCH 2/2] ath10k: add debugfs support to configure fwtest parameters
Date: Mon, 05 Mar 2018 08:42:53 +0100 [thread overview]
Message-ID: <1974303.3lPsqGCgIZ@bentobox> (raw)
In-Reply-To: <1520233148-26050-3-git-send-email-akolli@codeaurora.org>
[-- Attachment #1: Type: text/plain, Size: 503 bytes --]
On Montag, 5. März 2018 12:29:08 CET Anilkumar Kolli wrote:
> @@ -496,6 +497,8 @@ struct ath10k_debug {
> u32 reg_addr;
> u32 nf_cal_period;
> void *cal_data;
> + u32 fw_test_param_id;
> + u32 fw_test_param_value;
> };
Why is it necessary to have these two values in ath10k_debug? They seem to be
used only in the context of ath10k_write_fw_test().
Where can we find the documentation of the possible param_id and param_values?
Kind regards,
Sven
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Sven Eckelmann <sven@narfation.org>
To: Anilkumar Kolli <akolli@codeaurora.org>
Cc: Sathishkumar Muruganandam <murugana@codeaurora.org>,
linux-wireless@vger.kernel.org, ath10k@lists.infradead.org
Subject: Re: [PATCH 2/2] ath10k: add debugfs support to configure fwtest parameters
Date: Mon, 05 Mar 2018 08:42:53 +0100 [thread overview]
Message-ID: <1974303.3lPsqGCgIZ@bentobox> (raw)
In-Reply-To: <1520233148-26050-3-git-send-email-akolli@codeaurora.org>
[-- Attachment #1.1: Type: text/plain, Size: 503 bytes --]
On Montag, 5. März 2018 12:29:08 CET Anilkumar Kolli wrote:
> @@ -496,6 +497,8 @@ struct ath10k_debug {
> u32 reg_addr;
> u32 nf_cal_period;
> void *cal_data;
> + u32 fw_test_param_id;
> + u32 fw_test_param_value;
> };
Why is it necessary to have these two values in ath10k_debug? They seem to be
used only in the context of ath10k_write_fw_test().
Where can we find the documentation of the possible param_id and param_values?
Kind regards,
Sven
[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 146 bytes --]
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2018-03-05 7:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-05 6:59 [PATCH 0/2] FWTEST command support in debugfs Anilkumar Kolli
2018-03-05 6:59 ` Anilkumar Kolli
2018-03-05 6:59 ` [PATCH 1/2] ath10k: Add WMI FWTEST command support Anilkumar Kolli
2018-03-05 6:59 ` Anilkumar Kolli
2018-03-05 18:48 ` Peter Oh
2018-03-05 18:48 ` Peter Oh
2018-03-05 19:31 ` Sebastian Gottschall
2018-03-05 19:31 ` Sebastian Gottschall
2018-03-05 6:59 ` [PATCH 2/2] ath10k: add debugfs support to configure fwtest parameters Anilkumar Kolli
2018-03-05 6:59 ` Anilkumar Kolli
2018-03-05 7:42 ` Sven Eckelmann [this message]
2018-03-05 7:42 ` Sven Eckelmann
2018-03-05 10:46 ` akolli
2018-03-05 10:46 ` akolli
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=1974303.3lPsqGCgIZ@bentobox \
--to=sven@narfation.org \
--cc=akolli@codeaurora.org \
--cc=ath10k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=murugana@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 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.