diff options
| author | merge <null@invalid> | 2009-01-16 11:23:28 +0000 |
|---|---|---|
| committer | Andy Green <agreen@pads.home.warmcat.com> | 2009-01-16 11:23:28 +0000 |
| commit | 4ff379a06a70e17997e196c9c393bc7c8648e42a (patch) | |
| tree | d1b0ef0ecc612e860fe59bedf0f33bd06eae409b /include/linux/quotaops.h | |
| parent | 6fde2330ccdf7a6817b664702c4c5e4c7e61a054 (diff) | |
MERGE-via-pending-tracking-hist-MERGE-via-stable-tracking-rfkill-support-for-the-ar6000-1232104308
pending-tracking-hist top was MERGE-via-stable-tracking-rfkill-support-for-the-ar6000-1232104308 / 09faeb511e9e6872c79b4d1ea2f3b5fefc16f3a1 ... parent commitmessage:
From: merge <null@invalid>
MERGE-via-stable-tracking-hist-rfkill-support-for-the-ar6000-
stable-tracking-hist top was rfkill-support-for-the-ar6000- / e82f8ffa04ebcb05506c8e22268371c3c3b03173 ... parent commitmessage:
From: Werner Almesberger <werner@openmoko.org>
rfkill support for the AR6000 driver
This patch adds rfkill support to the AR6000 driver. The driver does
not directly implement an rfkill device but uses the help of a special
platform device, such that the latter can retain rfkill state when the
AR6k driver is removed (e.g., because of suspend).
If an attempt is made to bring the driver up (module load, bind, or
resume) while rfkill is blocking, only the driver's data structures
are initialized, but function activation and most of the rest of the
setup is deferred until the rfkill block is removed.
Signed-off-by: Werner Almesberger <werner@openmoko.org>
Diffstat (limited to 'include/linux/quotaops.h')
0 files changed, 0 insertions, 0 deletions