On Mon, Mar 09, 2020 at 06:56:00PM +0530, Kiran Gunda wrote:
Add cabc_config, sync_toggle, wled_ovp_fault_status and wled_ovp_delay callback functions to prepare the driver for adding WLED5 support.
Signed-off-by: Kiran Gunda kgunda@codeaurora.org
Overall this code would a lot easier to review if
drivers/video/backlight/qcom-wled.c | 196 +++++++++++++++++++++++------------- 1 file changed, 126 insertions(+), 70 deletions(-)
diff --git a/drivers/video/backlight/qcom-wled.c b/drivers/video/backlight/qcom-wled.c index 3d276b3..b73f273 100644 --- a/drivers/video/backlight/qcom-wled.c +++ b/drivers/video/backlight/qcom-wled.c @@ -128,6 +128,7 @@ struct wled_config { bool cs_out_en; bool ext_gen; bool cabc;
- bool en_cabc;
Does this ever get set to true?
bool external_pfet; bool auto_detection_enabled; }; @@ -147,14 +148,20 @@ struct wled { u32 max_brightness; u32 short_count; u32 auto_detect_count;
u32 version; bool disabled_by_short; bool has_short_detect;
bool cabc_disabled; int short_irq; int ovp_irq;
struct wled_config cfg; struct delayed_work ovp_work; int (*wled_set_brightness)(struct wled *wled, u16 brightness);
int (*cabc_config)(struct wled *wled, bool enable);
int (*wled_sync_toggle)(struct wled *wled);
int (*wled_ovp_fault_status)(struct wled *wled, bool *fault_set);
int (*wled_ovp_delay)(struct wled *wled);
Let's get some doc comments explaining what these callbacks do (and which versions they apply to).
cabc_config() in particular appears to have a very odd interface for wled4. It looks like it relies on being initially called with enable set a particular way and prevents itself from acting again. Therefore if the comment you end up writing doesn't sound "right" then please also fix the API!
Finally, why is everything except cabc_config() prefixed with wled?
Daniel.