intel-gfx.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: jani.nikula@intel.com, jesse.barnes@intel.com
Subject: [PATCH 0/7] drm/i915: per connector backlight, per chip vfuncs
Date: Thu, 31 Oct 2013 18:55:47 +0200	[thread overview]
Message-ID: <cover.1383237868.git.jani.nikula@intel.com> (raw)

Hi all -

I was going to pick up [1], rebase, add a few small things on top. I
forget what those small things were going to be, but I ended up with
per-connector backlight handling and chip specific backlight hooks. Oh
well.

This is still completely untested. I tried to be careful with each
change, but given that this is backlight, there's bound to be some
regression lurking in there. Keep your eyes open, you've been warned. ;)


BR,
Jani.


[1] http://mid.gmane.org/1381773821-16875-1-git-send-email-jbarnes@virtuousgeek.org

Jani Nikula (5):
  drm/i915: move opregion asle request handling to a work queue
  drm/i915: clean up backlight conditional build
  drm/i915: make backlight info per-connector
  drm/i915: handle backlight through chip specific functions
  drm/i915: make asle notifications update backlight on all connectors

Jesse Barnes (2):
  drm/i915: make backlight functions take a connector
  drm/i915/vlv: use per-pipe backlight controls v2

 drivers/gpu/drm/i915/i915_dma.c       |    2 +-
 drivers/gpu/drm/i915/i915_drv.h       |   21 +-
 drivers/gpu/drm/i915/i915_reg.h       |   15 +
 drivers/gpu/drm/i915/i915_suspend.c   |   37 +-
 drivers/gpu/drm/i915/intel_display.c  |   23 +-
 drivers/gpu/drm/i915/intel_dp.c       |    5 +-
 drivers/gpu/drm/i915/intel_drv.h      |   19 +-
 drivers/gpu/drm/i915/intel_lvds.c     |    9 +-
 drivers/gpu/drm/i915/intel_opregion.c |   39 ++-
 drivers/gpu/drm/i915/intel_panel.c    |  613 +++++++++++++++++++++++----------
 10 files changed, 562 insertions(+), 221 deletions(-)

-- 
1.7.10.4

             reply	other threads:[~2013-10-31 16:59 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-31 16:55 Jani Nikula [this message]
2013-10-31 16:55 ` [PATCH 1/7] drm/i915: move opregion asle request handling to a work queue Jani Nikula
2013-11-05 17:50   ` Jesse Barnes
2013-11-06 17:07   ` Joe Konno
2013-10-31 16:55 ` [PATCH 2/7] drm/i915: make backlight functions take a connector Jani Nikula
2013-11-06 17:08   ` Joe Konno
2013-10-31 16:55 ` [PATCH 3/7] drm/i915/vlv: use per-pipe backlight controls v2 Jani Nikula
2013-11-06 17:09   ` Joe Konno
2013-10-31 16:55 ` [PATCH 4/7] drm/i915: clean up backlight conditional build Jani Nikula
2013-11-06 17:11   ` Joe Konno
2013-10-31 16:55 ` [PATCH 5/7] drm/i915: make backlight info per-connector Jani Nikula
2013-11-06 17:12   ` Joe Konno
2013-10-31 16:55 ` [PATCH 6/7] drm/i915: handle backlight through chip specific functions Jani Nikula
2013-11-06 17:12   ` Joe Konno
2013-10-31 16:55 ` [PATCH 7/7] drm/i915: make asle notifications update backlight on all connectors Jani Nikula
2013-11-06 17:12   ` Joe Konno
2013-10-31 21:34 ` [PATCH 0/7] drm/i915: per connector backlight, per chip vfuncs Joe Konno
2013-11-01 13:28   ` Jani Nikula
2013-11-01 14:30     ` Joe Konno

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=cover.1383237868.git.jani.nikula@intel.com \
    --to=jani.nikula@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jesse.barnes@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;
as well as URLs for NNTP newsgroup(s).