We are seeing bugs that mute led is out-of-sync with OS's mute.
Steps to duplicate:
1. Press mute hotkey - it generates scancode and turns on mute led
2. Unmute by desktop application.
Expected result: System is un-muted and led is turned off
Actual result: System, depending on models, can be muted or unmuted. The led is always on.
One solution to the problem is to disable hardware mute. Mute hotkey will only generate scancode but led will not be toggled.
The other solution will be to develop an application or improve existing desktop daemons to handle the event as previously discussed, but it will need to have the sysfs nodes for mute/led controls.
On Wed, Aug 14, 2013 at 1:54 PM, Matthew Garrett <matthew.garrett@xxxxxxxxxx> wrote:
On Wed, 2013-08-14 at 13:53 +0800, Alex Hung wrote:Is there any reason you'd want this rather than just having it generate
> Hi Matthew,
>
>
> The scenario will be to have an user-application to listen to the mute
> key event, compare to hardware mute against OS mute, and sync both
> mute. When the application is loaded, it can use this interface to
> enable it; when it is unloaded it can disable it.
a scancode and be under userspace control?
--
Matthew Garrett <matthew.garrett@xxxxxxxxxx>
--
Cheers,
Alex Hung
Alex Hung
------------------------------------------------------------------------------ Get 100% visibility into Java/.NET code with AppDynamics Lite! It's a free troubleshooting tool designed for production. Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
_______________________________________________ ibm-acpi-devel mailing list ibm-acpi-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/ibm-acpi-devel
