All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Sven Eckelmann <sven.eckelmann@openmesh.com>
Cc: "ath10k@lists.infradead.org" <ath10k@lists.infradead.org>,
	Anilkumar Kolli <akolli@qti.qualcomm.com>,
	"akolli@codeaurora.org" <akolli@codeaurora.org>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"Daniel Jeang" <dyjeong@qti.qualcomm.com>,
	Yifeng Tu <yifeng@qti.qualcomm.com>
Subject: Re: [PATCHv3 1/2] ath10k: add per peer htt tx stats support for 10.4
Date: Tue, 21 Nov 2017 07:58:01 +0000	[thread overview]
Message-ID: <87tvxocbcn.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <2831996.nqnu04nqHR@bentobox> (Sven Eckelmann's message of "Fri, 17 Nov 2017 12:06:06 +0100")

Sven Eckelmann <sven.eckelmann@openmesh.com> writes:

> On Dienstag, 15. November 2016 22:07:29 CET akolli@qti.qualcomm.com wrote=
:
>> From: Anilkumar Kolli <akolli@qti.qualcomm.com>
>>=20
>> Per peer tx stats are part of 'HTT_10_4_T2H_MSG_TYPE_PEER_STATS'
>> event, Firmware sends one HTT event for every four PPDUs.
>> HTT payload has success pkts/bytes, failed pkts/bytes, retry
>> pkts/bytes and rate info per ppdu.
>> Peer stats are enabled through 'WMI_SERVICE_PEER_STATS',
>> which are nowadays enabled by default.
>>=20
>> Parse peer stats and update the tx rate information per STA.
>>=20
>> tx rate, Peer stats are tested on QCA4019 with Firmware version
>> 10.4-3.2.1-00028.
>>=20
>> Signed-off-by: Anilkumar Kolli <akolli@qti.qualcomm.com>
>
> Why is the support for 10.2.4 firmware not upstreamed? I mean the one whi=
ch is=20
> using pktlog to transfer the PEER_STATS information.

I'm not sure what you are asking. If you are asking the firmware release
mentioned in the commit log that's in ath10k-firmware:

https://github.com/kvalo/ath10k-firmware/tree/master/QCA4019/hw1.0/3.2.1

But I'm sure you know that already.

--=20
Kalle Valo=

WARNING: multiple messages have this Message-ID (diff)
From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Sven Eckelmann <sven.eckelmann@openmesh.com>
Cc: Yifeng Tu <yifeng@qti.qualcomm.com>,
	Daniel Jeang <dyjeong@qti.qualcomm.com>,
	Anilkumar Kolli <akolli@qti.qualcomm.com>,
	"akolli@codeaurora.org" <akolli@codeaurora.org>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: [PATCHv3 1/2] ath10k: add per peer htt tx stats support for 10.4
Date: Tue, 21 Nov 2017 07:58:01 +0000	[thread overview]
Message-ID: <87tvxocbcn.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <2831996.nqnu04nqHR@bentobox> (Sven Eckelmann's message of "Fri,  17 Nov 2017 12:06:06 +0100")

Sven Eckelmann <sven.eckelmann@openmesh.com> writes:

> On Dienstag, 15. November 2016 22:07:29 CET akolli@qti.qualcomm.com wrote:
>> From: Anilkumar Kolli <akolli@qti.qualcomm.com>
>> 
>> Per peer tx stats are part of 'HTT_10_4_T2H_MSG_TYPE_PEER_STATS'
>> event, Firmware sends one HTT event for every four PPDUs.
>> HTT payload has success pkts/bytes, failed pkts/bytes, retry
>> pkts/bytes and rate info per ppdu.
>> Peer stats are enabled through 'WMI_SERVICE_PEER_STATS',
>> which are nowadays enabled by default.
>> 
>> Parse peer stats and update the tx rate information per STA.
>> 
>> tx rate, Peer stats are tested on QCA4019 with Firmware version
>> 10.4-3.2.1-00028.
>> 
>> Signed-off-by: Anilkumar Kolli <akolli@qti.qualcomm.com>
>
> Why is the support for 10.2.4 firmware not upstreamed? I mean the one which is 
> using pktlog to transfer the PEER_STATS information.

I'm not sure what you are asking. If you are asking the firmware release
mentioned in the commit log that's in ath10k-firmware:

https://github.com/kvalo/ath10k-firmware/tree/master/QCA4019/hw1.0/3.2.1

But I'm sure you know that already.

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

  reply	other threads:[~2017-11-21  7:58 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-15 16:37 [PATCHv3 1/2] ath10k: add per peer htt tx stats support for 10.4 akolli
2016-11-15 16:37 ` akolli
2016-11-23 19:40 ` [PATCHv3,1/2] " Kalle Valo
2016-11-23 19:40   ` Kalle Valo
2017-05-11  8:40 ` [PATCHv3 1/2] " Sven Eckelmann
2017-05-11  8:40   ` Sven Eckelmann
2017-11-17 11:06 ` Sven Eckelmann
2017-11-17 11:06   ` Sven Eckelmann
2017-11-21  7:58   ` Kalle Valo [this message]
2017-11-21  7:58     ` Kalle Valo
2017-11-21  8:00     ` Sebastian Gottschall
2017-11-21  8:00       ` Sebastian Gottschall
2017-11-21  8:06       ` Kalle Valo
2017-11-21  8:06         ` Kalle Valo
2017-11-21  8:20       ` Sven Eckelmann
2017-11-21  8:20         ` Sven Eckelmann
2017-11-21  8:40         ` Kalle Valo
2017-11-21  8:40           ` Kalle Valo
2017-11-21  9:00           ` Sebastian Gottschall
2017-11-21  9:00             ` Sebastian Gottschall
2017-11-21  9:46             ` Sven Eckelmann
2017-11-21  9:46               ` Sven Eckelmann

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=87tvxocbcn.fsf@kamboji.qca.qualcomm.com \
    --to=kvalo@qca.qualcomm.com \
    --cc=akolli@codeaurora.org \
    --cc=akolli@qti.qualcomm.com \
    --cc=ath10k@lists.infradead.org \
    --cc=dyjeong@qti.qualcomm.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=sven.eckelmann@openmesh.com \
    --cc=yifeng@qti.qualcomm.com \
    /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.