All of lore.kernel.org
 help / color / mirror / Atom feed
From: Maharaja Kennadyrajan <mkenna@codeaurora.org>
To: Joshua Zhao <swzhao@gmail.com>
Cc: linux-wireless@vger.kernel.org, ath10k@lists.infradead.org
Subject: Re: [PATCH v2] ath10k: debugfs support to get final TPC stats for 10.4 variants
Date: Tue, 27 Feb 2018 11:03:25 +0530	[thread overview]
Message-ID: <c3d2bae3da74abf969072eb7ce001a07@codeaurora.org> (raw)
In-Reply-To: <CAKmTU=ptKUweW-WgoJiZRPS=6X+8q60XX2nHQwsqf=A1j-18iQ@mail.gmail.com>

On 2018-02-27 1:19 am, Joshua Zhao wrote:
> as you said:
>         The existing tpc_stats debugfs file provides the dump which is
> minimum of target power and regulatory domain.
>                         cat 
> /sys/kernel/debug/ieee80211/phyX/ath10k/tpc_stats
> 
> I’m curious what’s exact difference w/ this new addition:
>         Export the final Transmit Power Control (TPC) value, which is
> the minimum of control power and existing TPC value to user space via
> a new debugfs file "tpc_stats_final" to help with debugging.
> 
> Can you clarify or give examples on the difference?
> 
> Thanks!

The existing tpc_stats is the minimum of "target power and regulatory 
domain".
The new addition is the minimum of "existing tpc_stats and control 
power" which means minimum of "control power, target power and 
regulatory domain".

-- 
Regards,
Maha

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

WARNING: multiple messages have this Message-ID (diff)
From: Maharaja Kennadyrajan <mkenna@codeaurora.org>
To: Joshua Zhao <swzhao@gmail.com>
Cc: ath10k@lists.infradead.org, linux-wireless@vger.kernel.org
Subject: Re: [PATCH v2] ath10k: debugfs support to get final TPC stats for 10.4 variants
Date: Tue, 27 Feb 2018 11:03:25 +0530	[thread overview]
Message-ID: <c3d2bae3da74abf969072eb7ce001a07@codeaurora.org> (raw)
In-Reply-To: <CAKmTU=ptKUweW-WgoJiZRPS=6X+8q60XX2nHQwsqf=A1j-18iQ@mail.gmail.com>

On 2018-02-27 1:19 am, Joshua Zhao wrote:
> as you said:
>         The existing tpc_stats debugfs file provides the dump which is
> minimum of target power and regulatory domain.
>                         cat 
> /sys/kernel/debug/ieee80211/phyX/ath10k/tpc_stats
> 
> I’m curious what’s exact difference w/ this new addition:
>         Export the final Transmit Power Control (TPC) value, which is
> the minimum of control power and existing TPC value to user space via
> a new debugfs file "tpc_stats_final" to help with debugging.
> 
> Can you clarify or give examples on the difference?
> 
> Thanks!

The existing tpc_stats is the minimum of "target power and regulatory 
domain".
The new addition is the minimum of "existing tpc_stats and control 
power" which means minimum of "control power, target power and 
regulatory domain".

-- 
Regards,
Maha

  reply	other threads:[~2018-02-27  5:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-26  8:40 [PATCH v2] ath10k: debugfs support to get final TPC stats for 10.4 variants mkenna
2018-02-26  8:40 ` mkenna
2018-02-26 19:49 ` Joshua Zhao
2018-02-26 19:49   ` Joshua Zhao
2018-02-27  5:33   ` Maharaja Kennadyrajan [this message]
2018-02-27  5:33     ` Maharaja Kennadyrajan
2018-03-27  6:24     ` Joshua Zhao
2018-03-27  6:24       ` Joshua Zhao
2018-03-26 15:09 ` [v2] " Kalle Valo
2018-03-26 15:09 ` Kalle Valo

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=c3d2bae3da74abf969072eb7ce001a07@codeaurora.org \
    --to=mkenna@codeaurora.org \
    --cc=ath10k@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=swzhao@gmail.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.