From: Johannes Berg <johannes@sipsolutions.net>
To: Vladimir Kondratiev <qca_vkondrat@qca.qualcomm.com>
Cc: "Luis R. Rodriguez" <rodrigue@qca.qualcomm.com>,
"John W . Linville" <linville@tuxdriver.com>,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH v2 1/2] wireless: Driver for 60GHz card wil6210
Date: Wed, 31 Oct 2012 16:04:36 +0100 [thread overview]
Message-ID: <1351695876.10946.1.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <1952560.nYyRnDKWFr@lx-vladimir>
On Wed, 2012-10-31 at 17:00 +0200, Vladimir Kondratiev wrote:
> you just proved reason to be CC'ed: you give valuable feedback :-)
:)
> Oh, no! Usually, you start digging into ISR registers when something stalled
> when it should not. At this point, you want to discover that, for example,
> some interrupt bit not came up. Then, you may try to manually set it writing
> into register. If you trace, it will flood dmesg, impacting performance, in
> normal situation; and will not let you analyze and recover from abnormal one.
Well I wasn't thinking printk, but rather trace events, so you can
record it to the buffer and not have the big overhead etc.
> I need "manual control" here.
Fair enough.
johannes
next prev parent reply other threads:[~2012-10-31 15:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-29 11:58 [PATCH v2 0/2] driver for 60g Wilocity chip wil6210 Vladimir Kondratiev
2012-10-29 11:58 ` [PATCH v2 1/2] wireless: Driver for 60GHz card wil6210 Vladimir Kondratiev
2012-10-31 1:23 ` Luis R. Rodriguez
2012-10-31 12:57 ` Vladimir Kondratiev
2012-10-31 13:03 ` Luis R. Rodriguez
2012-10-31 14:27 ` Johannes Berg
2012-10-31 15:00 ` Vladimir Kondratiev
2012-10-31 15:04 ` Johannes Berg [this message]
2012-10-31 15:14 ` Luis R. Rodriguez
2012-10-31 17:25 ` Christian Lamparter
2012-10-31 18:53 ` Luis R. Rodriguez
2012-10-31 14:29 ` Gábor Stefanik
2012-10-31 14:52 ` Vladimir Kondratiev
2012-10-29 11:58 ` [PATCH v2 2/2] wireless: integrate wil6210 driver into build structure Vladimir Kondratiev
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=1351695876.10946.1.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=qca_vkondrat@qca.qualcomm.com \
--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