From: Clint Taylor <clinton.a.taylor@intel.com>
To: Jani Nikula <jani.nikula@intel.com>, intel-gfx@lists.freedesktop.org
Cc: rodrigo.vivi@intel.com, kevin.strasser@intel.com, jesse.barnes@intel.com
Subject: Re: [PATCH 0/4] drm/i915: backlight sysfs bl_power and brightness == 0
Date: Wed, 13 Aug 2014 18:11:39 -0700 [thread overview]
Message-ID: <53EC0CCB.2030305@intel.com> (raw)
In-Reply-To: <cover.1407849872.git.jani.nikula@intel.com>
On 08/12/2014 07:11 AM, Jani Nikula wrote:
> This series adds support for backlight class sysfs bl_power attribute
> for eDP panels, which allows switching the backlight on/off. This is
> done using the eDP panel power control as a sub-state of everything else
> being enabled. Patch 4 also makes 0 brightness switch off the eDP
> backlight using the same mechanism. This is all eDP specific, with no
> support for LVDS.
>
> I'm not particularly fond of these patches, but there appears to be
> demand for them, particularly since
>
> commit 6dda730e55f412a6dfb181cae6784822ba463847
> Author: Jani Nikula <jani.nikula@intel.com>
> Date: Tue Jun 24 18:27:40 2014 +0300
>
> drm/i915: respect the VBT minimum backlight brightness
>
> All the discussions seem to just drag on and on without code to speak
> about, so here goes. I've tried to make this as simple and unintrusive
> as possible.
>
> BR,
> Jani.
>
I have hand merged the first 3 patches of this series into kernel 3.10
Chromium and the bl_power sysfs entry is functional and turns off
backlight power independent of the PWM as designed.
The fourth patch is non-functional due to the difference between the 11
Chromium backlight patches from April 2014 and current upstream
implementation.
Clint
>
> Jani Nikula (4):
> drm/i915/dp: split up panel power control from backlight pwm control
> drm/i915: add some framework for backlight bl_power support
> drm/i915/dp: make backlight bl_power control power sequencer backlight
> drm/i915: switch off backlight for backlight class 0 brightness
>
> drivers/gpu/drm/i915/intel_dp.c | 61 ++++++++++++++++++++++++++++++--------
> drivers/gpu/drm/i915/intel_drv.h | 2 ++
> drivers/gpu/drm/i915/intel_panel.c | 27 +++++++++++++++++
> 3 files changed, 77 insertions(+), 13 deletions(-)
>
prev parent reply other threads:[~2014-08-14 1:13 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
2014-08-14 1:11 ` Clint Taylor [this message]
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=53EC0CCB.2030305@intel.com \
--to=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