Skip to content

Conversation

adamkondraciuk
Copy link
Contributor

@adamkondraciuk adamkondraciuk commented Oct 1, 2025

GRTC is used by the logger, so it must be initialized
as early as possible. On the other hand, clock requests
are allowed once the clock control API has been initialized.
This PR introduces a two-stage GRTC initialization to meet
these requirements.

@nordic-krch
Copy link
Contributor

Can you add a comment in commit message with reasoning behind splitting init into two stages?

GRTC is used by the logger, so it must be initialized
as early as possible. On the other hand, clock requests
are allowed once the clock control API has been initialized.
This PR introduces a two-stage GRTC initialization to meet
these requirements.

Signed-off-by: Adam Kondraciuk <adam.kondraciuk@nordicsemi.no>
@adamkondraciuk adamkondraciuk force-pushed the NRFX-8454-Move_GRTC-initialization branch from 08656d6 to fa3cb0a Compare October 2, 2025 16:59
Copy link

sonarqubecloud bot commented Oct 2, 2025

@bjarki-andreasen
Copy link
Contributor

Are you certain the logger is available pre kernel? semaphores and the kernel/system timer are not available before POST_KERNEL, so I would expect logging to not be ready either

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants