From: Martin Steigerwald <Martin@lichtvoll.de>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: James Hogan <james@albanarts.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Kamal Mostafa <kamal@canonical.com>,
Matthew Garrett <matthew.garrett@nebula.com>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Steven Newbury <steve@snewbury.org.uk>
Subject: Re: Linux 3.11-rc2
Date: Mon, 22 Jul 2013 15:15:38 +0200 [thread overview]
Message-ID: <3298830.Snx2ykMFY6@merkaba> (raw)
In-Reply-To: <5728692.GlhGgHY92H@vostro.rjw.lan>
Am Montag, 22. Juli 2013, 15:02:22 schrieb Rafael J. Wysocki:
> On Monday, July 22, 2013 12:08:40 AM James Hogan wrote:
> > On 21 July 2013 20:53, Linus Torvalds <torvalds@linux-foundation.org>
wrote:
> > > (b) we had a late change to how ACPI backlight handling is done on
> > >
> > > certain machines, and while this kind of thing really shouldn't be
> > > done outside the merge window, I ended up pulling it anyway. But I'd
> > > *really* like to have people test this thing particularly on laptops
> > > with intel-based graphics. It should only matter (and hopefully
> > > improve things) for the newer ones with BIOSes designed for Windows 8,
> > > but hey, the more testing, the better. Backlight handling has beenin
> > > painful before, so I'm mentioning this explicitly.
> >
> > 8c5bd7a "ACPI / video / i915: No ACPI backlight if firmware expects
> > Windows 8" breaks backlight control for me because
> > /sys/class/backlight/acpi_video0 disappears, and
> > /sys/class/backlight/intel_backlight doesn't seem to have any effect.
> >
> > Note that acpi_video0 only worked because I was applying "[PATCH]
> > drm/i915: quirk no PCH_PWM_ENABLE for Dell XPS13 backlight" [1], so
> > strictly speaking mainline already didn't work.
>
> James, sorry for breaking things for you. The patch you're mentioning is
> going to hit the mainline at one point anyway I suppose.
Dunno whether thats related, but after locking screen today and screen blanker
kicking in (just a blank screen), I was not able to reactivate the display
again by typing a key or so unless I closed the laptop display lid, let the
machine suspend (to ram) and opened it again.
Plain 3.11-rc2 on ThinkPad T520:
martin@merkaba:~> phoronix-test-suite system-info
Phoronix Test Suite v4.6.0
System Information
Hardware:
Processor: Intel Core i5-2520M @ 3.20GHz (4 Cores), Motherboard: LENOVO
42433WG, Chipset: Intel 2nd Generation Core Family DRAM, Memory: 8192MB, Disk:
300GB INTEL SSDSA2CW30 + 30GB INTEL SSDMCEAC03, Graphics: Intel 2nd Generation
Core Family IGP, Audio: Conexant CX20590, Network: Intel 82579LM Gigabit
Connection + Intel Centrino Advanced-N 6205
Software:
OS: Debian unstable, Kernel: 3.11.0-rc2-tp520 (x86_64), Desktop: KDE 4.10.5,
Display Server: X Server 1.12.4, Display Driver: intel 2.20.14, OpenGL: 3.0
Mesa 9.1.4, Compiler: GCC 4.8, File-System: btrfs, Screen Resolution:
1920x1080
Thanks,
--
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7
next prev parent reply other threads:[~2013-07-22 13:15 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-21 19:53 Linux 3.11-rc2 Linus Torvalds
2013-07-21 21:07 ` Tobias Klausmann
2013-07-22 13:08 ` Rafael J. Wysocki
2013-07-22 15:43 ` Tobias Klausmann
2013-07-21 23:08 ` James Hogan
2013-07-22 13:02 ` Rafael J. Wysocki
2013-07-22 13:15 ` Martin Steigerwald [this message]
2013-07-22 13:37 ` Rafael J. Wysocki
2013-07-22 18:46 ` Martin Steigerwald
2013-07-22 19:57 ` Rafael J. Wysocki
2013-07-24 5:10 ` Kalle Valo
2013-07-22 13:21 ` James Hogan
2013-07-22 18:11 ` Linus Torvalds
2013-07-22 19:54 ` Rafael J. Wysocki
2013-07-23 18:46 ` Linux 3.11-rc2 (acpi backlight) Kamal Mostafa
2013-07-24 0:05 ` Rafael J. Wysocki
2013-07-24 4:54 ` Steven Newbury
2013-07-24 6:49 ` James Hogan
2013-07-24 7:14 ` Mike Galbraith
2013-07-24 7:19 ` Igor Gnatenko
2013-07-24 12:06 ` Rafael J. Wysocki
2013-07-24 11:45 ` Jörg Otte
2013-07-25 13:00 ` Linux 3.11-rc2 (acpi backlight, revert) Rafael J. Wysocki
2013-07-25 14:43 ` Kamal Mostafa
2013-07-25 14:46 ` Daniel Vetter
2013-07-25 14:59 ` Kamal Mostafa
2013-07-25 14:52 ` Jörg Otte
2013-07-25 15:52 ` Jörg Otte
2013-07-25 19:14 ` James Hogan
2013-07-25 19:47 ` Rafael J. Wysocki
2013-07-26 4:23 ` Joerg Platte
2013-07-26 11:22 ` Igor Gnatenko
2013-07-26 7:43 ` Steven Newbury
2013-07-26 12:09 ` Martin Steigerwald
2013-07-26 12:40 ` Rafael J. Wysocki
2013-08-04 19:33 ` Martin Steigerwald
2013-08-04 22:15 ` Rafael J. Wysocki
2013-07-27 5:34 ` Kalle Valo
2013-07-27 12:18 ` Rafael J. Wysocki
2013-07-22 18:16 ` Linux 3.11-rc2 Matthew Garrett
2013-07-22 19:56 ` Rafael J. Wysocki
2013-07-23 17:47 ` Steven Newbury
2013-07-23 19:51 ` Matthew Garrett
2013-07-23 21:10 ` Steven Newbury
2013-07-23 21:24 ` Rafael J. Wysocki
2013-07-23 22:49 ` Steven Newbury
2013-07-22 1:25 ` Dave Chinner
2013-07-22 4:06 ` Al Viro
2013-07-24 3:22 ` Dave Chinner
2013-07-23 1:04 ` rydberg
2013-07-23 1:17 ` Myklebust, Trond
2013-07-23 18:31 ` Myklebust, Trond
2013-07-23 19:08 ` rydberg
2013-07-23 20:42 ` Linus Torvalds
2013-07-23 20:52 ` Myklebust, Trond
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=3298830.Snx2ykMFY6@merkaba \
--to=martin@lichtvoll.de \
--cc=james@albanarts.com \
--cc=kamal@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew.garrett@nebula.com \
--cc=rafael.j.wysocki@intel.com \
--cc=rjw@sisk.pl \
--cc=steve@snewbury.org.uk \
--cc=torvalds@linux-foundation.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