Skip to content
Snippets Groups Projects
Select Git revision
  • master default protected
  • fix/macos-meta-files-in-menu
  • koalo/bhi160
  • genofire/ble-rewrite
  • rahix/simple_menu
  • ch3/splashscreen
  • koalo/bhi160-works-but-dirty
  • ios-workarounds
  • koalo/wip/i2c-for-python
  • renze/safe_mode
  • renze/hatchery_apps
  • schneider/fundamental-test
  • koalo/factory-reset
  • msgctl/gfx_rle
  • msgctl/faultscreen
  • msgctl/textbuffer_api
  • schneider/bonding
  • schneider/bootloader-update-9a0d158
  • schneider/bsec
  • rahix/bma
  • v1.12
  • v1.11
  • v1.10
  • v1.9
  • v1.8
  • v1.7
  • v1.6
  • v1.5
  • v1.4
  • v1.3
  • v1.2
  • v1.1
  • v1.0
  • release-1
  • bootloader-v1
  • v0.0
36 results

interrupts.c

Blame
  • Forked from card10 / firmware
    Source project has a limited visibility.
    • rahix's avatar
      79a0d3d5
      feat(interrupts): Dispatch interrupts asynchroneously · 79a0d3d5
      rahix authored
      
      Instead of blocking the triggering task when core 1 is still busy
      handling the previous interrupt, offload interrupt dispatching into
      a separate task.  This is the first step towards making API-calls
      interrupt safe.
      
      Next to the async triggering, the synchroneous mechanism is retained for
      special cases where async does not work (e.g. because of spin-locks).
      Currently, there is only one such case when resetting core 1 (triggering
      EPIC_INT_RESET).
      
      Signed-off-by: default avatarRahix <rahix@rahix.de>
      79a0d3d5
      History
      feat(interrupts): Dispatch interrupts asynchroneously
      rahix authored
      
      Instead of blocking the triggering task when core 1 is still busy
      handling the previous interrupt, offload interrupt dispatching into
      a separate task.  This is the first step towards making API-calls
      interrupt safe.
      
      Next to the async triggering, the synchroneous mechanism is retained for
      special cases where async does not work (e.g. because of spin-locks).
      Currently, there is only one such case when resetting core 1 (triggering
      EPIC_INT_RESET).
      
      Signed-off-by: default avatarRahix <rahix@rahix.de>