| /arm-trusted-firmware-2.8.0/plat/arm/board/corstone700/common/drivers/mhu/ |
| A D | corstone700_mhu.c | 64 unsigned int message) in mhu_secure_message_send() argument
91 mmio_write_32(address + CPU_INTR_S_SET, message); in mhu_secure_message_send()
|
| A D | corstone700_mhu.h | 33 unsigned int message);
|
| /arm-trusted-firmware-2.8.0/services/std_svc/spmd/ |
| A D | spmd_private.h | 68 unsigned long long message);
|
| A D | spmd_main.c | 101 unsigned long long message) in spmd_build_spmc_message() argument
108 write_ctx_reg(gpregs, CTX_GPREG_X3, message); in spmd_build_spmc_message()
|
| /arm-trusted-firmware-2.8.0/services/std_svc/spm/el3_spmc/ |
| A D | spmc_pm.c | 25 unsigned long long message, in spmc_build_pm_message() argument
35 write_ctx_reg(gpregs, CTX_GPREG_X3, message); in spmc_build_pm_message()
|
| /arm-trusted-firmware-2.8.0/docs/threat_model/ |
| A D | threat_model_el3_spm.rst | 51 | | message request to SPMC targeting LSP as destination. |
167 | implemented? | The SPMC enforces checks in the direct message |
170 | | originated message directed to the SWd cannot use a|
326 | | A malicious endpoint may replay a message exchange |
408 | Threat | **A malicious endpoint may forge a direct message |
410 | | another endpoint through the direct message |
414 | | message by a direct message response with |
416 | | (e.g. partition message response outside of |
444 | | to be revealed through a direct message response. |
|
| A D | threat_model_spm.rst | 77 | ``DF4`` | SP to SP FF-A direct message request/response. |
80 | | (SP1 performs a direct message request to the |
82 | | the direct message response from SP2 to SP1). |
191 | | The SPMC must enforce checks in the direct message |
194 | | originated message directed to the SWd cannot use a|
374 | | A malicious endpoint may replay a message exchange |
450 | ``Threat`` | **A malicious endpoint may forge a direct message |
452 | | another endpoint through the direct message |
455 | | message by a direct message response with |
457 | | (.e.g. partition message response outside of |
[all …]
|
| /arm-trusted-firmware-2.8.0/plat/mediatek/drivers/ptp3/ |
| A D | ptp3_common.c | 121 #pragma message "PSCI hint not enable"
|
| /arm-trusted-firmware-2.8.0/docs/process/ |
| A D | commit-style.rst | 10 A good commit message provides all the background information needed for
39 The following example commit message demonstrates the use of the
|
| A D | coding-guidelines.rst | 271 emitting a ``WARN`` message, performing any necessary error handling and
291 1. If the unrecoverable error is unexpected then emit an ``ERROR`` message and
295 then emit an ``ERROR`` message and call the platform-specific function
|
| A D | code-review-guidelines.rst | 201 posted via the commit message or on the mailing list.
|
| /arm-trusted-firmware-2.8.0/drivers/arm/gic/common/ |
| A D | gic_common.c | 7 #pragma message __FILE__ " is deprecated, use gicv2.mk instead"
|
| /arm-trusted-firmware-2.8.0/lib/zlib/ |
| A D | inffast.c | 12 # pragma message("Assembler code may have bugs -- use at your own risk")
|
| /arm-trusted-firmware-2.8.0/docs/components/ |
| A D | secure-partition-manager.rst | 555 receive a direct message request originating from any physical core targeting
877 An incoming direct message request arriving at SPMD from NWd is forwarded to
879 message is coming from normal world in this specific code path. Thus the origin
882 An SP sending a direct message request must have bit 15 set in its origin
885 The SPMC shall reject the direct message if the claimed world in origin endpoint
1002 An attempt from an SP to send a message to a normal world VM whose RX buffer
1010 Hafnium copies a message from the sender TX buffer into receiver's RX buffer.
1018 On a successful message send, Hafnium pends an RX buffer full framework
1019 notification for the receiver, to inform it about a message in the RX buffer.
1300 request message to SP1. Further, SP1 sends a direct request message to SP2. SP1
[all …]
|
| A D | el3-spmc.rst | 298 An incoming direct message request arriving at SPMD from NWd is forwarded to
300 message is coming from normal world in this specific code path. Thus the origin
303 An SP sending a direct message request must have bit 15 set in its origin
306 The SPMC shall reject the direct message if the claimed world in origin endpoint
|
| A D | granule-protection-tables-design.rst | 211 error message and return a negative value. The return values of APIs should be
|
| A D | xlat-tables-lib-v2-design.rst | 274 unexpected error is encountered, they will print an error message on the UART.
|
| /arm-trusted-firmware-2.8.0/plat/intel/soc/common/sip/ |
| A D | socfpga_sip_fcs.c | 439 psgsigma_teardown_msg message = { in intel_fcs_sigma_teardown() local
446 (uint32_t *) &message, sizeof(message) / MBOX_WORD_BYTE, in intel_fcs_sigma_teardown()
|
| /arm-trusted-firmware-2.8.0/docs/getting_started/ |
| A D | tools-build.rst | 68 Invoking the tool with ``help`` will print a help message with all available
|
| A D | prerequisites.rst | 93 CI for feedback on commit message conformance.
|
| A D | porting-guide.rst | 247 Defines the maximum message size between AP and RSS. Need to define if
2498 The default implementation only prints out a warning message.
3338 message, and panics.
|
| /arm-trusted-firmware-2.8.0/docs/plat/marvell/armada/ |
| A D | porting.rst | 77 skip image request message is printed on the screen and boot rom boots from the
|
| A D | build.rst | 200 an error message will be printed prior trying to reboot via the usual way.
|
| /arm-trusted-firmware-2.8.0/ |
| A D | changelog.yaml | 9 # into these top-level sections based on the commit message "type":
73 # Sub-sections have an optional associated commit message "scope":
|
| /arm-trusted-firmware-2.8.0/docs/ |
| A D | change-log.md | 105 …- add RSS-AP message size macro ([445130b](https://review.trustedfirmware.org/plugins/gitiles/TF-A…
2028 …- fix type in message ([afcdc9d](https://review.trustedfirmware.org/plugins/gitiles/TF-A/trusted-f…
2051 …- correct type in message ([bd9cd63](https://review.trustedfirmware.org/plugins/gitiles/TF-A/trust…
3471 - Fill non-message data fields in sec_proxy with 0x0
3585 - Fixed error message printing in board makefile
4448 result in the platform entering system suspend state as expected. A message
4759 result in the platform entering system suspend state as expected. A message
5156 result in the platform entering system suspend state as expected. A message
5842 - If it applies (i.e. the CPU is affected by the errata), an INFO message is
5844 - If it does not apply, a VERBOSE message is printed, confirming that the
[all …]
|