[Nouveau] [Bug 86539] [NVAC] Trying to register nv_backlight after NV96 did it

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Sat Jan 23 03:55:51 PST 2016


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

--- Comment #4 from Pierre Moreau <pierre.morrow at free.fr> ---
Updated to 4.4, and still getting the same issue (which is still solved by
using NvForcePost=1).

I'm not sure how backlight is supposed to be managed in a multi-screen (same
backlight value set for all screens attached to a card?) and/or multi-gpu
situation (one backlight value per card?), but:

* If each card can have it's own backlight configuration, shouldn't the naming
of Nouveau's backlight path (/sys/class/nv_backlight) take that into account,
to avoid different cards registering to the same backlight entry point?

* When should a backlight interface be registered? If connectors are found,
regardless of if any screens are connected to those? Currently Nouveau iterates
over all LVDS and eDP connectors of a device, and will register one if the
"brightness value" (NV50_PDISP_SOR_PWM_CTL(i)) is different of 0. So if a
device has an LVDS connector and a eDP one, both will try to register a
backlight under the same name (nv_backlight) if I understand the code
correctly.

Anyone who could weight in, Ben or Hans maybe?

Attached two dmesgs, one without the NvForcePost, the other with. It's
interesting to see that both see the connectors the same way, but due to
NV50_PDISP_SOR_PWM_CTL having a different value (as outlined in comment #1),
one will try to register and additional backlight while the other won't.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/nouveau/attachments/20160123/14b905e2/attachment.html>


More information about the Nouveau mailing list