From: Thierry Reding <thierry.reding@gmail.com>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] pwm-backlight: Turn off pwm backlight in probe
Date: Tue, 07 Oct 2014 08:35:49 +0000 [thread overview]
Message-ID: <20141007083548.GD24254@ulmo> (raw)
In-Reply-To: <1412623364-14583-1-git-send-email-mpa@pengutronix.de>
[-- Attachment #1: Type: text/plain, Size: 1978 bytes --]
On Mon, Oct 06, 2014 at 09:22:44PM +0200, Markus Pargmann wrote:
> The backlight will be enabled by the panel again if it is used. So we
> can save the default brightness and disable the pwm backlight when
> probing.
>
> Signed-off-by: Markus Pargmann <mpa@pengutronix.de>
> ---
> drivers/video/backlight/pwm_bl.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/video/backlight/pwm_bl.c b/drivers/video/backlight/pwm_bl.c
> index 336b83be7e2d..b4f433a6f106 100644
> --- a/drivers/video/backlight/pwm_bl.c
> +++ b/drivers/video/backlight/pwm_bl.c
> @@ -317,9 +317,11 @@ static int pwm_backlight_probe(struct platform_device *pdev)
> data->dft_brightness = data->max_brightness;
> }
>
> - bl->props.brightness = data->dft_brightness;
> + bl->props.brightness = 0;
> backlight_update_status(bl);
>
> + bl->props.brightness = data->dft_brightness;
> +
> platform_set_drvdata(pdev, bl);
> return 0;
>
It would be nice if it was that easy. But we can't do this, because it
will regress for users of this driver that don't use a panel or DRM. If
the PWM backlight driver is used for example in conjunction with a plain
fbdev driver it isn't necessarily hooked up with anything and won't be
enabled automatically. That's really bad if fbdev is the only output you
have since you'd have to blindly type the commands to enable the
backlight. Furthermore disabling backlight isn't always what you want to
do. For example if the bootloader already turned it on and you hand over
from bootloader to kernel in a seamless way, then you absolutely want to
keep backlight on all the time.
See also[0] for a different proposal to solve the same problem. Back at
the time that received only a very few replies, but it would be nice if
Lee and Bryan could look at it again and see if we can come up with some
way to deal with this situation.
Thierry
[0]: https://lkml.org/lkml/2014/7/31/259
[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-10-07 8:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-06 19:22 [PATCH] pwm-backlight: Turn off pwm backlight in probe Markus Pargmann
2014-10-07 8:35 ` Thierry Reding [this message]
2014-10-07 9:06 ` Lee Jones
2014-10-07 9:07 ` Markus Pargmann
2014-10-07 9:29 ` Ajay kumar
2014-10-08 9:55 ` Markus Pargmann
2014-10-08 9:44 ` Jingoo Han
2014-10-08 12:13 ` Thierry Reding
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=20141007083548.GD24254@ulmo \
--to=thierry.reding@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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).