Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Darjeeling] Configure Darjeeling clocks #25990

Merged
merged 2 commits into from
Jan 23, 2025

Conversation

Razer6
Copy link
Member

@Razer6 Razer6 commented Jan 23, 2025

This PR changes the Darjeeling clocks to:

  • main: 1 GHz
  • IO: 1 GHz
  • USB (Not used): 1 GHz
  • AON: 62.5 MHz

From IO, clkmgr derives a 500 MHz and 250 MHz Clock.

The clkmgr needed a tweak in the template. To measure the clock frequency, the clkmgr has some measurement circuitry. These regs are preloaded with defaults to (freq / f_aon) +- 10. For the 250 MHz IO_DIV4 clock, this ratio becomes 4 - 10, which is negative. This change ensures the lower value is clipped at 0.

main: 1GHz
io: 1GHz
usb (not used): 1 GHz
AON: 62.5 MHz

Signed-off-by: Robert Schilling <[email protected]>
@Razer6 Razer6 requested a review from a team as a code owner January 23, 2025 15:34
@Razer6 Razer6 requested review from matutem, rswarbrick, vogelpi, alees24 and a team and removed request for a team and matutem January 23, 2025 15:34
Copy link
Contributor

@alees24 alees24 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for this, and for clarifying the clocking scheme. Let's just wait until CI is happy.

@Razer6
Copy link
Member Author

Razer6 commented Jan 23, 2025

One thing that is missing here is the clock generators within the AST need to be tweaked to output those frequencies.

@alees24 alees24 merged commit bf66a73 into lowRISC:master Jan 23, 2025
38 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants