Skip to content
Snippets Groups Projects
Select Git revision
  • schneider/ir
  • master default protected
  • rahix/user-space-ctx
  • schneider/iaq-python
  • schneider/ble-mini-demo
  • schneider/ble-ecg-stream-visu
  • schneider/mp-exception-print
  • schneider/sleep-display
  • schneider/deepsleep4
  • schneider/deepsleep2
  • schneider/deepsleep
  • schneider/ble-central
  • rahix/bluetooth-app-favorite
  • schneider/v1.17-changelog
  • schneider/ancs
  • schneider/png
  • schneider/freertos-list-debug
  • schneider/212-reset-hardware-when-entering-repl
  • schneider/bonding-fail-if-full
  • schneider/ble-fixes-2020-3
  • v1.18
  • v1.17
  • v1.16
  • v1.15
  • v1.14
  • v1.13
  • 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
40 results

caller.c

  • rahix's avatar
    92741109
    feat(api-caller): Hard-disable all IRQs during API calls · 92741109
    rahix authored
    Disable all maskable interrupts on core 1 during API calls.  This brings
    two main advantages:
    
    1. It means API calls are now always ISR-safe and can be used everywhere
       in core 1 code.  This is mostly interesting to l0dables as Pycardium
       should not need to do this.
    
    2. It allows Epicardium to halt the clock for core 1 without fear as we
       have observed problems with doing this when core 1 is currently
       executing instructions that touch memory.  Now a synchronous call
       from core 1 will guarantee that it is currently waiting in a WFE and
       no other ISRs could be potentially running.
    92741109
    History
    feat(api-caller): Hard-disable all IRQs during API calls
    rahix authored
    Disable all maskable interrupts on core 1 during API calls.  This brings
    two main advantages:
    
    1. It means API calls are now always ISR-safe and can be used everywhere
       in core 1 code.  This is mostly interesting to l0dables as Pycardium
       should not need to do this.
    
    2. It allows Epicardium to halt the clock for core 1 without fear as we
       have observed problems with doing this when core 1 is currently
       executing instructions that touch memory.  Now a synchronous call
       from core 1 will guarantee that it is currently waiting in a WFE and
       no other ISRs could be potentially running.