Warning: Can't synchronize with repository "(default)" (No changeset 96d22ec3fa3ef6de3ea8dc0d7d398adc9aa071cf in the repository). Look in the Trac log for more information.

Ticket #370 (closed enhancement: fixed)

Opened 4 years ago

Last modified 4 years ago

Display resource configuration

Reported by: vegyraupe Owned by: mickey
Priority: major Milestone:
Component: framework/oeventsd Version:
Keywords: Cc:

Description

quote "i think we should make configurable whether the DisplayResource? prevents dimming" mickey

The question raised was, should the display dimm during call. As we had diverging opinions mickey said it should be configurable to begin with.

Change History

comment:1 Changed 4 years ago by daniel

So what are you proposing? What exactly is the problem?

comment:2 Changed 4 years ago by daniel

Sounds like there's no problem then?

The Display resource controls whether the display dimms or not. CPU resource controls (auto) suspend. So if your application wants the Display to stay on just request the Display resource.

comment:3 Changed 4 years ago by stefan

I'm along with Daniel here. We have the CPU resource to control suspend and the display resource to control dimming.

If you think more is needed it would be good to explain your use-case.

comment:4 Changed 4 years ago by mickey

  • Owner changed from jluebbe to mickey
  • Status changed from new to accepted

I slowly remember what we talked about. It was about which idlenotifier level is actually be blocked by the Display resource, whether it is allowed to enter idle_dim or not. I still agree that this should be configurable, it's easy enough to do that.

comment:5 Changed 4 years ago by mickey

  • Status changed from accepted to closed
  • Resolution set to fixed

fixed in 7e1c1a3e2eebbcaefdb35f5b56342e7c727a576e, to allow for dimming, set: 

[fsodevice.kernel_idle]
display_resource_allows_dim = 1
Note: See TracTickets for help on using tickets.