/arm-trusted-firmware-2.8.0/drivers/io/ |
A D | io_block.c | 305 request = buf->length; in block_read() 313 request = skip + left; in block_read() 314 request = (request + (block_size - 1U)) & in block_read() 317 request = ops->read(lba, buf->offset, request); in block_read() 319 if (request <= skip) { in block_read() 418 request = buf->length; in block_write() 426 request = skip + left; in block_write() 427 request = (request + (block_size - 1U)) & in block_write() 446 request = ops->read(lba, buf->offset, request); in block_write() 471 request = ops->write(lba, buf->offset, request); in block_write() [all …]
|
/arm-trusted-firmware-2.8.0/drivers/usb/ |
A D | usb_device.c | 342 struct usb_setup_req *req = &pdev->request; in usb_core_setup_stage() 352 pdev->ep0_data_len = pdev->request.length; in usb_core_setup_stage() 354 switch (pdev->request.bm_request & USB_REQ_RECIPIENT_MASK) { in usb_core_setup_stage() 356 usb_core_dev_req(pdev, &pdev->request); in usb_core_setup_stage() 360 usb_core_itf_req(pdev, &pdev->request); in usb_core_setup_stage() 366 pdev->request.bm_request & USB_REQ_RECIPIENT_MASK); in usb_core_setup_stage() 367 usb_core_set_stall(pdev, pdev->request.bm_request & USB_REQ_DIRECTION); in usb_core_setup_stage()
|
/arm-trusted-firmware-2.8.0/plat/arm/board/fvp/fdts/ |
A D | optee_sp_manifest.dts | 28 messaging-method = <0x3>; /* Direct request/response supported. */
|
/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. | 142 | | FF-A ID in a direct request/response invocation.** | 168 | | request/response interfaces such an endpoint cannot| 173 | | only to originator of request. | 180 | | FF-A ID in a direct request/response invocation.** | 202 | | request to other endpoint by implementation | 212 | | request/response filtering. | 217 | | sends a direct request to which SWd endpoint ID). | 286 | | SP sends a direct request to the normal world | 409 | | request such that it reveals the internal state of | [all …]
|
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 | 167 | | FF-A ID in a direct request/response invocation.** | 192 | | request/response interfaces such an endpoint cannot| 198 | | request/response filtering. | 202 | | sends a direct request to which SWd endpoint ID). | 262 | | SP sends a direct request to the normal world early| 451 | | request such that it reveals the internal state of | 581 | | is unable to request services from another |
|
/arm-trusted-firmware-2.8.0/docs/components/ |
A D | secure-partition-manager-mm.rst | 89 fulfil a service request. 283 A service request is initiated from the SPM through an exception return 288 - A request to initialise the Secure Partition during system boot. 290 - A request to handle a runtime service request. 297 request. 299 For instance, a request to perform privileged operations on behalf of a 321 - Indicate completion of a service request delegated by the SPM 508 completion of a partition service request. 515 Signal completion of the last SP service request. 530 or a runtime request was handled successfully. [all …]
|
A D | el3-spmc.rst | 91 These hooks are called by SPMC before the initial share request completes, 239 The request made by an Hypervisor or OS kernel is forwarded to the SPMC and 267 - from Hypervisor or OS kernel to SPMC. The request is relayed by the SPMD. 292 - A VM-to-SP direct request/response shall set the origin world to be non-secure 295 - Similarly, an SP-to-LSP direct request/response shall set the FF-A ID bit 15 298 An incoming direct message request arriving at SPMD from NWd is forwarded to 303 An SP sending a direct message request must have bit 15 set in its origin 323 - An SP can send a direct request to LSP. 325 - An SP cannot send a direct request to an Hypervisor or OS kernel. 326 - An Hypervisor or OS kernel can send a direct request to an SP or LSP. [all …]
|
A D | secure-partition-manager.rst | 639 It is possible for an SP to call into another SP through a direct request 882 An SP sending a direct message request must have bit 15 set in its origin 899 - An SP can send a direct request to another SP. 900 - An SP can receive a direct request from another SP. 902 - An SP cannot send a direct request to an Hypervisor or OS kernel. 903 - An Hypervisor or OS kernel can send a direct request to an SP. 1029 Using those IDs in source/destination fields of a direct request/response 1032 - SPMC to SPMD direct request/response uses SMC conduit. 1033 - SPMD to SPMC direct request/response uses ERET conduit. 1300 request message to SP1. Further, SP1 sends a direct request message to SP2. SP1 [all …]
|
A D | arm-sip-service.rst | 36 Exception Level (either EL2, or NS EL1 if EL2 isn't implemented) to request to 82 a specific request.
|
A D | exception-handling.rst | 43 interacts with the Runtime Firmware in order to request notification of 462 Non-secure world to request Secure services. They're broadly classified as 468 to the caller only when the Secure world has finished serving the request. 472 - *Yielding* SMCs carry the semantics of a preemptible, lower-priority request. 477 #. Secure world completes the request, and the caller would find ``SMC_OK`` 486 example), so will vary across dispatchers that handle the request.
|
A D | xlat-tables-lib-v2-design.rst | 212 the limits of these allocations ; the library will deny any mapping request that 272 library detects that there is insufficient memory to meet the request, or that 336 is a request to map (resp. unmap) a memory region, it is added to (resp. removed 364 number of translation tables created to satisfy the user's request. It will 420 dynamic mapping request is deemed legitimate, it automatically concerns memory
|
A D | firmware-update.rst | 176 is permitted to request execution of a secure world FWU image (after
|
/arm-trusted-firmware-2.8.0/drivers/st/i2c/ |
A D | stm32_i2c.c | 407 uint32_t request) in i2c_transfer_config() argument 413 (I2C_CR2_RD_WRN & (request >> (31U - I2C_CR2_RD_WRN_OFFSET))); in i2c_transfer_config() 417 i2c_mode | request; in i2c_transfer_config()
|
/arm-trusted-firmware-2.8.0/docs/security_advisories/ |
A D | security-advisory-tfv-5.rst | 50 NOTE: The original pull request referenced above only fixed the issue for S-EL1
|
A D | security-advisory-tfv-8.rst | 55 request (or asynchronous exception to EL3) that used these return values.
|
/arm-trusted-firmware-2.8.0/docs/getting_started/ |
A D | rt-svc-writers-guide.rst | 11 levels lower than EL3 will request runtime services using the Secure Monitor 14 identifiers to each SMC request and describes how arguments are passed and 196 otherwise completing the request with the *Unknown SMC Function ID*: 211 If invalid, the request should be completed with:
|
A D | psci-lib-integration-guide.rst | 11 The runtime service request is made via SMC (Secure Monitor Call) and the call
|
A D | porting-guide.rst | 34 create a pull request that moves the code to ``plat/common`` so that it can be 1638 ``BL1_SMC_RUN_IMAGE`` SMC request raised by BL2. It should be used to perform
|
/arm-trusted-firmware-2.8.0/include/drivers/ |
A D | usb_device.h | 250 struct usb_setup_req request; member
|
/arm-trusted-firmware-2.8.0/docs/plat/marvell/armada/ |
A D | porting.rst | 51 Supported options to implement the skip request are: 77 skip image request message is printed on the screen and boot rom boots from the
|
/arm-trusted-firmware-2.8.0/docs/process/ |
A D | contributing.rst | 112 send an email to the `TF-A mailing list`_ to broadcast your review request 163 :ref:`maintainers` will request your help to solve the issue. They may
|
A D | code-review-guidelines.rst | 123 to request this information.
|
/arm-trusted-firmware-2.8.0/docs/design_documents/ |
A D | measured_boot_poc.rst | 73 a kernel module to forward the request from user space to the secure world.
|
/arm-trusted-firmware-2.8.0/docs/ |
A D | change-log.md | 65 …- add interrupt handler for reboot request ([f1fe144](https://review.trustedfirmware.org/plugins/g… 324 …- avoid spoofing in FF-A direct request ([5519f07](https://review.trustedfirmware.org/plugins/giti… 1026 …- support ECDH request ([4944686](https://review.trustedfirmware.org/plugins/gitiles/TF-A/trusted-… 1033 …- support HMAC SHA-2 MAC verify request ([c05ea29](https://review.trustedfirmware.org/plugins/giti… 3510 - Implement pinctrl request/release EEMI API 4222 - xilinx: versal: Add set wakeup source, client wakeup, query data, request 5776 AArch64 to AArch32, or vice verse, via a request to EL3. 5915 shutdown request using the PSCI SYSTEM_OFF API. 6120 instead of terminating its execution in response to a shutdown request using 6255 instead of terminating its execution in response to a shutdown request using [all …]
|
/arm-trusted-firmware-2.8.0/docs/design/ |
A D | firmware-design.rst | 841 levels lower than EL3 will request runtime services using the Secure Monitor 844 identifiers to each SMC request and describes how arguments are passed and 1153 request that the exit from ``bl31_main()`` is to the BL32 entrypoint in 1430 request, determines the highest power level at which to execute power down
|