Skip to content

Conversation

@maass-hamburg
Copy link
Member

move changeable peripherals from dtsi to board, as in litex these can change and might be on
different registers on custom out of tree
boards. So we limit riscv32-litex-vexriscv.dtsi
to just the interrupt controller and the cpu,
which don't change.

move changeable peripherals from dtsi to board, as
in litex these can change and might be on
different registers on custom out of tree
boards. So we limit riscv32-litex-vexriscv.dtsi
to just the interrupt controller and the cpu,
which don't change.

Signed-off-by: Fin Maaß <[email protected]>
@sonarqubecloud
Copy link

Copy link
Member

@fkokosinski fkokosinski left a comment

Choose a reason for hiding this comment

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

Not necessarily related to this PR, but it would be cool if we could leverage HWMv2 a bit more with LiteX in Zephyr, i.e. prepare more out-of-the-box configurations like:

  • litex_vexriscv//min <- minimal configuration (uart + gpio + timers)
  • litex_vexriscv//net <- net-capable config
  • and so on

@maass-hamburg
Copy link
Member Author

little ping @tgorochowik or any of the other reviewers for the second +1

@jhedberg jhedberg merged commit fc7a01a into zephyrproject-rtos:main Oct 21, 2025
35 checks passed
@maass-hamburg maass-hamburg deleted the litex_vexriscv_move_peripherals branch October 21, 2025 14:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area: Boards/SoCs area: RISCV RISCV Architecture (32-bit & 64-bit) platform: LiteX

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants