mirror of
https://github.com/AuxXxilium/linux_dsm_epyc7002.git
synced 2024-11-25 13:40:53 +07:00
ef0a5e80f5
In systems with multiple framebuffer devices, one of the devices might be blanked while another is unblanked. In order for the backlight blanking logic to know whether to turn off the backlight for a particular framebuffer's blanking notification, it needs to be able to check if a given framebuffer device corresponds to the backlight. This plumbs the check_fb hook from core backlight through the pwm_backlight helper to allow platform code to plug in a check_fb hook. Signed-off-by: Robert Morell <rmorell@nvidia.com> Cc: Richard Purdie <rpurdie@rpsys.net> Cc: Arun Murthy <arun.murthy@stericsson.com> Cc: Linus Walleij <linus.walleij@stericsson.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
22 lines
539 B
C
22 lines
539 B
C
/*
|
|
* Generic PWM backlight driver data - see drivers/video/backlight/pwm_bl.c
|
|
*/
|
|
#ifndef __LINUX_PWM_BACKLIGHT_H
|
|
#define __LINUX_PWM_BACKLIGHT_H
|
|
|
|
#include <linux/backlight.h>
|
|
|
|
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);
|
|
void (*exit)(struct device *dev);
|
|
int (*check_fb)(struct device *dev, struct fb_info *info);
|
|
};
|
|
|
|
#endif
|