From 4c1fa5235555c9ef3de1eebd006c4e91283362bf Mon Sep 17 00:00:00 2001 From: Jesse Barnes Date: Tue, 4 Dec 2007 18:27:24 -0800 Subject: Add BCM_ to backlight control method enums Avoids polluting the global namespace with such generic terms. --- src/i830.h | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) (limited to 'src/i830.h') diff --git a/src/i830.h b/src/i830.h index 2c1ac86b..fe4d6c5c 100644 --- a/src/i830.h +++ b/src/i830.h @@ -321,29 +321,29 @@ enum last_3d { * so they can choose an ideal one for their platform (assuming our quirk * code picks the wrong one). * - * Four different methods are available: - * NATIVE: only ever touch the native backlight control registers + * Four different backlight control methods are available: + * BCM_NATIVE: only ever touch the native backlight control registers * This method may be susceptible to problem (2) above if the firmware * modifies the legacy registers. - * LEGACY: only ever touch the legacy backlight control registers + * BCM_LEGACY: only ever touch the legacy backlight control registers * This method may be susceptible to problem (1) above if the firmware * also modifies the legacy registers. - * COMBO: try to use both sets + * BCM_COMBO: try to use both sets * In this case, the driver will try to modify both sets of registers * if needed. To avoid problem (2) above it may set the LBB register * to a non-zero value if the brightness is to be increased. It's still * susceptible to problem (1), but to a lesser extent than the LEGACY only * method. - * KERNEL: use kernel methods for controlling the backlight + * BCM_KERNEL: use kernel methods for controlling the backlight * This is only available on some platforms, but where present this can * provide the best user experience. */ enum backlight_control { - NATIVE = 0, - LEGACY, - COMBO, - KERNEL, + BCM_NATIVE = 0, + BCM_LEGACY, + BCM_COMBO, + BCM_KERNEL, }; typedef struct _I830Rec { -- cgit v1.2.3