Messages in this thread | | | Date | Mon, 19 May 2008 17:56:33 -0500 (CDT) | From | Randy Dunlap <> | Subject | Re: [PATCH 15/15] rfkill: document rw rfkill switches and clarify input subsystem interactions |
| |
--- Original Message --- > Randy Dunlap <randy.dunlap@oracle.com> 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?
Yes. Thanks.
~Randy
| |