From: Ivo van Doorn <ivdoorn@gmail.com>
To: rt2400-devel@lists.sourceforge.net
Cc: linux-wireless@vger.kernel.org
Subject: rt2x00: LED classes
Date: Fri, 21 Mar 2008 21:46:33 +0100 [thread overview]
Message-ID: <200803212146.34141.IvDoorn@gmail.com> (raw)
Hi,
Some time ago I introduced LED classes to rt2x00.
For the USB drivers this has prooven to be tricky
since LED triggers are called in non-sleepable context
and USB drivers do need some sleep for register access.
As a workaround I introduced the in_atomic() check
which prints an error and skips the call. I am now
reading a discussion about in_atomic() on the netdev
mailinglist, and drivers are urged to remove the
usage as much as possible.
I must admit that I don't know if LED triggers work
in non-sleepable context by design or if it depends
on the calling trigger....
For rt2x00 there are now 2 options, either find the
trigger that is calling rt2x00 in non-sleepable context
and fix it or drop the LED class feature for USB drivers.
Has anybody recently tested the LED class option with
rt2500usb or rt73usb? And if so, do the following lines
appear in the log:
Ignoring LED brightness command for led
If so, please post all those error messages so the problem
can be tracked down.
Otherwise I will start with either disabling LED handling
completely or create a large workaround which still uses
LED classes but works without LED triggers.
Depending on the amount of code, the LED triggers for PCI
drivers will also be sacrificed to keep the code as simple
as possible.
Ivo
next reply other threads:[~2008-03-21 20:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-21 20:46 Ivo van Doorn [this message]
2008-03-24 16:20 ` rt2x00: LED classes Ivo van Doorn
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=200803212146.34141.IvDoorn@gmail.com \
--to=ivdoorn@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=rt2400-devel@lists.sourceforge.net \
/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).