On Fri, 12 Sep 2014, Andrew Lutomirski wrote: > I think that v5 doesn't change behavior anywhere except for fixing > broken things. I could easily be wrong, though. Well, I can test it on a T43 (old-style hardware mixer), but not on anything else. I'll need to port the patch to 3.10 for that, though. > I kind of suspect that all laptops that don't default to the "none" > mode are at least a little bit broken, though. Any laptop on which > pressing mute mutes the hardware mixer *and* sends KEY_MUTE is going > to screw up if any modern GUI volume manager is running. Ideed. > Do you mean getting rid of latch mode and only keeping "none" and > "toggle"? I don't think that would be much simpler. The issue (from Then let's not do it. Latch mode is the sane one. > So most of the complexity is in the code that eats KEY_MUTE events and > does the right thing with them. I think that this is needed to get > "latch" and "toggle" right. Well, code complexity _is_ an acceptable price to get those right if we can manage it. > TBH, anyone running newish userspace probably wants the completely > non-magical "none" behavior. PulseAudio seems to do the right thing > if the mute button generates KEY_MUTE and does nothing else. I'm not > entirely convinced that there's any need to support the other modes, > but maybe I'm missing something, or maybe there are users with no > KEY_MUTE handler, or maybe there are users that just really like the > latching behavior where pressing the mute button never unmutes. Support for the other modes is optional, as long as the old thinkpads with full EC-driven behaviour still keep working in latch mode (which is the only one they support in firmware, anyway). -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh -- To unsubscribe from this list: send the line "unsubscribe platform-driver-x86" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
