asus-dumo: linux: 5.7 -> 5.8 #192
Merged
Conversation
This file contains 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
With a patch to work around a regression with sbs-battery
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The 5.8 update seems to come with at least two regressions with the
sbs-batterydriver that affects at the very leastasus-dumo. One is that there are accesses to unknown registers, which wouldn't do much harm. The other already being worked on upstream is that the battery is being constantly reset, causing a storm of messages that can be observed in the EC log.There may be a third regression, which may be causing
udevadmto fail to pass properly, which will be investigated once 5.9 hits, as too much time has been spent on that device for the time being.(I was also looking at the issues with the display not resuming after being powered down from DPMS, and nothing good has been found.)