ATH10K Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Bartosz Markowski <bartosz.markowski@tieto.com>
Cc: linux-wireless@vger.kernel.org, ath10k@lists.infradead.org
Subject: Re: [PATCH 0/3] ath10k: initial per-VDEV FW statistics implementation
Date: Tue, 27 Aug 2013 09:56:31 +0300	[thread overview]
Message-ID: <87txibmxk0.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: 1377516815-12660-1-git-send-email-bartosz.markowski@tieto.com

Bartosz Markowski <bartosz.markowski@tieto.com> writes:

> FW 1.0.0.716 brings per-VDEV statistics. This patch-set implements
> debugfs mechanism to fetch those. There's still few more fileds we
> can read from the FW stats event, which are not covered here.
>
> Please note there's an ABI change in wmi_peer_stats structure, hence
> the PEER statistics will be corrupted if used with older firmware
> (e.g. 1.0.0.636)

We need to support the older firmware, so please add a feature flag VDEV
statistics so that we can detect which version of the struct needs to be
used.

Also I think you can fold patches 1 and 2.

-- 
Kalle Valo

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

  parent reply	other threads:[~2013-08-27  6:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-26 11:33 [PATCH 0/3] ath10k: initial per-VDEV FW statistics implementation Bartosz Markowski
2013-08-26 11:33 ` [PATCH 1/3] ath10k: update wmi_request_stats_cmd structure Bartosz Markowski
2013-08-26 11:33 ` [PATCH 2/3] ath10k: update wal_dbg_tx_stats structure Bartosz Markowski
2013-08-26 11:33 ` [PATCH 3/3] ath10k: implement per-VDEV FW statistics Bartosz Markowski
2013-08-27  6:56 ` Kalle Valo [this message]
2013-08-27  8:39   ` [PATCH 0/3] ath10k: initial per-VDEV FW statistics implementation Bartosz Markowski

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=87txibmxk0.fsf@kamboji.qca.qualcomm.com \
    --to=kvalo@qca.qualcomm.com \
    --cc=ath10k@lists.infradead.org \
    --cc=bartosz.markowski@tieto.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox