Searched refs:receive (Results 1 – 14 of 14) sorted by relevance
14 can receive notification emails for these by watching the "Trusted Firmware-A"
28 API is likely to receive much greater scrutiny than a local change to a
110 - Bit[0]: partition can receive direct requests if set112 - Bit[2]: partition can send and receive indirect messages
87 ``id``. PEs in the system are expected to receive only enabled interrupts.102 ``id``. PEs in the system are not expected to receive disabled interrupts.
11 Non-secure world to register handlers with firmware to receive notifications12 about system events. Firmware will first receive the system events by way of
555 receive a direct message request originating from any physical core targeting825 receive buffers described by their IPAs to the SP EL1&0 Stage-2 translation894 - An SP can receive a direct request from another SP.918 it won't be able to bind notifications, hence forbidding it to receive any1316 These devices are dependent on PE endpoint to initiate and receive memory
166 interrupts into distinct priority levels. A dispatcher that chooses to receive
796 signal that it is initialised and ready to receive run-time requests.
261 | | the latter in not in a state to receive it (e.g. a |619 | | intended to receive notifications from SPs. Thus |657 | | state such that a partition isn't able to receive |722 | | Also, receivers that are not meant to receive |
553 RCAR_DVFS_API(receive, uint8_t slave, uint8_t reg, uint8_t *data) in RCAR_DVFS_API() argument
152 receive parameters in registers depending on their actual boot sequence. On
230 BL1 does not expect to receive any exceptions other than the SMC exception.231 For the latter, BL1 installs a simple stub. The stub expects to receive a494 #. BL2 does not receive the meminfo information from BL1 anymore. This
2235 Should a PE receive an interrupt that was bound to an |SDEI| event while the
2681 - Fixed bug in SDEI receive event of RAS handler
