ATH11K Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Anilkumar Kolli <akolli@codeaurora.org>
To: Kalle Valo <kvalo@codeaurora.org>
Cc: ath11k@lists.infradead.org
Subject: Re: [PATCH] ath11k: Add debugfs per chip
Date: Fri, 11 Oct 2019 10:40:01 +0530	[thread overview]
Message-ID: <5a580e62daf75a265ad327f3db927912@codeaurora.org> (raw)
In-Reply-To: <87a7a837s5.fsf@kamboji.qca.qualcomm.com>

On 2019-10-10 21:35, Kalle Valo wrote:
> Anilkumar Kolli <akolli@codeaurora.org> writes:
> 
>> Add debugfs per chip [soc/pci] under ath11k debugfs entry.
>> 
>> Example:
>> $ls -l /sys/kernel/debug/ath11k/ipq8074/
>> mac0/              mac2/              soc_ring_stats
>> mac1/              simulate_fw_crash  soc_rx_stats
>> $ls -l /sys/kernel/debug/ieee80211/phy0/
>> lrwxrwxrwx    1 root     root             0 Aug  6 17:06 ath11k ->
>> ../../ath11k/ipq8074/mac0
>> $ ls -l /sys/kernel/debug/ieee80211/phy0/ath11k/
>> dfs_block_radar_events  htt_stats               spectral_bins
>> dfs_simulate_radar      htt_stats_reset         spectral_count
>> ext_rx_stats            htt_stats_type          spectral_scan0
>> ext_tx_stats            pktlog/                 spectral_scan_ctl
>> fw_stats/               pktlog_filter
>> 
>> Signed-off-by: Anilkumar Kolli <akolli@codeaurora.org>
> 
> This didn't apply but I fixed the conflicts myself. Please double 
> check:
> 
> https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git/commit/?h=pending-ath11k&id=727f4796623292eb33ce560a3e25ba0040d17871

Thanks Kalle, This looks good.

Regards
Anil.

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

  reply	other threads:[~2019-10-11  5:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-09  7:40 [PATCH] ath11k: Add debugfs per chip Anilkumar Kolli
2019-10-10 16:05 ` Kalle Valo
2019-10-11  5:10   ` Anilkumar Kolli [this message]
2019-10-11  8:19 ` 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=5a580e62daf75a265ad327f3db927912@codeaurora.org \
    --to=akolli@codeaurora.org \
    --cc=ath11k@lists.infradead.org \
    --cc=kvalo@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox