From: Mike Dunn <mikedunn@newsguy.com>
To: thierry.reding@gmail.com
Cc: Mike Dunn <mikedunn@newsguy.com>,
Richard Purdie <rpurdie@rpsys.net>,
Jingoo Han <jg1.han@samsung.com>,
Jean-Christophe Plagniol-Villard <plagnioj@jcrosoft.com>,
Tomi Valkeinen <tomi.valkeinen@ti.com>,
Grant Likely <grant.likely@linaro.org>,
Rob Herring <rob.herring@calxeda.com>,
linux-pwm@vger.kernel.org, linux-fbdev@vger.kernel.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
Robert Jarzmik <robert.jarzmik@free.fr>,
Marek Vasut <marex@denx.de>
Subject: [PATCH] pwm-backlight: allow for non-increasing brightness levels
Date: Thu, 12 Sep 2013 18:35:52 +0000 [thread overview]
Message-ID: <1379010952-8928-1-git-send-email-mikedunn@newsguy.com> (raw)
Currently the driver assumes that the values specified in the brightness-levels
device tree property increase as they are parsed from left to right. But boards
that invert the signal between the PWM output and the backlight will need to
specify decreasing brightness-levels. This patch removes the assumption that
the last element of the array is the max value, and instead searches the array
for the max value and uses that as the normalizing value when determining the
duty cycle.
Signed-off-by: Mike Dunn <mikedunn@newsguy.com>
---
drivers/video/backlight/pwm_bl.c | 13 +++++++++++--
1 file changed, 11 insertions(+), 2 deletions(-)
diff --git a/drivers/video/backlight/pwm_bl.c b/drivers/video/backlight/pwm_bl.c
index 1fea627..d66aaa0 100644
--- a/drivers/video/backlight/pwm_bl.c
+++ b/drivers/video/backlight/pwm_bl.c
@@ -27,6 +27,7 @@ struct pwm_bl_data {
unsigned int period;
unsigned int lth_brightness;
unsigned int *levels;
+ unsigned int max_level;
int (*notify)(struct device *,
int brightness);
void (*notify_after)(struct device *,
@@ -57,7 +58,7 @@ static int pwm_backlight_update_status(struct backlight_device *bl)
if (pb->levels) {
duty_cycle = pb->levels[brightness];
- max = pb->levels[max];
+ max = pb->levels[pb->max_level];
} else {
duty_cycle = brightness;
}
@@ -195,7 +196,15 @@ static int pwm_backlight_probe(struct platform_device *pdev)
}
if (data->levels) {
- max = data->levels[data->max_brightness];
+ int i, max_value = 0, max_idx = 0;
+ for (i = 0; i <= data->max_brightness; i++) {
+ if (data->levels[i] > max_value) {
+ max_value = data->levels[i];
+ max_idx = i;
+ }
+ }
+ pb->max_level = max_idx;
+ max = data->levels[max_idx];
pb->levels = data->levels;
} else
max = data->max_brightness;
--
1.8.1.5
next reply other threads:[~2013-09-12 18:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-12 18:35 Mike Dunn [this message]
[not found] ` <1379010952-8928-1-git-send-email-mikedunn-kFrNdAxtuftBDgjK7y7TUQ@public.gmane.org>
2013-09-17 9:36 ` [PATCH] pwm-backlight: allow for non-increasing brightness levels Sascha Hauer
[not found] ` <20130917093622.GB30088-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2013-09-17 14:23 ` Mike Dunn
2013-09-19 11:56 ` Thierry Reding
2013-09-19 16:13 ` Mike Dunn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1379010952-8928-1-git-send-email-mikedunn@newsguy.com \
--to=mikedunn@newsguy.com \
--cc=devicetree@vger.kernel.org \
--cc=grant.likely@linaro.org \
--cc=jg1.han@samsung.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=marex@denx.de \
--cc=plagnioj@jcrosoft.com \
--cc=rob.herring@calxeda.com \
--cc=robert.jarzmik@free.fr \
--cc=rpurdie@rpsys.net \
--cc=thierry.reding@gmail.com \
--cc=tomi.valkeinen@ti.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).