From: Daniel Vetter <daniel@ffwll.ch>
To: Clint Taylor <clinton.a.taylor@intel.com>
Cc: Jani Nikula <jani.nikula@intel.com>,
intel-gfx@lists.freedesktop.org, kevin.strasser@intel.com,
jesse.barnes@intel.com, rodrigo.vivi@intel.com
Subject: Re: [PATCH 4/4] drm/i915: switch off backlight for backlight class 0 brightness
Date: Mon, 25 Aug 2014 23:24:55 +0200 [thread overview]
Message-ID: <20140825212455.GR15520@phenom.ffwll.local> (raw)
In-Reply-To: <53F3D812.1050800@intel.com>
On Tue, Aug 19, 2014 at 04:04:50PM -0700, Clint Taylor wrote:
> On 08/12/2014 07:11 AM, Jani Nikula wrote:
> >Make backlight class sysfs brightness 0 value switch off the backlight
> >for connectors that have the backlight_power callback defined. For eDP,
> >this has the similar caveats regarding power savings as bl_power as only
> >the power sequencer backlight control is switched off.
> >
> >Signed-off-by: Jani Nikula <jani.nikula@intel.com>
> >---
> > drivers/gpu/drm/i915/intel_panel.c | 3 ++-
> > 1 file changed, 2 insertions(+), 1 deletion(-)
> >
> >diff --git a/drivers/gpu/drm/i915/intel_panel.c b/drivers/gpu/drm/i915/intel_panel.c
> >index c365f2a57c75..574690afadb3 100644
> >--- a/drivers/gpu/drm/i915/intel_panel.c
> >+++ b/drivers/gpu/drm/i915/intel_panel.c
> >@@ -986,7 +986,8 @@ static int intel_backlight_device_update_status(struct backlight_device *bd)
> > */
> > if (panel->backlight.enabled) {
> > if (panel->backlight_power) {
> >- bool enable = bd->props.power == FB_BLANK_UNBLANK;
> >+ bool enable = bd->props.power == FB_BLANK_UNBLANK &&
> >+ bd->props.brightness != 0;
> > panel->backlight_power(connector, enable);
> > }
> > } else {
> >
> Didn't get a chance to test this on nightly.
>
> Reviewed_by: Clinton Taylor <Clinton.A.Taylor@intel.com>
All 4 patches merged, thanks.
Aside: I really liked that your review here didn't just amount to an r-b
tag, but had some comments and questions - that gives my a nice warm&fuzzy
feeling that a real review has actually been done and not just some patch
rubber stamping.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
next prev parent reply other threads:[~2014-08-25 21:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-12 14:11 [PATCH 0/4] drm/i915: backlight sysfs bl_power and brightness == 0 Jani Nikula
2014-08-12 14:11 ` [PATCH 1/4] drm/i915/dp: split up panel power control from backlight pwm control Jani Nikula
2014-08-18 17:15 ` Clint Taylor
2014-08-19 23:02 ` Clint Taylor
2014-08-12 14:11 ` [PATCH 2/4] drm/i915: add some framework for backlight bl_power support Jani Nikula
2014-08-13 9:10 ` [PATCH v2 " Jani Nikula
2014-08-19 23:04 ` Clint Taylor
2014-08-12 14:11 ` [PATCH 3/4] drm/i915/dp: make backlight bl_power control power sequencer backlight Jani Nikula
2014-08-18 17:44 ` Clint Taylor
2014-08-19 5:36 ` Jani Nikula
2014-08-19 23:03 ` Clint Taylor
2014-08-12 14:11 ` [PATCH 4/4] drm/i915: switch off backlight for backlight class 0 brightness Jani Nikula
2014-08-19 23:04 ` Clint Taylor
2014-08-25 21:24 ` Daniel Vetter [this message]
2014-08-14 1:11 ` [PATCH 0/4] drm/i915: backlight sysfs bl_power and brightness == 0 Clint Taylor
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=20140825212455.GR15520@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=clinton.a.taylor@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=jesse.barnes@intel.com \
--cc=kevin.strasser@intel.com \
--cc=rodrigo.vivi@intel.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