From: Ben Greear <greearb@candelatech.com>
To: Sujith Manoharan <c_manoha@qca.qualcomm.com>
Cc: Peter Stuge <peter@stuge.se>,
ath9k-devel@venema.h4ckr.net, linux-wireless@vger.kernel.org,
linville@tuxdriver.com
Subject: Re: [ath9k-devel] [PATCH 3/7] ath9k: Merge wiphy and misc debugfs files
Date: Tue, 14 Feb 2012 09:32:59 -0800 [thread overview]
Message-ID: <4F3A9ACB.3010009@candelatech.com> (raw)
In-Reply-To: <20282.7088.898987.229335@gargle.gargle.HOWL>
On 02/14/2012 12:30 AM, Sujith Manoharan wrote:
> Peter Stuge wrote:
>> As a compromise, you could suggest a move to a two-level compile time
>> option for debugging. You would enable only what you believe to be
> Having multiple levels of debugging makes things complex. If the general
> consensus is to keep the information, I can rework the patch.
Actually, I think it might be useful to have a second level of debugging.
I hope to soon have time & resources to add some logic to dump lots of register
info and such in human-readable format, (like, when DMA times out). That is going to be a lot
of strings added to the driver, so the compile size will definitely
increase. If keeping the size small is important, then this sort of verbose thing
could be hidden behind a second level of debugging...
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2012-02-14 17:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-13 6:20 [PATCH 3/7] ath9k: Merge wiphy and misc debugfs files Sujith Manoharan
2012-02-13 17:25 ` Ben Greear
2012-02-14 1:48 ` Sujith Manoharan
2012-02-14 1:56 ` Ben Greear
2012-02-14 2:52 ` Sujith Manoharan
2012-02-14 7:38 ` [ath9k-devel] " Peter Stuge
2012-02-14 8:30 ` Sujith Manoharan
2012-02-14 17:32 ` Ben Greear [this message]
2012-02-14 18:29 ` Sujith
2012-02-14 18:43 ` Ben Greear
2012-02-14 22:29 ` Felix Fietkau
2012-02-14 22:41 ` Ben Greear
2012-02-15 4:47 ` Sujith Manoharan
2012-02-15 8:37 ` Sujith Manoharan
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=4F3A9ACB.3010009@candelatech.com \
--to=greearb@candelatech.com \
--cc=ath9k-devel@venema.h4ckr.net \
--cc=c_manoha@qca.qualcomm.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=peter@stuge.se \
/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).