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

fix: call effective ETH scheduler only from Timer callback #60

Merged
merged 1 commit into from
Mar 14, 2022

Conversation

ABOSTM
Copy link
Contributor

@ABOSTM ABOSTM commented Mar 14, 2022

fix: call effective ETH scheduler only from Timer callback

Restrict effective ETH scheduler to Timer callback only.
This is to avoid any race condition on ETH scheduler,
which could previously be called from timer ISR,
as well as DHCP or UDP driver parts.
Any direct request for ETH scheduler (direct call to stm32_eth_scheduler())
will generate a Timer Update Event to force a call to timer callback

Fixes #45

Restrict effective ETH scheduler to Timer callback only.
This is to avoid any race condition on ETH scheduler,
which could previously be called from timer ISR,
as well as  DHCP or UDP driver parts.
Any direct request for ETH scheduler (direct call to stm32_eth_scheduler())
will generate a Timer Update Event to force a call to timer callback

Fixes stm32duino#45

Signed-off-by: Alexandre Bourdiol <alexandre.bourdiol@st.com>
@ABOSTM ABOSTM requested a review from fpistm March 14, 2022 14:10
@fpistm fpistm added the enhancement New feature or request label Mar 14, 2022
@fpistm fpistm added this to the 1.2.x milestone Mar 14, 2022
@fpistm fpistm merged commit e2e0a42 into stm32duino:main Mar 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

stm32_eth_scheduler() and timer interrupt
2 participants