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