[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <1390543476-13499-1-git-send-email-Ying.Liu@freescale.com>
Date: Fri, 24 Jan 2014 14:04:34 +0800
From: Liu Ying <Ying.Liu@...escale.com>
To: <jg1.han@...sung.com>
CC: <plagnioj@...osoft.com>, <tomi.valkeinen@...com>,
<linux-fbdev@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
<dri-devel@...ts.freedesktop.org>, <jani.nikula@...ux.intel.com>
Subject: [PATCH v4 0/2] backlight: update bl status and some bd properties when necessary
We don't have to turn backlight on/off every time a blanking
or unblanking event comes because the backlight status may
have already been what we want. Another thought is that one
backlight device may be shared by multiple framebuffers. We
don't hope blanking one of the framebuffers may turn the
backlight off for all the other framebuffers, since they are
likely being active to display something. This patch set adds
some logics to record each framebuffer's backlight usage to
determine the backlight device use count and whether the
backlight status should be updated or not.
Liu Ying (2):
backlight: update bd state & fb_blank properties when necessary
backlight: update backlight status when necessary
v3->v4:
* Split v3 into 2 patches to separate the change for updating the
backlight device properties and backlight status, according to
the comments from Jani Nikula and Jingoo Han.
v2->v3:
* Set fb_blank(*(int *)evdata->data) to bd->props.fb_blank
when we turn off a blacklight.
* Correct some trivial typos in the commit message.
v1->v2:
* Make the commit message be more specific about the condition
in which backlight device use count can be increased/decreased.
* Correct the setting for bd->props.fb_blank.
drivers/video/backlight/backlight.c | 28 +++++++++++++++++++++-------
include/linux/backlight.h | 6 ++++++
2 files changed, 27 insertions(+), 7 deletions(-)
--
1.7.9.5
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists