-
Notifications
You must be signed in to change notification settings - Fork 14
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
feat: janky way of having tracing in ISRs #132
Conversation
; Conflicts: ; platforms/allwinner-d1/core/src/drivers/twi.rs
✅ Deploy Preview for merry-scone-cc7a60 ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
@@ -234,8 +234,10 @@ impl D1 { | |||
/// At the moment, we only service the Channel 0 interrupt, | |||
/// which indicates that the serial transmission is complete. | |||
fn handle_dmac() { | |||
let _isr = kernel::isr::Isr::enter(); |
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.
We could potentially do this at the top of the actual ISR entry point instead of in every handler
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.
done!
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.
shipit.swf
This is not that good but it allows at least one ISR to trace even if
the interrupt fired while normal code was holding the trace WGR. We can
probably figure out a nicer version of this, with different tracebufs
for each ISR priority level, later.
Cherry-picked out of #103