RFC - fix RTC alias for 6.1.x kernel series #232
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
tim-seoss
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.
DRAFT - RFC
This device tree overlay (and also various others in the tree which have been derived from it) assign the alias rtc1 to the SoC realtime clock via its device tree path - this makes Debian and the kernel do the right thing with a fully functioning rtc at
/dev/rtc0. Between the 4.19.x kernel series and the 6.1.x kernel series, the path for this changed from/ocp/rtc@44e3e000to/ocp/interconnect@44c00000/segment@200000/target-module@3e000/rtc@0.This change breaks backward compatibility. The parent device tree path:
/__symbols__/rtcpoints to the correct path in both kernel series, but I don't think it's possible to utilise this in a devicetree overlay.