aboutsummaryrefslogtreecommitdiffstats
path: root/include/linux/pwm_backlight.h
diff options
context:
space:
mode:
authorArun Murthy <arun.murthy@stericsson.com>2010-11-11 14:05:28 -0800
committerLinus Torvalds <torvalds@linux-foundation.org>2010-11-12 07:55:33 -0800
commitfef7764f8bca9d603a8a51dcb522db97739a33c2 (patch)
treecd3a3d97e729cf814c924e3dd5bd81aca6a3ace4 /include/linux/pwm_backlight.h
parenta1025e224c518dceb342d0cc54e5513c6476f60c (diff)
downloadkernel_samsung_crespo-fef7764f8bca9d603a8a51dcb522db97739a33c2.zip
kernel_samsung_crespo-fef7764f8bca9d603a8a51dcb522db97739a33c2.tar.gz
kernel_samsung_crespo-fef7764f8bca9d603a8a51dcb522db97739a33c2.tar.bz2
backlight: add low threshold to pwm backlight
The intensity of the backlight can be varied from a range of max_brightness to zero. Though most, if not all the pwm based backlight devices start flickering at lower brightness value. And also for each device there exists a brightness value below which the backlight appears to be turned off though the value is not equal to zero. If the range of brightness for a device is from zero to max_brightness. A graph is plotted for brightness Vs intensity for the pwm based backlight device has to be a linear graph. intensity | / | / | / |/ --------- 0 max_brightness But pratically on measuring the above we note that the intensity of backlight goes to zero(OFF) when the value in not zero almost nearing to zero(some x%). so the graph looks like intensity | / | / | / | | ------------ 0 x max_brightness In order to overcome this drawback knowing this x% i.e nothing but the low threshold beyond which the backlight is off and will have no effect, the brightness value is being offset by the low threshold value(retaining the linearity of the graph). Now the graph becomes intensity | / | / | / | / ------------- 0 max_brightness With this for each and every digit increment in the brightness from zero there is a change in the intensity of backlight. Devices having this behaviour can set the low threshold brightness(lth_brightness) and pass the same as platform data else can have it as zero. [akpm@linux-foundation.org: coding-style fixes] Signed-off-by: Arun Murthy <arun.murthy@stericsson.com> Acked-by: Linus Walleij <linus.walleij@stericsson.com> Acked-by: Richard Purdie <rpurdie@linux.intel.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'include/linux/pwm_backlight.h')
-rw-r--r--include/linux/pwm_backlight.h1
1 files changed, 1 insertions, 0 deletions
diff --git a/include/linux/pwm_backlight.h b/include/linux/pwm_backlight.h
index 01b3d75..e031e1a 100644
--- a/include/linux/pwm_backlight.h
+++ b/include/linux/pwm_backlight.h
@@ -8,6 +8,7 @@ struct platform_pwm_backlight_data {
int pwm_id;
unsigned int max_brightness;
unsigned int dft_brightness;
+ unsigned int lth_brightness;
unsigned int pwm_period_ns;
int (*init)(struct device *dev);
int (*notify)(struct device *dev, int brightness);