[pulseaudio-tickets] [Bug 93946] Changing device profile to HDMI is reset to default after monitor goes into powersave

[bugzilla-daemon at freedesktop.org]

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

--- Comment #61 from Tanu Kaskinen <tanuk at iki.fi> ---
(In reply to Arun Raghavan from comment #60)
> At least equally bad in my opinion, so I'd prefer avoiding trading one
> regression for another.

Regression compared to what?

In 7.0 we kept the HDMI profile active until the user manually switches the
profile.

In 8.0 we started to switch away from HDMI when it becomes unavailable.

My patches introduce no regression compared to 7.0 as far as I can see. There
is a regression compared to 8.0, but in my books that doesn't count, because
the routing changes in 8.0 shouldn't have been included in the release. The
readily-available reasonable options that we have are to either revert
everything back to 7.0 level, or apply my patches. Both of those cause a
"regression" compared to 8.0, but I think that's fine. We can avoid the
regression only by keeping things as they are (which is not a good idea in my
opinion) or coming up with some new patches.

(In reply to Arun Raghavan from comment #59)
> There seemed to be some discussion around this at:
> 
>  
> https://lists.freedesktop.org/archives/pulseaudio-discuss/2016-February/
> 025394.html

Ok. I guess this (modifying graphics drivers) is not a viable solution for 9.0
(at least I'm not volunteering to modify the drivers).

> Doing a port based on ELDs is one way to do this. The other way to do this
> is to change how we store preferred_port in module-card-restore from a
> boolean choice to some other mechanism that allows a more fine-tuned
> selection of whether the port is the preferred port or not.
> 
> As an example, it could be a list of key/value pairs such that if we find
> any property on a card's port that matches the given (key, value), then it
> is a preferred port. We could special-case the "name" key to just be the
> port's name.
> 
> Now this does mean that module-card-restore will need to start being aware
> of the property we'll be adding on the ports. I don't see a way to avoid
> that.

I'd rather not do this, because I think you overstate the severity of the
problem, and because a cleaner solution would be to dynamically create ports
based on ELD, and any additions to the card-restore database schema will have
to be supported indefinitely. But if you really think this is the best way
forward, I can write new patches implementing this.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/pulseaudio-bugs/attachments/20160503/69beef6f/attachment.html>