arch/[risc-v|xtensa]/src/common: Create SoC-specific initialization routine#18461
Open
tmedicci wants to merge 2 commits intoapache:masterfrom
Open
arch/[risc-v|xtensa]/src/common: Create SoC-specific initialization routine#18461tmedicci wants to merge 2 commits intoapache:masterfrom
tmedicci wants to merge 2 commits intoapache:masterfrom
Conversation
This commits adds a function that can be implemented by any vendor to allow SoC-specific functions to be called by `up_initialize`. Please note that `up_initialize` is provided by the arch level, but it doesn't allow SoC-specific initialization. Although it could be possible to run such initialization on board-level, semantically it isn't related to the board, but with the SoC. As an example of such implementation, some SoCs require RTC subsystem initialization to occur before the OS is completely initialized. Signed-off-by: Tiago Medicci Serrano <tiago.medicci@espressif.com>
This commits adds a function that can be implemented by any vendor to allow SoC-specific functions to be called by `up_initialize`. Please note that `up_initialize` is provided by the arch level, but it doesn't allow SoC-specific initialization. Although it could be possible to run such initialization on board-level, semantically it isn't related to the board, but with the SoC. As an example of such implementation, some SoCs require RTC subsystem initialization to occur before the OS is completely initialized. Signed-off-by: Tiago Medicci Serrano <tiago.medicci@espressif.com>
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
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.
Summary
Adds a function that can be implemented by any vendor to allow SoC-specific functions to be called by
up_initialize. Please note thatup_initializeis provided by the arch level, but it doesn't allow SoC-specific initialization. Although it could be possible to run such initialization on board-level, semanticallyit isn't related to the board, but with the SoC. As an example of such implementation, some SoCs require RTC subsystem initialization to occur before the OS is completely initialized.
Impact
Impact on user: No.
Impact on build: No.
Impact on hardware: Yes. It allows performing SoC-specific initialization that is not board-dependent.
Impact on documentation: No.
Impact on security: No.
Impact on compatibility: No.
Testing
There is no specific testing for it at this moment. There is no implementation of it yet. This PR is part of a bigger refactor on Espressif devices to simplify its boot-up process and remove code from board-level, making it easier to support new SoCs.
For this moment,
osteston affected architectures may ensure that there is no compatibility issue. Taking ESP32-C6 as an example:Building
Running
Run
ostestas usual.Results