linux.git/Documentation/rfkill.txt, branch v4.4

rfkill: document rfkill module parameters

2015-01-09T22:22:12+00:00

Document the rfkill module parameters default_state and
master_switch_mode.

Signed-off-by: Andrew Clausen 
[rewrite commit message]
Signed-off-by: Johannes Berg

doc: spelling error changes

2014-05-05T13:32:05+00:00

Fixed multiple spelling errors.

Acked-by: Randy Dunlap 
Signed-off-by: Carlos E. Garcia 
Signed-off-by: Jiri Kosina

doc: fix some typos in documentations

2013-12-02T13:45:19+00:00

Fix some typos in five documentations, no functional change.

Signed-off-by: Xishi Qiu 
Acked-by: Rob Landley 
Signed-off-by: Jiri Kosina

doc: fix broken references

2011-09-27T16:08:04+00:00

There are numerous broken references to Documentation files (in other
Documentation files, in comments, etc.). These broken references are
caused by typo's in the references, and by renames or removals of the
Documentation files. Some broken references are simply odd.

Fix these broken references, sometimes by dropping the irrelevant text
they were part of.

Signed-off-by: Paul Bolle 
Signed-off-by: Jiri Kosina

Document the rfkill sysfs ABI

2010-03-10T22:09:33+00:00

This moves sysfs ABI info from Documentation/rfkill.txt to the
ABI subfolder and reformats it.

This also schedules the deprecated sysfs parts to be removed in
2012 (claim file) and 2014 (state file).

Signed-off-by: Florian Mickler 
Signed-off-by: John W. Linville

rfkill: export persistent attribute in sysfs

2009-06-19T15:50:18+00:00

This information allows userspace to implement a hybrid policy where
it can store the rfkill soft-blocked state in platform non-volatile
storage if available, and if not then file-based storage can be used.

Some users prefer platform non-volatile storage because of the behaviour
when dual-booting multiple versions of Linux, or if the rfkill setting
is changed in the BIOS setting screens, or if the BIOS responds to
wireless-toggle hotkeys itself before the relevant platform driver has
been loaded.

Signed-off-by: Alan Jenkins 
Acked-by: Henrique de Moraes Holschuh 
Signed-off-by: John W. Linville

rfkill: improve docs

2009-06-15T19:05:58+00:00

Now that the dust has settled a bit, improve the docs on rfkill
and include more information about /dev/rfkill.

Signed-off-by: Johannes Berg 
Signed-off-by: John W. Linville

rfkill: document /dev/rfkill

2009-06-03T18:06:15+00:00

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

rfkill: rewrite

2009-06-03T18:06:13+00:00

This patch completely rewrites the rfkill core to address
the following deficiencies:

 * all rfkill drivers need to implement polling where necessary
   rather than having one central implementation

 * updating the rfkill state cannot be done from arbitrary
   contexts, forcing drivers to use schedule_work and requiring
   lots of code

 * rfkill drivers need to keep track of soft/hard blocked
   internally -- the core should do this

 * the rfkill API has many unexpected quirks, for example being
   asymmetric wrt. alloc/free and register/unregister

 * rfkill can call back into a driver from within a function the
   driver called -- this is prone to deadlocks and generally
   should be avoided

 * rfkill-input pointlessly is a separate module

 * drivers need to #ifdef rfkill functions (unless they want to
   depend on or select RFKILL) -- rfkill should provide inlines
   that do nothing if it isn't compiled in

 * the rfkill structure is not opaque -- drivers need to initialise
   it correctly (lots of sanity checking code required) -- instead
   force drivers to pass the right variables to rfkill_alloc()

 * the documentation is hard to read because it always assumes the
   reader is completely clueless and contains way TOO MANY CAPS

 * the rfkill code needlessly uses a lot of locks and atomic
   operations in locked sections

 * fix LED trigger to actually change the LED when the radio state
   changes -- this wasn't done before

Tested-by: Alan Jenkins 
Signed-off-by: Henrique de Moraes Holschuh  [thinkpad]
Signed-off-by: Johannes Berg 
Signed-off-by: John W. Linville

rfkill: remove user_claim stuff

2009-04-22T20:54:27+00:00

Almost all drivers do not support user_claim, so remove it
completely and always report -EOPNOTSUPP to userspace. Since
userspace cannot really drive rfkill _anyway_ (due to the
odd restrictions imposed by the documentation) having this
code is just pointless.

Signed-off-by: Johannes Berg 
Signed-off-by: John W. Linville