From: Johannes Berg Date: Wed, 3 Jun 2009 08:17:59 +0000 (+0200) Subject: rfkill: document /dev/rfkill X-Git-Tag: v2.6.31-rc1~14^2~234^2~9 X-Git-Url: http://ftp.safe.ca/?a=commitdiff_plain;ds=sidebyside;h=f71fea23a27ba8ec53375832aab6a80fc14622e0;p=safe%2Fjmp%2Flinux-2.6 rfkill: document /dev/rfkill Add some blurb about /dev/rfkill to the documentation and fix the "transmiter" spelling error. Signed-off-by: Johannes Berg Signed-off-by: John W. Linville --- diff --git a/Documentation/rfkill.txt b/Documentation/rfkill.txt index de941e3..1b74b5f 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.