| /trusted-firmware-a/plat/hisilicon/hikey/ |
| A D | hisi_ipc.c | 77 void hisi_ipc_spin_lock(unsigned int signal) in hisi_ipc_spin_lock() argument
81 if (signal >= HISI_IPC_INT_SRC_NUM) in hisi_ipc_spin_lock()
85 hs_ctrl = mmio_read_32(HISI_IPC_ACPU_CTRL(signal)); in hisi_ipc_spin_lock()
89 void hisi_ipc_spin_unlock(unsigned int signal) in hisi_ipc_spin_unlock() argument
91 if (signal >= HISI_IPC_INT_SRC_NUM) in hisi_ipc_spin_unlock()
94 mmio_write_32(HISI_IPC_ACPU_CTRL(signal), 0); in hisi_ipc_spin_unlock()
|
| /trusted-firmware-a/plat/hisilicon/hikey/include/ |
| A D | hisi_ipc.h | 35 void hisi_ipc_spin_lock(unsigned int signal);
36 void hisi_ipc_spin_unlock(unsigned int signal);
|
| /trusted-firmware-a/docs/design/ |
| A D | interrupt-framework-design.rst | 169 Mapping of interrupt type to signal
174 FIQ or IRQ signal to the CPU depending upon the current security state. The
182 FIQ signal while Non-secure interrupts are signaled through the IRQ signal.
185 Effect of mapping of several interrupt types to one signal argument
189 interrupt signal, and if any one of the interrupt type sets **TEL3=1** for a
190 particular security state, then interrupt signal will be routed to EL3 when in
197 signal. So if either one of the interrupt type sets the routing model so
199 route the FIQ signal to EL3 when executing in Secure-EL1/Secure-EL0, thereby
524 the FIQ signal is used to generate Secure-EL1 interrupts and the IRQ signal
799 signal completion of interrupt handling.
[all …]
|
| /trusted-firmware-a/docs/build/TF-A_2.5/_sources/design/ |
| A D | interrupt-framework-design.rst.txt | 169 Mapping of interrupt type to signal
174 FIQ or IRQ signal to the CPU depending upon the current security state. The
182 FIQ signal while Non-secure interrupts are signaled through the IRQ signal.
185 Effect of mapping of several interrupt types to one signal
189 interrupt signal, and if any one of the interrupt type sets **TEL3=1** for a
190 particular security state, then interrupt signal will be routed to EL3 when in
197 signal. So if either one of the interrupt type sets the routing model so
199 route the FIQ signal to EL3 when executing in Secure-EL1/Secure-EL0, thereby
524 the FIQ signal is used to generate Secure-EL1 interrupts and the IRQ signal
799 signal completion of interrupt handling.
[all …]
|
| /trusted-firmware-a/docs/components/ |
| A D | secure-partition-manager.rst | 600 endpoint to signal another for service provision, without hindering its current
616 A sender can signal notifications once the receiver has provided it with
806 Pair of interfaces to manage permissions to signal notifications. Prior to
807 handling notifications, an FF-A endpoint must allow a given sender to signal a
946 how to signal start and completion of secure interrupt handling as discussed in
955 either the FFA_INTERRUPT interface with ERET conduit or vIRQ signal for signaling
965 | | vIRQ | Interrupt ID | interrupt. It pends vIRQ signal and |
970 | | vIRQ | | is pending. It pends vIRQ signal and |
974 | PREEMPTED | vIRQ | NA | SPMC pends the vIRQ signal but does |
977 | RUNNING | ERET, | NA | SPMC pends the vIRQ signal and resumes|
[all …]
|
| A D | secure-partition-manager-mm.rst | 285 instruction to signal completion of the request. Some example use cases are
387 ``MM_SP_EVENT_COMPLETE_AARCH64`` call (described later) to signal readiness for
507 was made to signal either completion of Secure Partition initialisation or
587 A Secure Partition must only call ``MM_SP_EVENT_COMPLETE_AARCH64`` to signal
796 signal that it is initialised and ready to receive run-time requests.
|
| A D | ras.rst | 145 RAS nodes can signal errors to the PE by raising Fault Handling and/or Error
|
| A D | sdei.rst | 76 macro takes only one parameter: an SGI number to signal other PEs.
|
| A D | exception-handling.rst | 36 components of the system may use one of the asynchronous exceptions to signal
|
| /trusted-firmware-a/docs/build/TF-A_2.5/_sources/components/ |
| A D | secure-partition-manager.rst.txt | 600 endpoint to signal another for service provision, without hindering its current
616 A sender can signal notifications once the receiver has provided it with
806 Pair of interfaces to manage permissions to signal notifications. Prior to
807 handling notifications, an FF-A endpoint must allow a given sender to signal a
946 how to signal start and completion of secure interrupt handling as discussed in
955 either the FFA_INTERRUPT interface with ERET conduit or vIRQ signal for signaling
965 | | vIRQ | Interrupt ID | interrupt. It pends vIRQ signal and |
970 | | vIRQ | | is pending. It pends vIRQ signal and |
974 | PREEMPTED | vIRQ | NA | SPMC pends the vIRQ signal but does |
977 | RUNNING | ERET, | NA | SPMC pends the vIRQ signal and resumes|
[all …]
|
| A D | secure-partition-manager-mm.rst.txt | 285 instruction to signal completion of the request. Some example use cases are
387 ``MM_SP_EVENT_COMPLETE_AARCH64`` call (described later) to signal readiness for
507 was made to signal either completion of Secure Partition initialisation or
587 A Secure Partition must only call ``MM_SP_EVENT_COMPLETE_AARCH64`` to signal
796 signal that it is initialised and ready to receive run-time requests.
|
| A D | ras.rst.txt | 145 RAS nodes can signal errors to the PE by raising Fault Handling and/or Error
|
| A D | sdei.rst.txt | 76 macro takes only one parameter: an SGI number to signal other PEs.
|
| A D | exception-handling.rst.txt | 36 components of the system may use one of the asynchronous exceptions to signal
|
| /trusted-firmware-a/docs/build/TF-A_2.5/ |
| A D | searchindex.js | 1 …signal:[11,23,24,27,29,38,53,137,142],signatur:[6,11,27,36,38,43,47,56,67,68,142],signed:6,signifi…
|
| /trusted-firmware-a/docs/build/latex/ |
| A D | trustedfirmware-a.tex | 17818 macro takes only one parameter: an SGI number to signal other PEs.
20172 interrupt. It pends vIRQ signal and
20189 is pending. It pends vIRQ signal and
20204 SPMC pends the vIRQ signal but does
20219 SPMC pends the vIRQ signal and resumes
31011 \subsubsection{Mapping of interrupt type to signal}
31024 FIQ signal while Non\sphinxhyphen{}secure interrupts are signaled through the IRQ signal.
31028 \paragraph{Effect of mapping of several interrupt types to one signal}
31451 the FIQ signal is used to generate Secure\sphinxhyphen{}EL1 interrupts and the IRQ signal
31820 signal completion of interrupt handling.
[all …]
|
| /trusted-firmware-a/docs/getting_started/ |
| A D | porting-guide.rst | 2668 the platform IC uses to signal each type of interrupt supported by the framework
|
| /trusted-firmware-a/docs/build/TF-A_2.5/_sources/getting_started/ |
| A D | porting-guide.rst.txt | 2668 the platform IC uses to signal each type of interrupt supported by the framework
|
| /trusted-firmware-a/docs/build/TF-A_2.5/_static/css/ |
| A D | theme.css | 4 ….fa-search-minus:before{content:""}.fa-power-off:before{content:""}.fa-signal:before{content:""…
|