All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: Len Brown <lenb@kernel.org>, Zhao Yakui <yakui.zhao@intel.com>,
	Yves-Alexis Perez <corsac@debian.org>,
	"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>
Subject: Re: [intel/acpi] backlight
Date: Mon, 1 Dec 2008 19:32:15 +0000	[thread overview]
Message-ID: <20081201193215.GA23773@srcf.ucam.org> (raw)
In-Reply-To: <200812011127.09720.jbarnes@virtuousgeek.org>

On Mon, Dec 01, 2008 at 11:27:09AM -0800, Jesse Barnes wrote:
> On Monday, December 1, 2008 12:38 am Matthew Garrett wrote:
> > Jesse, are IRQs being delivered to the drm code when X isn't the
> > foreground VT? If not, this would seem to need fixing.
> 
> The X driver calls into the DRM to disable IRQs when it releases the VT, but 
> we could make that just affect vblank interrupts if needed (yay more 
> i915_irq.c changes).

Yeah, I think that's going to be necessary unfortunately, otherwise we 
lose support for changing brightness outside X.

-- 
Matthew Garrett | mjg59@srcf.ucam.org

  reply	other threads:[~2008-12-01 19:32 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-28  6:47 [intel/acpi] backlight Yves-Alexis Perez
2008-11-28 19:18 ` [intel/acpi] backlight - T61 Len Brown
2008-11-28 22:38   ` Thomas Renninger
2008-11-28 22:50   ` Yves-Alexis Perez
2008-12-01  1:32     ` Zhang Rui
2008-12-01  3:18       ` Len Brown
2008-12-01  5:08         ` Zhang Rui
2008-12-03 23:14           ` Zhenyu Wang
2008-12-04  2:50             ` [Intel-gfx] " Zhenyu Wang
2008-12-09 21:24             ` Jesse Barnes
2008-12-01  1:08 ` [intel/acpi] backlight Zhao Yakui
2008-12-01  3:28   ` Len Brown
2008-12-01  8:38     ` Matthew Garrett
2008-12-01 19:27       ` Jesse Barnes
2008-12-01 19:32         ` Matthew Garrett [this message]
2008-12-01 11:11   ` Yves-Alexis Perez

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=20081201193215.GA23773@srcf.ucam.org \
    --to=mjg59@srcf.ucam.org \
    --cc=corsac@debian.org \
    --cc=jbarnes@virtuousgeek.org \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=yakui.zhao@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.