-
Notifications
You must be signed in to change notification settings - Fork 8.2k
drivers: reset: rpi_pico: wait for reset deassertion #92321
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
Conversation
7c3f9d8 to
15d0281
Compare
… deassertion Failing to do so can lead to e.g. PIO not being ready by the time a driver tries to use it. pico-sdk also does block on this register in its reset deassertion routines. Signed-off-by: Dmitrii Sharshakov <[email protected]>
No need to toggle reset line manually, use the standard reset API. This improves code searchability and aids debugging. Requires zephyrproject-rtos#92321 to make sure reset deassertion is waited for. Signed-off-by: Dmitrii Sharshakov <[email protected]>
No need to toggle reset line manually, use the standard reset API. This improves code searchability and aids debugging. Requires zephyrproject-rtos#92321 to make sure reset deassertion is waited for. Signed-off-by: Dmitrii Sharshakov <[email protected]>
No need to toggle reset line manually, use the standard reset API. This improves code searchability and aids debugging. Requires zephyrproject-rtos#92321 to make sure reset deassertion is waited for. Signed-off-by: Dmitrii Sharshakov <[email protected]>
|
@soburi @ThreeEights @ajf58 could you please take a look at this driver rewrite? |
Use HAL functions, which also wait for reset to complete. Remove unused register size and active-low DT props. Signed-off-by: Dmitrii Sharshakov <[email protected]>
|
soburi
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
ajf58
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry for taking so long to review this.
No need to toggle reset line manually, use the standard reset API. This improves code searchability and aids debugging. Requires zephyrproject-rtos#92321 to make sure reset deassertion is waited for. Signed-off-by: Dmitrii Sharshakov <[email protected]>
No need to toggle reset line manually, use the standard reset API. This improves code searchability and aids debugging. Requires zephyrproject-rtos#92321 to make sure reset deassertion is waited for. Signed-off-by: Dmitrii Sharshakov <[email protected]>
No need to toggle reset line manually, use the standard reset API. This improves code searchability and aids debugging. Requires zephyrproject-rtos#92321 to make sure reset deassertion is waited for. Signed-off-by: Dmitrii Sharshakov <[email protected]>
No need to toggle reset line manually, use the standard reset API. This improves code searchability and aids debugging. Requires zephyrproject-rtos#92321 to make sure reset deassertion is waited for. Signed-off-by: Dmitrii Sharshakov <[email protected]>
No need to toggle reset line manually, use the standard reset API. This improves code searchability and aids debugging. Requires zephyrproject-rtos#92321 to make sure reset deassertion is waited for. Signed-off-by: Dmitrii Sharshakov <[email protected]>



Failing to do so can lead to e.g. PIO not being ready by the time
a driver tries to use it.
pico-sdk also does block on this register in
its reset deassertion routines.
Signed-off-by: Dmitrii Sharshakov [email protected]