| /trusted-firmware-a-latest/drivers/io/ |
| D | io_block.c | 253 size_t request; /* number of requested bytes in one iteration */ in block_read() local
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()
333 nbytes = request - skip; in block_read()
365 size_t request; /* number of requested bytes in one iteration */ in block_write() local
418 request = buf->length; in block_write()
426 request = skip + left; in block_write()
[all …]
|
| /trusted-firmware-a-latest/plat/mediatek/include/lpm/ |
| D | mt_lp_rq.h | 24 int (*request)(struct mt_lp_resource_user *this, unsigned int resource); member
|
| /trusted-firmware-a-latest/drivers/usb/ |
| 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-latest/docs/components/ |
| D | secure-partition-manager-mm.rst | 82 fulfil a service request.
254 software to make a request for an operation implemented in privileged software.
259 and installs a simple exception vector table in S-EL1 that relays a SVC request
260 from a Secure Partition as a SMC request to the SPM in EL3. Upon servicing the
261 SMC request, Trusted Firmware-A returns control directly to S-EL0 through an
276 A service request is initiated from the SPM through an exception return
278 instruction to signal completion of the request. Some example use cases are
281 - A request to initialise the Secure Partition during system boot.
283 - A request to handle a runtime service request.
288 A request is initiated from the Secure Partition by executing a SVC instruction.
[all …]
|
| 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
320 This is a mandatory interface for secure partitions participating in direct request
323 - An SP can send a direct request to LSP.
325 - An SP cannot send a direct request to an Hypervisor or OS kernel.
[all …]
|
| D | secure-partition-manager.rst | 577 receive a direct message request originating from any physical core targeting
666 It is possible for an SP to call into another SP through a direct request
847 The request made by an Hypervisor or OS kernel is forwarded to the SPMC and
875 - from Hypervisor or OS kernel to SPMC. The request is relayed by the SPMD.
898 - A VM-to-SP direct request/response shall set the origin world to be non-secure
901 - Similarly, an SP-to-SP direct request/response shall set the FF-A ID bit 15
904 An incoming direct message request arriving at SPMD from NWd is forwarded to
909 An SP sending a direct message request must have bit 15 set in its origin
923 This is a mandatory interface for secure partitions consisting in direct request
926 - An SP can send a direct request to another SP.
[all …]
|
| 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.
|
| 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.
|
| 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
|
| D | sdei.rst | 375 client can request an invalid interrupt to be bound. This may potentially
|
| D | firmware-update.rst | 176 is permitted to request execution of a secure world FWU image (after
|
| /trusted-firmware-a-latest/plat/arm/board/fvp/fdts/ |
| D | optee_sp_manifest.dts | 28 messaging-method = <0x3>; /* Direct request/response supported. */
|
| /trusted-firmware-a-latest/docs/threat_model/ |
| D | threat_model_el3_spm.rst | 52 | | message request to SPMC targeting LSP as destination. |
144 | | FF-A ID in a direct request/response invocation.** |
170 | | request/response interfaces such an endpoint cannot|
175 | | only to originator of request. |
182 | | FF-A ID in a direct request/response invocation.** |
204 | | request to other endpoint by implementation |
214 | | request/response filtering. |
219 | | sends a direct request to which SWd endpoint ID). |
288 | | SP sends a direct request to the normal world |
411 | | request such that it reveals the internal state of |
[all …]
|
| /trusted-firmware-a-latest/plat/mediatek/common/lpm/ |
| D | mt_lp_rq.c | 105 ru->request = NULL; in mt_lp_resource_user_register()
127 ru->request = mt_lp_resource_request; in mt_lp_resource_user_register()
|
| /trusted-firmware-a-latest/docs/design_documents/ |
| D | psci_osi_mode.rst | 49 states, and may request for a topology node to enter a low-power state when
156 :retval SUCCESS: if the request is successful.
195 :retval SUCCESS: if the request is successful.
199 that is incompatible with the request.
209 In OS-initiated mode, the calling OS is making an explicit request for a
211 must comply with the request, unless the request is not consistent with the
252 state. For example, the OS might request a powerdown state for a node from one
258 * The calling OS must specify in each CPU_SUSPEND request the deepest power
263 CPU_SUSPEND request are consistent with the system's state, and that the
265 the request otherwise.
[all …]
|
| D | rss.rst | 21 in idle for the incoming request, handles them, and sends a response then goes
65 the memory, where payload data lives, while the RSS handles the request.
138 process can be requested from RSS. Furthermore, AP can request RSS to
|
| D | measured_boot_poc.rst | 75 a kernel module to forward the request from user space to the secure world.
|
| /trusted-firmware-a-latest/drivers/st/i2c/ |
| 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()
|
| /trusted-firmware-a-latest/docs/security_advisories/ |
| D | security-advisory-tfv-5.rst | 50 NOTE: The original pull request referenced above only fixed the issue for S-EL1
|
| D | security-advisory-tfv-8.rst | 55 request (or asynchronous exception to EL3) that used these return values.
|
| /trusted-firmware-a-latest/docs/getting_started/ |
| 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-latest/include/drivers/ |
| D | usb_device.h | 250 struct usb_setup_req request; member
|
| /trusted-firmware-a-latest/docs/plat/marvell/armada/ |
| 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-latest/docs/process/ |
| 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
|
| D | code-review-guidelines.rst | 152 to request this information.
|
