mirror of
https://github.com/tinygo-org/tinygo.git
synced 2026-09-11 06:59:31 +00:00
0d13e61d0c
Signed-off-by: deadprogram <ron@hybridgroup.com>
39 lines
1.3 KiB
Go
39 lines
1.3 KiB
Go
//go:build tinygo.riscv && !tkey
|
|
|
|
package interrupt
|
|
|
|
import "device/riscv"
|
|
|
|
// State represents the previous global interrupt state.
|
|
type State uintptr
|
|
|
|
// Disable disables all interrupts and returns the previous interrupt state. It
|
|
// can be used in a critical section like this:
|
|
//
|
|
// state := interrupt.Disable()
|
|
// // critical section
|
|
// interrupt.Restore(state)
|
|
//
|
|
// Critical sections can be nested. Make sure to call Restore in the same order
|
|
// as you called Disable (this happens naturally with the pattern above).
|
|
func Disable() (state State) {
|
|
return State(riscv.DisableInterrupts())
|
|
}
|
|
|
|
// Restore restores interrupts to what they were before. Give the previous state
|
|
// returned by Disable as a parameter. If interrupts were disabled before
|
|
// calling Disable, this will not re-enable interrupts, allowing for nested
|
|
// critical sections.
|
|
func Restore(state State) {
|
|
riscv.EnableInterrupts(uintptr(state))
|
|
}
|
|
|
|
// In returns whether the system is currently in an interrupt.
|
|
func In() bool {
|
|
// There is one exception that has the value 0 (instruction address
|
|
// misaligned), but it's not very likely and even if it happens, it's not
|
|
// really something that can be recovered from. Therefore I think it's safe
|
|
// to ignore it. It's handled specially (in handleException).
|
|
return riscv.MCAUSE.Get() != 0
|
|
}
|