Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: jani.nikula@intel.com
Subject: [PATCH 0/5] drm/i915: backlight locking, cleanup
Date: Tue,  2 Apr 2013 15:48:08 +0300	[thread overview]
Message-ID: <cover.1364906645.git.jani.nikula@intel.com> (raw)

I think these should DTRT, but with backlight and BIOS you never seem to
know...

BR,
Jani.

Jani Nikula (5):
  drm/i915: group backlight related stuff into a struct
  drm/i915: protect backlight enable and level with spinlock
  drm/i915: don't pretend we support ASLE ALS, PFIT, or PFMB
  drm/i915/opregion: don't pretend we did something when we didn't
  drm/i915: drop code duplication in favor of asle interrupt handler

 drivers/gpu/drm/i915/i915_drv.h       |   13 ++++---
 drivers/gpu/drm/i915/i915_irq.c       |    4 +--
 drivers/gpu/drm/i915/intel_opregion.c |   60 ++++-----------------------------
 drivers/gpu/drm/i915/intel_panel.c    |   60 +++++++++++++++++++++------------
 4 files changed, 55 insertions(+), 82 deletions(-)

-- 
1.7.9.5

             reply	other threads:[~2013-04-02 12:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-02 12:48 Jani Nikula [this message]
2013-04-02 12:48 ` [PATCH 1/5] drm/i915: group backlight related stuff into a struct Jani Nikula
2013-04-02 13:49   ` Daniel Vetter
2013-04-02 12:48 ` [PATCH 2/5] drm/i915: protect backlight enable and level with spinlock Jani Nikula
2013-04-02 13:39   ` Daniel Vetter
2013-04-02 12:48 ` [PATCH 3/5] drm/i915: don't pretend we support ASLE ALS, PFIT, or PFMB Jani Nikula
2013-04-02 12:48 ` [PATCH 4/5] drm/i915/opregion: don't pretend we did something when we didn't Jani Nikula
2013-04-02 12:48 ` [PATCH 5/5] drm/i915: drop code duplication in favor of asle interrupt handler Jani Nikula

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.1364906645.git.jani.nikula@intel.com \
    --to=jani.nikula@intel.com \
    --cc=intel-gfx@lists.freedesktop.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