Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

intel/display: switching off connectors not reflected (regression) #5404

Open
chelmuth opened this issue Dec 12, 2024 · 5 comments
Open

intel/display: switching off connectors not reflected (regression) #5404

chelmuth opened this issue Dec 12, 2024 · 5 comments

Comments

@chelmuth
Copy link
Member

If connectors are switched off in Sculpt 24.10.3, the capture session is terminated but the connectors report does reflect the enabled="false" state (while brightness becomes 0 on my notebook-internal connector though).

@chelmuth chelmuth added the bug label Dec 12, 2024
@chelmuth chelmuth changed the title intel/display: switching connectors off is not reflected (regression) intel/display: switching off connectors not reflected (regression) Dec 12, 2024
@chelmuth
Copy link
Member Author

I suspect the regression in changes to lx_emul_i915_iterate_modes() and inuse handling that no longer examines crtc members.

alex-ab added a commit to alex-ab/genode that referenced this issue Dec 12, 2024
@alex-ab
Copy link
Member

alex-ab commented Dec 12, 2024

@chelmuth: please try the commit fee0c4a. Somehow the reporting of the connectors enable state seems to be not reported at all atm.

@chelmuth
Copy link
Member Author

IIRC we refrained from adding this attribute some weeks ago as a missing <mode ... used="true"> reflects the same information. I had a look into sculpt_manager that implements its Off state this way and, thus, could not profit from the patch.

alex-ab added a commit to alex-ab/genode that referenced this issue Dec 12, 2024
@alex-ab
Copy link
Member

alex-ab commented Dec 12, 2024

Okay, I got than the bug report wrong, which talked about connector and enable. Though, commit 7baeea7 should help if is related to the used state.

@chelmuth
Copy link
Member Author

Great, it works again with the patch applied.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants