From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 106901] Brightness / WIFI Key does not generate any events
Date: Thu, 05 Nov 2015 06:46:35 +0000 [thread overview]
Message-ID: <bug-106901-2300-Jx9LVZY9Ap@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-106901-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=106901
Aaron Lu <aaron.lu@intel.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDINFO |ASSIGNED
Component|Power-Video |Video(DRI - non Intel)
Assignee|aaron.lu@intel.com |drivers_video-dri@kernel-bu
| |gs.osdl.org
Product|ACPI |Drivers
--- Comment #15 from Aaron Lu <aaron.lu@intel.com> ---
I have no idea why the acpi_video inteface doesn't work, the _BCM control
method is there, but just doesn't work.
The _BCM control method did some setting on the GPU's PCI config space, that
may trigger GPU driver to do the actual handling, but then this is driver
specific, maybe nvidia/nouveau driver has this knowledge.
As for the notification, the firmware decides to send the notification only
when the _DCS control method returns 0x1f:
Method (_Q0E, 0, NotSerialized) // _Qxx: EC Query
{
If ((MSOS () < OSW8))
{
SBRN ()
}
If ((MSOS () >= OSVT))
{
Local0 = LBTN /* \_SB_.LBTN */
If (^^^PEG0.GFX0.PRST ())
{
If ((^^^PEG0.GFX0.LCDD._DCS () != 0x1F))
{
If ((^^^PEG0.GFX0.EDPD._DCS () != 0x1F))
{
Return (One)
}
}
^^^PEG0.GFX0.DWBL ()
ASBN = One
}
The _DCS is:
Method (_DCS, 0, NotSerialized) // _DCS: Display
Current Status
{
CHA1 = One
CHA2 = One
CHA3 = Zero
Notify (GFX0, 0xF0) // Hardware-Specific
While ((CHA2 == One))
{
Sleep (0x32)
If ((CHA3 != One))
{
CHA2 = Zero
}
}
ACTD = MD2A (ACTD)
AVLD = MD2A (AVLD)
Local0 = ACTD /* \_SB_.ACTD */
Local0 = AVLD /* \_SB_.AVLD */
If (Local0)
{
If ((Local0 & EDPM))
{
Return (0x1F)
}
}
Return (0x1D)
}
The AVLD is retrieved from a memory field, I doubt it depends on the GPU driver
to set this value.
We should let the GPU people to take a look.
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next parent reply other threads:[~2015-11-05 6:47 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-106901-2300@https.bugzilla.kernel.org/>
2015-11-05 6:46 ` bugzilla-daemon [this message]
2015-11-20 11:18 ` [Bug 106901] Brightness / WIFI Key does not generate any events bugzilla-daemon
2015-11-20 11:19 ` bugzilla-daemon
2015-11-20 11:20 ` bugzilla-daemon
2015-12-13 18:27 ` bugzilla-daemon
2015-12-13 18:27 ` bugzilla-daemon
2015-12-13 18:37 ` bugzilla-daemon
2015-12-13 18:55 ` bugzilla-daemon
2015-12-17 16:02 ` bugzilla-daemon
2015-12-17 16:04 ` bugzilla-daemon
2015-12-17 16:06 ` bugzilla-daemon
2015-12-17 16:07 ` bugzilla-daemon
2015-12-17 16:08 ` bugzilla-daemon
2015-12-17 16:11 ` bugzilla-daemon
2016-01-15 13:13 ` bugzilla-daemon
2016-01-15 13:14 ` bugzilla-daemon
2016-01-15 13:14 ` bugzilla-daemon
2016-01-15 13:15 ` bugzilla-daemon
2016-03-09 13:05 ` bugzilla-daemon
2016-03-09 13:05 ` bugzilla-daemon
2016-03-21 10:44 ` bugzilla-daemon
2016-03-21 10:45 ` bugzilla-daemon
2016-03-21 10:45 ` bugzilla-daemon
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=bug-106901-2300-Jx9LVZY9Ap@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
/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