'Twas brillig, and Arun Raghavan at 25/01/11 07:51 did gyre and gimble: > On Mon, 2011-01-24 at 14:14 -0800, pl bossart wrote: >>> FWIW, the zero-length wait seems to work fine for me as well (also >>> HDAudio). A couple of things to consider if we do decide to go ahead >>> with this are are that: >> >> Any ideas on how we can make this timeout sink-specific? Everything I >> know of (default.pa, module-udev-detect) will set this timeout for all >> possible sinks. Not clear to me how I can make this configuratble. >> Properties maybe, but I don't know how to set them with a command or >> configuration file. > > I can't think if anything simple to handle this. However. if we're going > to have to apply some policy on a per-profile basis, perhaps we could > let modules set a "can-quick-suspend" property or some such on the sink > which module-suspend-on-idle can look for. This leaves the decision to > the module that exposes the sink which, in theory, knows best about this > anyway. Yeah that's pretty much what I suggested earlier in the thread too - put some new flag in the mixer profile that ultimately sets a property on the sink that module-suspend-on idle can look for. It's maybe not the most elegant but I thin it's quite practical for the current use case. Col -- Colin Guthrie gmane(at)colin.guthr.ie http://colin.guthr.ie/ Day Job: Tribalogic Limited [http://www.tribalogic.net/] Open Source: Mageia Contributor [http://www.mageia.org/] PulseAudio Hacker [http://www.pulseaudio.org/] Trac Hacker [http://trac.edgewall.org/]
