Skip to content

Conversation

@erwango
Copy link
Member

@erwango erwango commented Oct 7, 2019

With dual core handling introduction, we now need to take care to
always release lock before exiting function.
Rework gpio_stm32_config to take this into account.
Additionally, since ENOSYS usage is resevred to system calls
handling, replace with EIO.

Signed-off-by: Erwan Gouriou [email protected]

@erwango erwango requested review from galak and mnkp October 7, 2019 08:52
@erwango erwango requested a review from rsalveti as a code owner October 7, 2019 08:52
@erwango erwango changed the base branch from master to topic-gpio October 7, 2019 09:07
With dual core handling introduction, we now need to take care to
always release lock before exiting function.
Rework gpio_stm32_config to take this into account.
Additionally, since ENOSYS usage is resevred to system calls
handling, replace with EIO.


Signed-off-by: Erwan Gouriou <[email protected]>
@erwango erwango force-pushed the gpio_release_lock branch from 12b4de2 to bf92577 Compare October 7, 2019 09:09
@erwango erwango changed the title drivers/gpio: stm32: Rework configure function exit for dual core [topic-gpio] drivers/gpio: stm32: Rework configure function exit for dual core Oct 7, 2019
@MaureenHelm MaureenHelm merged commit 7c4821a into zephyrproject-rtos:topic-gpio Oct 7, 2019
@erwango erwango deleted the gpio_release_lock branch January 27, 2022 13:39
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.

3 participants