[Bug 39550] [NV96] Brightness stuck to low value after suspend/resume on HP Elitebook 8530w - bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ

From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 39550] [NV96] Brightness stuck to low value after suspend/resume on HP Elitebook 8530w
Date: Sun, 01 Sep 2013 15:28:20 +0000	[thread overview]
Message-ID: <bug-39550-8800-8dLEBxfpEk@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-39550-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>

[-- Attachment #1.1: Type: text/plain, Size: 1612 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=39550

Roy <r.spliet-oe7qfRrRQfeEZXFvZSAUrfP6llvjuJOh@public.gmane.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |NEEDINFO
           Assignee|nouveau-PD4FTy7X32lNgt0PjOBp93rCq3LdnpKM@public.gmane.org |r.spliet-oe7qfRrRQfeEZXFvZSAUrfP6llvjuJOh@public.gmane.org
                   |rg                          |
  Attachment #85010|0                           |1
        is obsolete|                            |

--- Comment #46 from Roy <r.spliet-oe7qfRrRQfeEZXFvZSAUrfP6llvjuJOh@public.gmane.org> ---
Created attachment 85012
  --> https://bugs.freedesktop.org/attachment.cgi?id=85012&action=edit
drm/nv50: Fix backlight not working when PWM_DIV is uninitialised (v2)

V2 fixes the reach of this patch.
From what I can tell the PWM_DIV is simply a divider for the initial PWM clock
or something, it does not affect the scope of the duty cycle. I therefore
assume 0x5e is always a good value to set. Traces from NV50:NVA0 would help
verify whether NVIDIA always sets this value or not.
This patch requires acpi_backlight=vendor to be set because it tests for the
presence of a backlight by testing drm->backlight. An alternative to this test
would be checking for the GPIO to be present and routed to SOR, but I wouldn't
be surprised if there is at least one device that expects our driver to route
it manually. How should we go about this?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 3397 bytes --]

[-- Attachment #2: Type: text/plain, Size: 181 bytes --]

_______________________________________________
Nouveau mailing list
Nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
http://lists.freedesktop.org/mailman/listinfo/nouveau