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

[7.1.r1] arm64: dts: SoMC: Akatsuki: Set SDE to max performance mode #2591

Conversation

voidanix
Copy link

Turns out that akatsuki's clock calculation shenanigans do not only apply to 4.19.

See sailfishos-sony-tama/main#150 and sailfishos-sony-tama/main#203 for context (and epic artifacts).

This device has issues with the userspace libdisplayqos as
it will lock up the device due to a totally wrong calculation
of the bus bandwidth and MDP clock rates.

For this reason, sadly say NO to the battery improvements and
ramp up to the sky both busses and MDP clocks while the display
is on.

Signed-off-by: voidanix <[email protected]>
@MarijnS95
Copy link
Contributor

The funny thing is that I see a similar glitch - on non-Tama platforms - when changing brightness (the extra command is interrupting or otherwise affecting [available bandwidth for] the datastream).

@voidanix
Copy link
Author

Out of curiosity, do you also have some white pixelated/noisy, full-brightness screen flashes when pressing the power button? That seems to affect several devices too, but should be unrelated to this.

@bartcubbins
Copy link
Contributor

Out of curiosity, do you also have some white pixelated/noisy, full-brightness screen flashes when pressing the power button? That seems to affect several devices too, but should be unrelated to this.

this was fixed at some stage in the 9.12 kernel tag

@jerpelea jerpelea merged commit 05d534b into sonyxperiadev:aosp/LA.UM.7.1.r1 Nov 23, 2023
@voidanix
Copy link
Author

this was fixed at some stage in the 9.12 kernel tag

It still persists on kumano (both 4.14 and 4.19), no idea about akatsuki on 4.19 because it gets stuck on the bootloader logo (both with precompiled and built kernel w/ A12 and A13 clang).

@bartcubbins
Copy link
Contributor

It still persists on kumano

AOSP?

because it gets stuck on the bootloader logo

it's a blobs issue

@MarijnS95
Copy link
Contributor

MarijnS95 commented Nov 23, 2023

Out of curiosity, do you also have some white pixelated/noisy, full-brightness screen flashes when pressing the power button? That seems to affect several devices too, but should be unrelated to this.

Not on mainline that I recall, but the panel off/on sequence is a bit off with "desktop-y" window/session managers.

EDIT: I can retry with the ACTIVE DRM connector/CRTC property, we've used that to test our shutdown paths but I don't remember what corruption appeared; the DSI power sequence is still being amended upstream due to not perfectly fitting with the drm_bridge design.

@voidanix
Copy link
Author

AOSP?

Yeah AOSP11 and AOSP12, the issue gets down to SFOS too.

it's a blobs issue

I see... Hope there will be a fix for this eventually.

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

Successfully merging this pull request may close these issues.

5 participants