ayaneo-pocket-s2: Fix standby#1
Open
Drakulix wants to merge 1 commit intosuperna9999:topic/sm8650/ayaneo-pocket-s2/pmos-v2from
Open
ayaneo-pocket-s2: Fix standby#1Drakulix wants to merge 1 commit intosuperna9999:topic/sm8650/ayaneo-pocket-s2/pmos-v2from
Drakulix wants to merge 1 commit intosuperna9999:topic/sm8650/ayaneo-pocket-s2/pmos-v2from
Conversation
Owner
|
Interesting, you should submit this upstream, I don't remember seing this waking up other devices |
Owner
|
Oh perhaps it's because of the fan |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
(opening PRs here, as I wasn't able to do that on gitlab.com.)
Trying to successfully enter any kind of suspend on the ayaneo pocket s2 was a journey.
After disabling a bunch of wakeup-sources, I was left with a few interrupts still ocasionally waking the devices and those turned out to be from the thermal sensors..
Apparently up/down events will also trigger wakeup, even though these are constantly triggered in normal usage.
Not sure if this is a correct fix and if I've understood the interrupt documentation correctly, but it seems to be doing, what it is supposed to, which is keeping up/down-interrupts from waking the device (while hopefully keeping critical-interrupts working to emergency shutoff the device).
With this the device can at least enter s2idle correctly without sporadically waking up.