I thought I would have a proposal up already but too many other things got in the way last week.
You only have to use the dummy buffer consumer when the screen is off (arguably not even then). When it's on you can do normal composition/occlusion testing. And the dummy consumer does not need to be woken (hence avoiding this bug).
Weirdly that would make Mir's power usage potentially lower when the screen is on than when it's off. So that would be motivation to implement similar smarts for the screen off case.
Essentially the dumb buffer consumer that was introduced recently just needs to be smarter. That can be done a variety of ways. Although I don't see any need for adding new message types for clients to interpret.
I thought I would have a proposal up already but too many other things got in the way last week.
You only have to use the dummy buffer consumer when the screen is off (arguably not even then). When it's on you can do normal composition/ occlusion testing. And the dummy consumer does not need to be woken (hence avoiding this bug).
Weirdly that would make Mir's power usage potentially lower when the screen is on than when it's off. So that would be motivation to implement similar smarts for the screen off case.
Essentially the dumb buffer consumer that was introduced recently just needs to be smarter. That can be done a variety of ways. Although I don't see any need for adding new message types for clients to interpret.