| commit | 3a643d244f09fa1fdd25d48a56a073c1a69583ee | |
| author | Ivo van Doorn <ivdoorn@gmail.com> | |
| Tue, 25 Mar 2008 13:13:18 +0000 (25 14:13 +0100) | ||
| committer | John W. Linville <linville@tuxdriver.com> | |
| Tue, 25 Mar 2008 20:42:00 +0000 (25 16:42 -0400) | ||
| tree | 3cd8423f72f37d66fdd2738409f72779da3911fc | treesnapshot (tar.gz zip) |
| parent | 866a05038481d77cac6fc0186250b4c44e691b42 | commitdiff |
rt2x00: Fix in_atomic() usage
rt73usb and rt2500usb used in_atomic to determine
if a configuration step should be rescheduled or not.
Since in_atomic() is not a valid method to determine
if sleeping is allowed we should fix the way this is handled
by adding a new flag to rt2x00.
In addition mark LED class support for the drivers broken
since that also uses the broken in_atomic() method but
so far no solution exists to have LED triggers work only
in scheduled context.
Signed-off-by: Ivo van Doorn <IvDoorn@gmail.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
rt73usb and rt2500usb used in_atomic to determine
if a configuration step should be rescheduled or not.
Since in_atomic() is not a valid method to determine
if sleeping is allowed we should fix the way this is handled
by adding a new flag to rt2x00.
In addition mark LED class support for the drivers broken
since that also uses the broken in_atomic() method but
so far no solution exists to have LED triggers work only
in scheduled context.
Signed-off-by: Ivo van Doorn <IvDoorn@gmail.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>