[lkml]   [2008]   [May]   [19]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH 15/15] rfkill: document rw rfkill switches and clarify input subsystem interactions
Randy Dunlap <> wrote:
> On Sun, 18 May 2008 15:48:05 -0300 Henrique de Moraes Holschuh wrote:
>> +===============================================================================
>> +3: Kernel API
>> +
>> +To build a driver with rfkill subsystem support, the driver should depend on
>> +the Kconfig symbol RFKILL; it should _not_ depend on RKFILL_INPUT.
>> +
>> +The hardware the driver talks to may be write-only (where the current state
>> +of the hardware is unknown), or read-write (where the hardware can be queried
>> +about its current state).
>> +
>> +The rfkill class will call the get_state hook of a device every time it needs
>> +to know the *real* current state of the hardware. This can happen often.
>> +
>> +Some hardware provide events when its status change. In these cases, it is
> provides

Wouldn't that be "changes" as welll?



 \ /
  Last update: 2008-05-20 00:55    [W:0.092 / U:1.884 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site