diff options
| author | Johannes Berg <johannes@sipsolutions.net> | 2009-06-03 10:17:59 +0200 |
|---|---|---|
| committer | John W. Linville <linville@tuxdriver.com> | 2009-06-03 14:06:15 -0400 |
| commit | f71fea23a27ba8ec53375832aab6a80fc14622e0 (patch) | |
| tree | 277692f96525aa4eae979fb4c97c83b2ea2eef9e | |
| parent | 2ec2c68c11af95075f29e370970eb97c89234e2e (diff) | |
rfkill: document /dev/rfkill
Add some blurb about /dev/rfkill to the documentation and
fix the "transmiter" spelling error.
Signed-off-by: Johannes Berg <johannes@sipsolutions.net>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
| -rw-r--r-- | Documentation/rfkill.txt | 8 |
1 files changed, 7 insertions, 1 deletions
diff --git a/Documentation/rfkill.txt b/Documentation/rfkill.txt index de941e309d4..1b74b5f30af 100644 --- a/Documentation/rfkill.txt +++ b/Documentation/rfkill.txt @@ -113,7 +113,7 @@ The following sysfs entries exist for every rfkill device: 0: RFKILL_STATE_SOFT_BLOCKED transmitter is turned off by software 1: RFKILL_STATE_UNBLOCKED - transmiter is (potentially) active + transmitter is (potentially) active 2: RFKILL_STATE_HARD_BLOCKED transmitter is forced off by something outside of the driver's control. @@ -128,3 +128,9 @@ RFKILL_TYPE The contents of these variables corresponds to the "name", "state" and "type" sysfs files explained above. + +An alternative userspace interface exists as a misc device /dev/rfkill, +which allows userspace to obtain and set the state of rfkill devices and +sets of devices. It also notifies userspace about device addition and +removal. The API is a simple read/write API that is defined in +linux/rfkill.h. |