Add "fb notify" quirk, fixing motorola-addison touch with boot GUI #154
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
This quirk touches the `blank` file of the framebuffer /sys nodes, which ends up unsuspending things that start suspended until the *right thing* is happening to not be suspended. X11, among others, do the right things. It seems other framebuffer interfaces are not. This can likely be fixed in other ways, but this is the more approachable way to me right now.
samueldr
changed the title
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.
Quite simply,
motorola-addison's touch input will not work if the display has not been properly "awakened".Touching
.../blankends up causingfb_notifier_call_chainto be called, which ends up causingrmi4_data->panel_nb.notifier_callto be called, causingsynaptics_dsx_panel_cbto be called. This, finally, puts the touch panel active. (grepthe vendor kernel tree for those names.)X11 touch input was working fine. It must be doing things just right to wake up the framebuffer. LVGL does not, which means the boot GUI did not work.