From: Zefir Kurtisi <zefir.kurtisi@neratec.com>
To: "Luis R. Rodriguez" <rodrigue@qca.qualcomm.com>
Cc: linux-wireless@vger.kernel.org, ath9k-devel@lists.ath9k.org,
kgiori@qca.qualcomm.com, nbd@openwrt.org
Subject: Re: [RFC 2/6] ath9k: add DFS debug flag
Date: Tue, 04 Oct 2011 10:31:39 +0200 [thread overview]
Message-ID: <4E8AC46B.1010707@neratec.com> (raw)
In-Reply-To: <CAB=NE6WupXPFNOpzW6=De1XwpLdg16mv_jTjvwdaGomNJ9ktJg@mail.gmail.com>
On 10/03/2011 08:15 PM, Luis R. Rodriguez wrote:
> On Mon, Oct 3, 2011 at 3:29 AM, Zefir Kurtisi <zefir.kurtisi@neratec.com> wrote:
>>
>> Signed-off-by: Zefir Kurtisi <zefir.kurtisi@neratec.com>
>> ---
>> drivers/net/wireless/ath/ath.h | 34 ++++++++++++++++++----------------
>> 1 files changed, 18 insertions(+), 16 deletions(-)
>>
>> diff --git a/drivers/net/wireless/ath/ath.h b/drivers/net/wireless/ath/ath.h
>> index 6d56532..34d4da1 100644
>> --- a/drivers/net/wireless/ath/ath.h
>> +++ b/drivers/net/wireless/ath/ath.h
>> @@ -211,6 +211,7 @@ ath_printk(const char *level, struct ath_common *common, const char *fmt, ...);
>> * @ATH_DBG_HWTIMER: hardware timer handling
>> * @ATH_DBG_BTCOEX: bluetooth coexistance
>> * @ATH_DBG_BSTUCK: stuck beacons
>> + * @ATH_DBG_DFS: radar datection
>> * @ATH_DBG_ANY: enable all debugging
>> *
>> * The debug level is used to control the amount and type of debugging output
>> @@ -220,22 +221,23 @@ ath_printk(const char *level, struct ath_common *common, const char *fmt, ...);
>> * entry.
>> */
>> enum ATH_DEBUG {
>> - ATH_DBG_RESET = 0x00000001,
>> - ATH_DBG_QUEUE = 0x00000002,
>> - ATH_DBG_EEPROM = 0x00000004,
>> - ATH_DBG_CALIBRATE = 0x00000008,
>> - ATH_DBG_INTERRUPT = 0x00000010,
>> - ATH_DBG_REGULATORY = 0x00000020,
>> - ATH_DBG_ANI = 0x00000040,
>> - ATH_DBG_XMIT = 0x00000080,
>> - ATH_DBG_BEACON = 0x00000100,
>> - ATH_DBG_CONFIG = 0x00000200,
>> - ATH_DBG_FATAL = 0x00000400,
>> - ATH_DBG_PS = 0x00000800,
>> - ATH_DBG_HWTIMER = 0x00001000,
>> - ATH_DBG_BTCOEX = 0x00002000,
>> - ATH_DBG_WMI = 0x00004000,
>> - ATH_DBG_BSTUCK = 0x00008000,
>> + ATH_DBG_RESET = BIT(0),
>> + ATH_DBG_QUEUE = BIT(1),
>> + ATH_DBG_EEPROM = BIT(2),
>> + ATH_DBG_CALIBRATE = BIT(3),
>> + ATH_DBG_INTERRUPT = BIT(4),
>> + ATH_DBG_REGULATORY = BIT(5),
>> + ATH_DBG_ANI = BIT(6),
>> + ATH_DBG_XMIT = BIT(7),
>> + ATH_DBG_BEACON = BIT(8),
>> + ATH_DBG_CONFIG = BIT(9),
>> + ATH_DBG_FATAL = BIT(10),
>> + ATH_DBG_PS = BIT(11),
>> + ATH_DBG_HWTIMER = BIT(12),
>> + ATH_DBG_BTCOEX = BIT(13),
>> + ATH_DBG_WMI = BIT(14),
>> + ATH_DBG_BSTUCK = BIT(15),
>> + ATH_DBG_DFS = BIT(16),
>> ATH_DBG_ANY = 0xffffffff
>
> Split this into two patches, one to convert stuff to BIT(foo) and the
> other one to add ATH_DBG_DFS
In fact, the BIT values will be reverted, since it is easier to have the hex values when setting debug mask than the bit position (for me at least).
>
> Luis
Thanks,
Zefir
next prev parent reply other threads:[~2011-10-04 8:31 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-03 10:29 [RFC 0/6] ath9k: DFS pattern detection Zefir Kurtisi
2011-10-03 10:29 ` [RFC 1/6] ath9k: add DFS statistics to debugfs Zefir Kurtisi
2011-10-03 18:14 ` Luis R. Rodriguez
2011-10-04 8:27 ` Zefir Kurtisi
2011-10-03 10:29 ` [RFC 2/6] ath9k: add DFS debug flag Zefir Kurtisi
2011-10-03 18:15 ` Luis R. Rodriguez
2011-10-04 8:31 ` Zefir Kurtisi [this message]
2011-10-04 9:40 ` Mohammed Shafi
2011-10-03 10:29 ` [RFC 3/6] ath9k: initial radar pulse detection for DFS Zefir Kurtisi
2011-10-03 11:57 ` Adrian Chadd
2011-10-03 12:23 ` Zefir Kurtisi
2011-10-03 12:43 ` Adrian Chadd
2011-10-03 14:21 ` Zefir Kurtisi
2011-10-03 14:23 ` Adrian Chadd
2011-10-03 10:29 ` [RFC 4/6] ath9k: add DFS build parameter Zefir Kurtisi
2011-10-03 18:26 ` Luis R. Rodriguez
2011-10-04 9:55 ` Zefir Kurtisi
2011-10-04 10:37 ` Felix Fietkau
2011-10-04 12:25 ` Adrian Chadd
2011-10-05 22:20 ` Luis R. Rodriguez
2011-10-03 10:29 ` [RFC 5/6] ath9k: enable DFS pulse detection Zefir Kurtisi
2011-10-03 18:27 ` Luis R. Rodriguez
2011-10-03 19:24 ` Christian Lamparter
2011-10-03 19:31 ` Luis R. Rodriguez
2011-10-04 13:38 ` Christian Lamparter
2011-10-04 14:17 ` Zefir Kurtisi
2011-10-04 14:34 ` Adrian Chadd
2011-10-05 22:31 ` Luis R. Rodriguez
2011-10-04 14:42 ` Christian Lamparter
2011-10-04 14:50 ` Adrian Chadd
2011-10-04 15:26 ` Christian Lamparter
2011-10-04 15:57 ` Adrian Chadd
2011-10-04 16:42 ` Christian Lamparter
2011-10-04 17:03 ` Adrian Chadd
2011-10-04 17:49 ` Christian Lamparter
2011-10-05 22:37 ` Luis R. Rodriguez
2011-10-04 16:26 ` Zefir Kurtisi
2011-10-05 22:30 ` Luis R. Rodriguez
2011-10-05 22:27 ` [ath9k-devel] " Luis R. Rodriguez
2011-10-06 16:49 ` Christian Lamparter
2011-10-06 18:36 ` Luis R. Rodriguez
2011-10-06 18:41 ` Luis R. Rodriguez
2011-10-06 20:32 ` Zefir Kurtisi
2011-10-06 20:41 ` Luis R. Rodriguez
2011-10-06 21:08 ` Zefir Kurtisi
2011-10-06 21:12 ` Luis R. Rodriguez
2011-10-07 3:06 ` Adrian Chadd
2011-10-07 7:54 ` Luis R. Rodriguez
2011-10-07 8:48 ` Zefir Kurtisi
2011-10-07 11:43 ` Adrian Chadd
2011-10-04 10:11 ` Zefir Kurtisi
2011-10-05 22:23 ` Luis R. Rodriguez
2011-10-03 10:29 ` [RFC 6/6] ath9k: handle pulse data reported by DFS HW Zefir Kurtisi
2011-10-03 18:30 ` Luis R. Rodriguez
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=4E8AC46B.1010707@neratec.com \
--to=zefir.kurtisi@neratec.com \
--cc=ath9k-devel@lists.ath9k.org \
--cc=kgiori@qca.qualcomm.com \
--cc=linux-wireless@vger.kernel.org \
--cc=nbd@openwrt.org \
--cc=rodrigue@qca.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).