| /trusted-firmware-a/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 …]
|
| /trusted-firmware-a/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()
|
| /trusted-firmware-a/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 | secure-partition-manager.rst | 538 It is possible for an SP to call into another SP through a direct request
711 The request made by an Hypervisor or OS kernel is forwarded to the SPMC and
735 - from Hypervisor or OS kernel to SPMC. The request is relayed by the SPMD.
769 An SP sending a direct message request must have bit 15 set in its origin
786 - An SP can send a direct request to another SP.
787 - An SP can receive a direct request from another SP.
789 - An SP cannot send a direct request to an Hypervisor or OS kernel.
790 - An Hypervisor or OS kernel can send a direct request to an SP.
872 Using those IDs in source/destination fields of a direct request/response
875 - SPMC to SPMD direct request/response uses SMC conduit.
[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
|
| /trusted-firmware-a/docs/build/TF-A_2.5/_sources/components/ |
| A D | secure-partition-manager-mm.rst.txt | 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 | secure-partition-manager.rst.txt | 538 It is possible for an SP to call into another SP through a direct request
711 The request made by an Hypervisor or OS kernel is forwarded to the SPMC and
735 - from Hypervisor or OS kernel to SPMC. The request is relayed by the SPMD.
769 An SP sending a direct message request must have bit 15 set in its origin
786 - An SP can send a direct request to another SP.
787 - An SP can receive a direct request from another SP.
789 - An SP cannot send a direct request to an Hypervisor or OS kernel.
790 - An Hypervisor or OS kernel can send a direct request to an SP.
872 Using those IDs in source/destination fields of a direct request/response
875 - SPMC to SPMD direct request/response uses SMC conduit.
[all …]
|
| A D | arm-sip-service.rst.txt | 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.txt | 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.txt | 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
|
| /trusted-firmware-a/plat/arm/board/fvp/fdts/ |
| A D | optee_sp_manifest.dts | 28 messaging-method = <0x3>; /* Direct request/response supported. */
|
| /trusted-firmware-a/docs/build/TF-A_2.5/_sources/threat_model/ |
| A D | threat_model_spm.rst.txt | 76 | ``DF4`` | SP to SP FF-A direct message request/response. |
79 | | (SP1 performs a direct message request to the |
166 | | FF-A ID in a direct request/response invocation.** |
191 | | request/response interfaces such an endpoint cannot|
197 | | request/response filtering. |
201 | | sends a direct request to which SWd endpoint ID). |
261 | | SP sends a direct request to the normal world early|
452 | | request such that it reveals the internal state of |
580 | | is unable to request services from another |
|
| /trusted-firmware-a/docs/threat_model/ |
| A D | threat_model_spm.rst | 76 | ``DF4`` | SP to SP FF-A direct message request/response. |
79 | | (SP1 performs a direct message request to the |
166 | | FF-A ID in a direct request/response invocation.** |
191 | | request/response interfaces such an endpoint cannot|
197 | | request/response filtering. |
201 | | sends a direct request to which SWd endpoint ID). |
261 | | SP sends a direct request to the normal world early|
452 | | request such that it reveals the internal state of |
580 | | is unable to request services from another |
|
| /trusted-firmware-a/drivers/st/i2c/ |
| A D | stm32_i2c.c | 406 uint32_t request) in i2c_transfer_config() argument
412 (I2C_CR2_RD_WRN & (request >> (31U - I2C_CR2_RD_WRN_OFFSET))); in i2c_transfer_config()
416 i2c_mode | request; in i2c_transfer_config()
|
| /trusted-firmware-a/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.
|
| /trusted-firmware-a/docs/build/TF-A_2.5/_sources/security_advisories/ |
| A D | security-advisory-tfv-5.rst.txt | 50 NOTE: The original pull request referenced above only fixed the issue for S-EL1
|
| A D | security-advisory-tfv-8.rst.txt | 55 request (or asynchronous exception to EL3) that used these return values.
|
| /trusted-firmware-a/docs/build/TF-A_2.5/_sources/getting_started/ |
| A D | rt-svc-writers-guide.rst.txt | 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:
|
| /trusted-firmware-a/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:
|
| /trusted-firmware-a/docs/build/TF-A_2.5/_sources/plat/marvell/armada/ |
| A D | porting.rst.txt | 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
|
| /trusted-firmware-a/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
|
| /trusted-firmware-a/include/drivers/ |
| A D | usb_device.h | 250 struct usb_setup_req request; member
|