public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: Rainer Koenig <Rainer.Koenig@ts.fujitsu.com>,
	intel-gfx@lists.freedesktop.org,
	Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
Cc: "Jan-Marek Glogowski" <glogow@fbihome.de>,
	"Jonathan Woithe" <jwoithe@just42.net>,
	"Michał Kępień" <kernel@kempniu.pl>
Subject: Re: [PATCH v4 0/2] drm/i915/opregion: proper handling of DIDL and CADL
Date: Fri, 01 Jul 2016 16:51:36 +0300	[thread overview]
Message-ID: <877fd5pitz.fsf@intel.com> (raw)
In-Reply-To: <59222b96-f64c-6b37-2c2c-c6adbc5c2b44@ts.fujitsu.com>

On Fri, 01 Jul 2016, Rainer Koenig <Rainer.Koenig@ts.fujitsu.com> wrote:
> Found a problem: After screensaver kicked in and display was turned off
> the brightness keys stop working.
>
> Problem can be reproduced like that:
>
> 1. Boot laptop
> 2. Test brightness keys, they are working
> 3. open Terminal and issue "xset -display :0 dpms force off"
> 4. the screen goes blank (like after the screensaver timeout)
> 5. push a key to bring the screen back
> 6. test brightness keys again, now they don't work
>
> If the system is sent to suspend and woken up everything is fine again.
>
> Behaviour happens on the 4.7.0-rc5 kernel from the opregion-didl-v4 branch.
> Before I compiled the 4.7.0-r4 from the same git repository. On this
> (v3) everything still works after the screen was blanked.

Maarten, I think the difference is between where and when the calls to
cadl update are made.

BR,
Jani.


>
> Best regards
> Rainer
>
> Am 30.06.2016 um 11:19 schrieb Rainer Koenig:
>> Am 29.06.2016 um 17:36 schrieb Jani Nikula:
>>> This is v4 of [1]. The first three have already been pushed to
>>> drm-intel-next-queued. The only change here is the atomic commit.
>>>
>>> Review and testing would be much appreciated to move this forward. For
>>> testing, I've pushed this to opregion-didl-v4 branch of my repo at [2].
>>>
>> Tested on a Fujitsu LIFEBOOK E736: Brightness keys are working now.
>>
>> Best regards
>> Rainer
>>

-- 
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2016-07-01 13:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-29 15:36 [PATCH v4 0/2] drm/i915/opregion: proper handling of DIDL and CADL Jani Nikula
2016-06-29 15:36 ` [PATCH v4 1/2] drm/i915: make i915 the source of acpi device ids for _DOD Jani Nikula
2016-06-29 15:36 ` [PATCH v4 2/2] drm/i915/opregion: update cadl based on actually active outputs Jani Nikula
2016-07-04  5:13   ` Maarten Lankhorst
2016-06-29 16:23 ` ✗ Ro.CI.BAT: failure for drm/i915/opregion: proper handling of DIDL and CADL (rev4) Patchwork
2016-06-29 17:01 ` [PATCH v4 0/2] drm/i915/opregion: proper handling of DIDL and CADL Peter Wu
2016-06-30  9:19 ` Rainer Koenig
2016-07-01 12:12   ` Rainer Koenig
2016-07-01 13:51     ` Jani Nikula [this message]
2016-07-12 10:23       ` Maarten Lankhorst
  -- strict thread matches above, loose matches on Subject: below --
2016-08-15 11:24 Marcos Paulo de Souza

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=877fd5pitz.fsf@intel.com \
    --to=jani.nikula@intel.com \
    --cc=Rainer.Koenig@ts.fujitsu.com \
    --cc=glogow@fbihome.de \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jwoithe@just42.net \
    --cc=kernel@kempniu.pl \
    --cc=maarten.lankhorst@linux.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