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

driver/dma_smartbond: Fix driver initialization when PM_DEVICE is set #81085

Conversation

ydamigos
Copy link
Collaborator

@ydamigos ydamigos commented Nov 7, 2024

Fix DMA driver initialization when PM_DEVICE is set.
Don't put PM policy state lock if it is not active.

Fixes #81083

Fix DMA driver initialization when PM_DEVICE is set.
Don't put PM policy state lock if it is not active.

Signed-off-by: Ioannis Damigos <[email protected]>
@zephyrbot zephyrbot added area: DMA Direct Memory Access platform: Renesas SmartBond Renesas Electronics Corporation, SmartBond labels Nov 7, 2024
@ydamigos ydamigos added bug The issue is a bug, or the PR is fixing a bug backport v3.7-branch Request backport to the v3.7-branch labels Nov 7, 2024
@ioannis-karachalios ioannis-karachalios added this to the v4.0.0 milestone Nov 10, 2024
@dkalowsk dkalowsk modified the milestones: v4.0.0, v4.1.0 Nov 12, 2024
@dkalowsk
Copy link
Contributor

Moving to 4.1.0 milestone given that RC3 is here. If you feel this really needs to be in 4.0 add the backport label

@mmahadevan108 mmahadevan108 merged commit 135214d into zephyrproject-rtos:main Nov 12, 2024
32 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: DMA Direct Memory Access backport v3.7-branch Request backport to the v3.7-branch bug The issue is a bug, or the PR is fixing a bug platform: Renesas SmartBond Renesas Electronics Corporation, SmartBond
Projects
None yet
Development

Successfully merging this pull request may close these issues.

DA1469x dma driver initialization fails
7 participants