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

dts: bindings: nrf-vpr: Allow specifying pins and not using launcher #88168

Merged
merged 1 commit into from
Apr 8, 2025

Conversation

anangl
Copy link
Member

@anangl anangl commented Apr 4, 2025

Add possibility to use pinctrl to configure pins that should be assigned to nRF VPR coprocessors and also provide a way of preventing activation of the nordic_vpr_launcher driver for an enabled VPR so that it can be supplied with the code to execute and launched in a custom way.

Add possibility to use pinctrl to configure pins that should be assigned
to nRF VPR coprocessors and also provide a way of preventing activation
of the nordic_vpr_launcher driver for an enabled VPR so that it can be
supplied with the code to execute and launched in a custom way.

Signed-off-by: Andrzej Głąbek <andrzej.glabek@nordicsemi.no>
Comment on lines +20 to +22
by the nordic_vpr_launcher driver when the node is enabled. In such case,
the launching is supposed to be done explicitly by the user code, in some
custom way presumably.
Copy link
Collaborator

Choose a reason for hiding this comment

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

I'm curious about this comment. I assume that a custom way of launching VPR boils down to allowing the App core to determine at runtime when and/or where it boots the VPR. Should this really be covered by zephyr,deferred-init and maybe an extra driver API for setting the execution address before calling device_init()?

Copy link
Member Author

@anangl anangl Apr 4, 2025

Choose a reason for hiding this comment

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

This is also about a custom way of supplying the code to be executed by the VPR. The application my want to copy the code to RAM by itself and then start the VPR, so in fact do everything that is provided by the nordic_vpr_launcher driver but in its own way (this is in fact an actual use case for which I need these changes).

@kartben kartben merged commit 54d8c80 into zephyrproject-rtos:main Apr 8, 2025
25 checks passed
@anangl anangl deleted the nrf_vpr_improvements branch April 8, 2025 14:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: RISCV RISCV Architecture (32-bit & 64-bit) platform: nRF Nordic nRFx
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants