Hi list,
I have an Asus laptop, and these two patches solved my problem with
bright hot-keys not working[1].
I applied both patches on 4.8-rc1, and the only necessary fix was
changing priv_dev->dev to priv_dev->drm in all places of for_each_*
macros touched by these patches.
Is there any chance
Op 01-07-16 om 15:51 schreef Jani Nikula:
> On Fri, 01 Jul 2016, Rainer Koenig 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
On Fri, 01 Jul 2016, Rainer Koenig 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 -displa
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
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
Hi Jani,
I just tested your branch (2f9a317) and can confirm that the fix is still
valid. evtest reports brightness up/down events.
Kind regards,
Peter
https://lekensteyn.nl
(pardon my brevity, top-posting and formatting, sent from my phone)
On 29 June 2016 17:36:40 CEST, Jani Nikula wrote:
>
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].
Maarten, please check the
