From: Kalle Valo <kvalo@codeaurora.org>
To: Maharaja Kennadyrajan <mkenna@codeaurora.org>
Cc: ath11k@lists.infradead.org, linux-wireless@vger.kernel.org,
Maharaja Kennadyrajan <mkenna@codeaurora.org>
Subject: Re: [PATCH] ath11k: add pktlog checksum in trace events to support pktlog
Date: Mon, 6 Apr 2020 16:18:33 +0000 (UTC) [thread overview]
Message-ID: <20200406161833.D4BBCC433BA@smtp.codeaurora.org> (raw)
In-Reply-To: <1585234155-30574-1-git-send-email-mkenna@codeaurora.org>
Maharaja Kennadyrajan <mkenna@codeaurora.org> wrote:
> Pktlog data are different among the chipset & chipset versions.
> As part of enhancing the user space script to decode the pktlog
> trace events generated, it is desirable to know which chipset or
> which chipset version has provided the events and thereby decode
> the pktlogs appropriately.
>
> Pktlog checksum helps to determine the chipset variant which is
> given by the firmware in the struct wmi_ready_event.
>
> Pktlog checksums are computed during the firmware build.
> So, adding that pktlog checksum in the pklog trace events.
>
> Signed-off-by: Maharaja Kennadyrajan <mkenna@codeaurora.org>
> Signed-off-by: Kalle Valo <kvalo@codeaurora.org>
Patch applied to ath-next branch of ath.git, thanks.
21c1b063f4b9 ath11k: add pktlog checksum in trace events to support pktlog
--
https://patchwork.kernel.org/patch/11460287/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2020-04-06 16:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-26 14:49 [PATCH] ath11k: add pktlog checksum in trace events to support pktlog Maharaja Kennadyrajan
2020-03-26 14:49 ` Maharaja Kennadyrajan
2020-03-26 16:44 ` Kalle Valo
2020-03-26 16:44 ` Kalle Valo
2020-03-27 4:32 ` Maharaja Kennadyrajan
2020-03-27 4:32 ` Maharaja Kennadyrajan
2020-04-06 16:18 ` Kalle Valo
2020-04-06 16:18 ` Kalle Valo [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-03-26 14:47 Maharaja Kennadyrajan
2020-03-26 14:47 ` Maharaja Kennadyrajan
2020-03-26 14:47 ` Maharaja Kennadyrajan
2020-03-26 14:47 ` Maharaja Kennadyrajan
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=20200406161833.D4BBCC433BA@smtp.codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=ath11k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mkenna@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.