Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752073AbeADC0R (ORCPT + 1 other); Wed, 3 Jan 2018 21:26:17 -0500 Received: from lucky1.263xmail.com ([211.157.147.133]:42688 "EHLO lucky1.263xmail.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751867AbeADC0O (ORCPT ); Wed, 3 Jan 2018 21:26:14 -0500 X-Greylist: delayed 431 seconds by postgrey-1.27 at vger.kernel.org; Wed, 03 Jan 2018 21:26:07 EST X-263anti-spam: KSV:0;BIG:0; X-MAIL-GRAY: 1 X-MAIL-DELIVERY: 0 X-KSVirus-check: 0 X-ADDR-CHECKED4: 1 X-ABS-CHECKED: 1 X-SKE-CHECKED: 1 X-ANTISPAM-LEVEL: 2 X-RL-SENDER: hl@rock-chips.com X-FST-TO: mka@google.com X-SENDER-IP: 103.29.142.67 X-LOGIN-NAME: hl@rock-chips.com X-UNIQUE-TAG: <887ac59628fe7bb6640a49d73119b2a6> X-ATTACHMENT-NUM: 0 X-DNS-TYPE: 0 Subject: Re: [RFC] pwm-backlight: Allow backlight to remain disabled on boot To: Thierry Reding , Jingoo Han , Bryan Wu , Lee Jones Cc: Mark Rutland , devicetree@vger.kernel.org, linux-fbdev@vger.kernel.org, Russell King , Pawel Moll , Ian Campbell , Tomi Valkeinen , linux-kernel@vger.kernel.org, Rob Herring , Kumar Gala , Eric Miao , Jean-Christophe Plagniol-Villard , linux-arm-kernel@lists.infradead.org, Brian Norris , Doug Anderson , Matthias Kaehlcke References: <1406806970-12561-1-git-send-email-thierry.reding@gmail.com> From: hl Message-ID: <6b14a283-0ded-e22c-8f81-5c241ad57463@rock-chips.com> Date: Thu, 4 Jan 2018 10:18:33 +0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 In-Reply-To: <1406806970-12561-1-git-send-email-thierry.reding@gmail.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Return-Path: Hi All,     Since many panel power sequence request backlight stay disable before panel power ready, but with now pwm-backlight drvier, it default to enable backlight when pwm-backlight probe, it mess up the panel power sequence. So we need this patch. This patch have been fly for a long time, does anyone have plan to merge it? On Thursday, July 31, 2014 07:42 PM, Thierry Reding wrote: > From: Thierry Reding > > The default for backlight devices is to be enabled immediately when > registering with the backlight core. This can be useful for setups that > use a simple framebuffer device and where the backlight cannot otherwise > be hooked up to the panel. > > However, when dealing with more complex setups, such as those of recent > ARM SoCs, this can be problematic. Since the backlight is usually setup > separately from the display controller, the probe order is not usually > deterministic. That can lead to situations where the backlight will be > powered up and the panel will show an uninitialized framebuffer. > > Furthermore, subsystems such as DRM have advanced functionality to set > the power mode of a panel. In order to allow such setups to power up the > panel at exactly the right moment, a way is needed to prevent the > backlight core from powering the backlight up automatically when it is > registered. > > This commit introduces a new boot_off field in the platform data (and > also implements getting the same information from device tree). When set > the initial backlight power mode will be set to "off". > > Signed-off-by: Thierry Reding > --- > I've been meaning to send this for a while but was always holding back > because of the indoctrination that this type of configuration shouldn't > be part of device tree. However this issue was recently raised again in > the context of power up sequences for display panels. As described above > the issue is that panel datasheets recommend that the backlight attached > to a panel be turned on at the very last step to avoid visual glitches > during the panel's power up sequence. With the current implementation it > is typical for the backlight to be probed before the display panel. That > has, in many cases, the side-effect of enabling the backlight, therefore > making the screen content visible before it's actually initialized. > > Some panels come up with random garbage when uninitialized, others show > all white. With some luck the panel will be all black and users won't > really notice. > > This patch is an attempt to enable boards to override the default of > turning on the backlight for the pwm-backlight driver. I'm not sure if > there was a specific reason to turn on the backlight by default when > this driver was initially written, but the fact is that since it has > pretty much always been like this we can't really go and change the > default, otherwise a lot of people may end up with no backlight and no > clue as to how to enable it. So the only reasonable thing we can do is > to keep the old behaviour and give new boards a way to override it if > they know that some other part of the stack will enable it at the right > moment. > > .../devicetree/bindings/video/backlight/pwm-backlight.txt | 1 + > drivers/video/backlight/pwm_bl.c | 8 ++++++++ > include/linux/pwm_backlight.h | 2 ++ > 3 files changed, 11 insertions(+) > > diff --git a/Documentation/devicetree/bindings/video/backlight/pwm-backlight.txt b/Documentation/devicetree/bindings/video/backlight/pwm-backlight.txt > index 764db86d441a..65e001a1733d 100644 > --- a/Documentation/devicetree/bindings/video/backlight/pwm-backlight.txt > +++ b/Documentation/devicetree/bindings/video/backlight/pwm-backlight.txt > @@ -17,6 +17,7 @@ Optional properties: > "pwms" property (see PWM binding[0]) > - enable-gpios: contains a single GPIO specifier for the GPIO which enables > and disables the backlight (see GPIO binding[1]) > + - backlight-boot-off: keep the backlight disabled on boot > > [0]: Documentation/devicetree/bindings/pwm/pwm.txt > [1]: Documentation/devicetree/bindings/gpio/gpio.txt > diff --git a/drivers/video/backlight/pwm_bl.c b/drivers/video/backlight/pwm_bl.c > index d7a3d13e72ec..62adfc9d37a7 100644 > --- a/drivers/video/backlight/pwm_bl.c > +++ b/drivers/video/backlight/pwm_bl.c > @@ -173,6 +173,8 @@ static int pwm_backlight_parse_dt(struct device *dev, > data->max_brightness--; > } > > + data->boot_off = of_property_read_bool(node, "backlight-boot-off"); > + > return 0; > } > > @@ -317,6 +319,12 @@ static int pwm_backlight_probe(struct platform_device *pdev) > } > > bl->props.brightness = data->dft_brightness; > + > + if (data->boot_off) > + bl->props.power = FB_BLANK_POWERDOWN; > + else > + bl->props.power = FB_BLANK_UNBLANK; > + > backlight_update_status(bl); > > platform_set_drvdata(pdev, bl); > diff --git a/include/linux/pwm_backlight.h b/include/linux/pwm_backlight.h > index efdd9227a49c..1fc14989da4a 100644 > --- a/include/linux/pwm_backlight.h > +++ b/include/linux/pwm_backlight.h > @@ -15,6 +15,8 @@ struct platform_pwm_backlight_data { > unsigned int *levels; > /* TODO remove once all users are switched to gpiod_* API */ > int enable_gpio; > + bool boot_off; > + > int (*init)(struct device *dev); > int (*notify)(struct device *dev, int brightness); > void (*notify_after)(struct device *dev, int brightness);