From: "Aditya Kumar Singh (QUIC)" <quic_adisi@quicinc.com> To: Kalle Valo <kvalo@kernel.org> Cc: "ath11k@lists.infradead.org" <ath11k@lists.infradead.org>, "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>, "Aditya Kumar Singh (QUIC)" <quic_adisi@quicinc.com> Subject: RE: [PATCH 1/2] ath11k: move firmware stats out of debugfs Date: Fri, 3 Jun 2022 08:30:23 +0000 [thread overview] Message-ID: <DM5PR0201MB35890931A39B89FB8E1A94FC84A19@DM5PR0201MB3589.namprd02.prod.outlook.com> (raw) In-Reply-To: <165423896462.24941.15580147276579618500.kvalo@kernel.org> > -----Original Message----- > From: Kalle Valo <kvalo@kernel.org> > Sent: Friday, June 3, 2022 12:21 > To: Aditya Kumar Singh (QUIC) <quic_adisi@quicinc.com> > Cc: ath11k@lists.infradead.org; linux-wireless@vger.kernel.org; Aditya > Kumar Singh (QUIC) <quic_adisi@quicinc.com> > Subject: Re: [PATCH 1/2] ath11k: move firmware stats out of debugfs > > Aditya Kumar Singh <quic_adisi@quicinc.com> wrote: > > > Currently, firmware stats, comprising pdev, vdev and beacon stats are > > part of debugfs. In firmware pdev stats, firmware reports the final Tx > > power used to transmit each packet. If driver wants to know the final > > Tx power being used at firmware level, it can leverage from firmware > > pdev stats. > > > > Move firmware stats out of debugfs context in order to leverage the > > final Tx power reported in it even when debugfs is disabled. > > > > Tested-on: IPQ8074 hw2.0 AHB > > WLAN.HK.2.5.0.1-01100-QCAHKSWPL_SILICONZ-1 > > Tested-on: QCN9074 hw1.0 PCI > > WLAN.HK.2.5.0.1-01100-QCAHKSWPL_SILICONZ-1 > > Tested-on: WCN6855 hw2.0 PCI > > WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3 > > > > Signed-off-by: Aditya Kumar Singh <quic_adisi@quicinc.com> > > Signed-off-by: Kalle Valo <quic_kvalo@quicinc.com> > > This added new warnings: > > drivers/net/wireless/ath/ath11k/debugfs.c:94: Please don't use multiple > blank lines > drivers/net/wireless/ath/ath11k/debugfs.c:976: Blank lines aren't necessary > before a close brace '}' > I have sent [v2] before your mail. But that too will lead to these warnings hence I have rectified and sent [v3]. > I fixed them in the pending branch. Sure thanks. > > -- > https://patchwork.kernel.org/project/linux- > wireless/patch/20220602051425.9265-2-quic_adisi@quicinc.com/ > > https://wireless.wiki.kernel.org/en/developers/documentation/submittingp > atches
WARNING: multiple messages have this Message-ID (diff)
From: "Aditya Kumar Singh (QUIC)" <quic_adisi@quicinc.com> To: Kalle Valo <kvalo@kernel.org> Cc: "ath11k@lists.infradead.org" <ath11k@lists.infradead.org>, "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>, "Aditya Kumar Singh (QUIC)" <quic_adisi@quicinc.com> Subject: RE: [PATCH 1/2] ath11k: move firmware stats out of debugfs Date: Fri, 3 Jun 2022 08:30:23 +0000 [thread overview] Message-ID: <DM5PR0201MB35890931A39B89FB8E1A94FC84A19@DM5PR0201MB3589.namprd02.prod.outlook.com> (raw) In-Reply-To: <165423896462.24941.15580147276579618500.kvalo@kernel.org> > -----Original Message----- > From: Kalle Valo <kvalo@kernel.org> > Sent: Friday, June 3, 2022 12:21 > To: Aditya Kumar Singh (QUIC) <quic_adisi@quicinc.com> > Cc: ath11k@lists.infradead.org; linux-wireless@vger.kernel.org; Aditya > Kumar Singh (QUIC) <quic_adisi@quicinc.com> > Subject: Re: [PATCH 1/2] ath11k: move firmware stats out of debugfs > > Aditya Kumar Singh <quic_adisi@quicinc.com> wrote: > > > Currently, firmware stats, comprising pdev, vdev and beacon stats are > > part of debugfs. In firmware pdev stats, firmware reports the final Tx > > power used to transmit each packet. If driver wants to know the final > > Tx power being used at firmware level, it can leverage from firmware > > pdev stats. > > > > Move firmware stats out of debugfs context in order to leverage the > > final Tx power reported in it even when debugfs is disabled. > > > > Tested-on: IPQ8074 hw2.0 AHB > > WLAN.HK.2.5.0.1-01100-QCAHKSWPL_SILICONZ-1 > > Tested-on: QCN9074 hw1.0 PCI > > WLAN.HK.2.5.0.1-01100-QCAHKSWPL_SILICONZ-1 > > Tested-on: WCN6855 hw2.0 PCI > > WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3 > > > > Signed-off-by: Aditya Kumar Singh <quic_adisi@quicinc.com> > > Signed-off-by: Kalle Valo <quic_kvalo@quicinc.com> > > This added new warnings: > > drivers/net/wireless/ath/ath11k/debugfs.c:94: Please don't use multiple > blank lines > drivers/net/wireless/ath/ath11k/debugfs.c:976: Blank lines aren't necessary > before a close brace '}' > I have sent [v2] before your mail. But that too will lead to these warnings hence I have rectified and sent [v3]. > I fixed them in the pending branch. Sure thanks. > > -- > https://patchwork.kernel.org/project/linux- > wireless/patch/20220602051425.9265-2-quic_adisi@quicinc.com/ > > https://wireless.wiki.kernel.org/en/developers/documentation/submittingp > atches -- ath11k mailing list ath11k@lists.infradead.org http://lists.infradead.org/mailman/listinfo/ath11k
next prev parent reply other threads:[~2022-06-03 8:30 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-06-02 5:14 [PATCH 0/2] ath11k: add support for get_txpower mac ops Aditya Kumar Singh 2022-06-02 5:14 ` Aditya Kumar Singh 2022-06-02 5:14 ` [PATCH 1/2] ath11k: move firmware stats out of debugfs Aditya Kumar Singh 2022-06-02 5:14 ` Aditya Kumar Singh 2022-06-02 14:33 ` Jeff Johnson 2022-06-02 14:33 ` Jeff Johnson 2022-06-03 4:23 ` Aditya Kumar Singh (QUIC) 2022-06-03 4:23 ` Aditya Kumar Singh (QUIC) 2022-06-03 10:37 ` Kalle Valo 2022-06-03 10:37 ` Kalle Valo 2022-06-03 6:50 ` Kalle Valo 2022-06-03 6:50 ` Kalle Valo 2022-06-03 8:30 ` Aditya Kumar Singh (QUIC) [this message] 2022-06-03 8:30 ` Aditya Kumar Singh (QUIC) 2022-06-02 5:14 ` [PATCH 2/2] ath11k: add get_txpower mac ops Aditya Kumar Singh 2022-06-02 5:14 ` Aditya Kumar Singh 2022-06-02 14:51 ` Jeff Johnson 2022-06-02 14:51 ` Jeff Johnson 2022-06-03 4:41 ` Aditya Kumar Singh (QUIC) 2022-06-03 4:41 ` Aditya Kumar Singh (QUIC)
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=DM5PR0201MB35890931A39B89FB8E1A94FC84A19@DM5PR0201MB3589.namprd02.prod.outlook.com \ --to=quic_adisi@quicinc.com \ --cc=ath11k@lists.infradead.org \ --cc=kvalo@kernel.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: linkBe 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.