Date: Thu, 05 Sep 2013 22:04:56 +0200 From: Bengt Ahlgren <bengta@sics.se> To: Jung-uk Kim <jkim@FreeBSD.org> Cc: Kevin Oberman <rkoberman@gmail.com>, freebsd-acpi <freebsd-acpi@FreeBSD.org>, Laura Marie Feeney <lmfeeney@sics.se>, Gleb Smirnoff <glebius@FreeBSD.org>, "Sergey A. Osokin" <osa@FreeBSD.org>, =?iso-8859-1?Q?Jean-S=E9bastien_P=E9dron?= <dumbbell@FreeBSD.org> Subject: Re: suspend/resume on Lenovo X1 (regression from reports on wiki) Message-ID: <uh7ob87nifr.fsf@P142.sics.se> In-Reply-To: <5227CAF0.5040300@FreeBSD.org> (Jung-uk Kim's message of "Wed, 04 Sep 2013 20:06:08 -0400") References: <521D03AE.3050709@sics.se> <201309031647.47650.jhb@freebsd.org> <522669AF.5000209@FreeBSD.org> <201309040929.35903.jhb@freebsd.org> <52276554.6020807@FreeBSD.org> <uh7a9jsl7qf.fsf@P142.sics.se> <522791D2.9050606@FreeBSD.org> <uh71u54ky9g.fsf@P142.sics.se> <5227B893.1000509@FreeBSD.org> <5227CAF0.5040300@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Jung-uk Kim <jkim@FreeBSD.org> writes: > On 2013-09-04 18:47:47 -0400, Jung-uk Kim wrote: >> On 2013-09-04 18:39:07 -0400, Bengt Ahlgren wrote: >>> The value of hw.acpi.video.lcd0.brightness changes when the >>> screen brightness keys (Fn+Home/End) are pressed, but nothing >>> happens with the screen. Same goes for changing the value with >>> sysctl. After a fresh boot it works with one issue. The screen >>> brightness level seems to lag behind one keypress. Without >>> acpi_video, screen brightness changes without the lag. >> >>> hw.acpi.video.lcd0.active is always stuck at 0 - can't change >>> with sysctl (regardless if the screen is on after a fresh boot, >>> or black after a text console suspend/resume): >> >>> [root@bit ~]# sysctl hw.acpi.video.lcd0.active=1 >>> hw.acpi.video.lcd0.active: 0 -> 0 >> >>> Again, for my old X40 with non-KMS Xorg intel driver has >>> (curiously, the screen blinks when issuing this sysctl command): >> >>> [bengta@P142 ~]$ sysctl hw.acpi.video hw.acpi.video.lcd0.active: >>> 1 hw.acpi.video.crt0.active: 0 >> >> Then, KMS probably breaks acpi_video(4), too. :-( > > kib let me know that there is a way to make it work but it was not > well-integrated to i915kms.ko. If you are interested in fixing it, > dev/drm2/i915/intel_opregion.c is the source and you can download the > specification from here: > > https://01.org/linuxgraphics/sites/default/files/documentation/acpi_igd_opregion_spec.pdf Hmm, scanning that spec, I wonder whether the opregion functionality is better placed together with acpi_video, and then i915kms makes calls to that instead? Hmm, again, perhaps the intel platform needs opregion support to work properly also without the kms driver. Could be an explanation for the backlight issues. (Just speculation so far... I have no idea if/how this relates to or interacts with options VESA) Bengt
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?uh7ob87nifr.fsf>