public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
* [PATCH] rfkill: document /dev/rfkill
@ 2009-06-03  8:17 Johannes Berg
  0 siblings, 0 replies; only message in thread
From: Johannes Berg @ 2009-06-03  8:17 UTC (permalink / raw)
  To: John Linville; +Cc: linux-wireless, Jiri Kosina

Add some blurb about /dev/rfkill to the documentation and
fix the "transmiter" spelling error.

Signed-off-by: Johannes Berg <johannes@sipsolutions.net>
---
 Documentation/rfkill.txt |    8 +++++++-
 1 file changed, 7 insertions(+), 1 deletion(-)

--- wireless-testing.orig/Documentation/rfkill.txt	2009-06-03 10:14:56.000000000 +0200
+++ wireless-testing/Documentation/rfkill.txt	2009-06-03 10:16:41.000000000 +0200
@@ -113,7 +113,7 @@ The following sysfs entries exist for ev
 		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.



^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2009-06-03  8:18 UTC | newest]

Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-06-03  8:17 [PATCH] rfkill: document /dev/rfkill Johannes Berg

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox