Rev 5056 | Go to most recent revision | Details | Compare with Previous | Last modification | View Log | RSS feed
| Rev | Author | Line No. | Line |
|---|---|---|---|
| 3120 | serge | 1 | /* |
| 2 | * Backlight Lowlevel Control Abstraction |
||
| 3 | * |
||
| 4 | * Copyright (C) 2003,2004 Hewlett-Packard Company |
||
| 5 | * |
||
| 6 | */ |
||
| 7 | |||
| 8 | #ifndef _LINUX_BACKLIGHT_H |
||
| 9 | #define _LINUX_BACKLIGHT_H |
||
| 6336 | serge | 10 | |
| 11 | #include |
||
| 12 | #include |
||
| 13 | #include |
||
| 5056 | serge | 14 | /* Notes on locking: |
| 15 | * |
||
| 16 | * backlight_device->ops_lock is an internal backlight lock protecting the |
||
| 17 | * ops pointer and no code outside the core should need to touch it. |
||
| 18 | * |
||
| 19 | * Access to update_status() is serialised by the update_lock mutex since |
||
| 20 | * most drivers seem to need this and historically get it wrong. |
||
| 21 | * |
||
| 22 | * Most drivers don't need locking on their get_brightness() method. |
||
| 23 | * If yours does, you need to implement it in the driver. You can use the |
||
| 24 | * update_lock mutex if appropriate. |
||
| 25 | * |
||
| 26 | * Any other use of the locks below is probably wrong. |
||
| 27 | */ |
||
| 28 | |||
| 29 | enum backlight_update_reason { |
||
| 30 | BACKLIGHT_UPDATE_HOTKEY, |
||
| 31 | BACKLIGHT_UPDATE_SYSFS, |
||
| 32 | }; |
||
| 33 | |||
| 34 | enum backlight_type { |
||
| 35 | BACKLIGHT_RAW = 1, |
||
| 36 | BACKLIGHT_PLATFORM, |
||
| 37 | BACKLIGHT_FIRMWARE, |
||
| 38 | BACKLIGHT_TYPE_MAX, |
||
| 39 | }; |
||
| 40 | |||
| 41 | enum backlight_notification { |
||
| 42 | BACKLIGHT_REGISTERED, |
||
| 43 | BACKLIGHT_UNREGISTERED, |
||
| 44 | }; |
||
| 45 | |||
| 3120 | serge | 46 | #endif |