pub struct EndpointSynchronousProxy { /* private fields */ }Implementations§
Source§impl EndpointSynchronousProxy
impl EndpointSynchronousProxy
pub fn new(channel: Channel) -> Self
pub fn into_channel(self) -> Channel
Sourcepub fn wait_for_event(
&self,
deadline: MonotonicInstant,
) -> Result<EndpointEvent, Error>
pub fn wait_for_event( &self, deadline: MonotonicInstant, ) -> Result<EndpointEvent, Error>
Waits until an event arrives and returns it. It is safe for other threads to make concurrent requests while waiting for an event.
Sourcepub fn get_info(
&self,
___deadline: MonotonicInstant,
) -> Result<EndpointGetInfoResult, Error>
pub fn get_info( &self, ___deadline: MonotonicInstant, ) -> Result<EndpointGetInfoResult, Error>
Gets endpoint information
Sourcepub fn register_vmos(
&self,
vmo_ids: &[VmoInfo],
___deadline: MonotonicInstant,
) -> Result<Vec<VmoHandle>, Error>
pub fn register_vmos( &self, vmo_ids: &[VmoInfo], ___deadline: MonotonicInstant, ) -> Result<Vec<VmoHandle>, Error>
Registers and pins VMOs to the vmo_ids. Returns
- vmo: Handles to successfully registered vmo_ids. VMO IDs that are already are registered to will fail.
Sourcepub fn unregister_vmos(
&self,
vmo_ids: &[u64],
___deadline: MonotonicInstant,
) -> Result<(Vec<u64>, Vec<i32>), Error>
pub fn unregister_vmos( &self, vmo_ids: &[u64], ___deadline: MonotonicInstant, ) -> Result<(Vec<u64>, Vec<i32>), Error>
Unregisters the VMOs corresponding to the vmo_ids. Returns
- failed_vmo_ids: vmo_ids that failed to unregister.
- errors: Error values that correspond 1:1 to failed_vmo_ids above.
Sourcepub fn queue_requests(&self, req: Vec<Request>) -> Result<(), Error>
pub fn queue_requests(&self, req: Vec<Request>) -> Result<(), Error>
Submit Requests to queue. Processed starting with the 0th Request. Submitting a vector of Requests allows for pre-buffering.
Clients are responsible for cache management and ensuring cache coherency. The explanation to follow concerns VMOs that have been previously registered via RegisterVmos. The following rules must be followed:
-
After writing to VMO-backed buffers, the caller must call zx_cache_flush with ZX_CACHE_FLUSH_DATA before invoking QueueRequests, causing the hardware to DMA-process the buffer. This avoids both stale buffer data being DMA-read, and a concurrent race between the hardware and CPU to update the same addresses.
-
Before reading from VMO-backed buffers, the caller must call zx_cache_flush with ZX_CACHE_FLUSH_DATA | ZX_CACHE_FLUSH_INVALIDATE after the buffer contents have been DMA-written by the hardware. This implies a non-dirty cache (see #1 above) and ensures any subsequent CPU-reads fetch the previously DMA-written data from RAM.
Failing to adhere to these rules will result in the exchange of corrupted and/or stale data. If the VMO is not virtually mapped (uncommon), zx_vmo_op_range should be used in lieu of zx_cache_flush. If the usb::FidlRequest types are in use, they contain helpers for these operations.
Requests may be pre-buffered. In other words, requests may be queued for data that is not present/ready in the buffer yet. The USB Endpoint Server consuming requests does not care if the data in the buffer is ready or not and will always process requests on schedule. It is the responsibility of the USB Endpoint Client that submits requests to ensure that data is ready on schedule (taking into consideration cache management above).
- Definition of “on schedule” varies for different endpoints and controllers. In general,
this will be communicated by the
lead_timeparameter returned byGetInfo.
Sourcepub fn cancel_all(
&self,
___deadline: MonotonicInstant,
) -> Result<EndpointCancelAllResult, Error>
pub fn cancel_all( &self, ___deadline: MonotonicInstant, ) -> Result<EndpointCancelAllResult, Error>
Cancels all requests. Returns
- ZX_ERR_IO_NOT_PRESENT: If device is not running, disconnected, or inactive.
- ZX_ERR_IO: If cancel failed due to an unsuccessful request.
Trait Implementations§
Source§impl Debug for EndpointSynchronousProxy
impl Debug for EndpointSynchronousProxy
Source§impl From<Channel> for EndpointSynchronousProxy
Available on Fuchsia only.
impl From<Channel> for EndpointSynchronousProxy
Source§impl From<EndpointSynchronousProxy> for NullableHandle
Available on Fuchsia only.
impl From<EndpointSynchronousProxy> for NullableHandle
Source§fn from(value: EndpointSynchronousProxy) -> Self
fn from(value: EndpointSynchronousProxy) -> Self
Source§impl FromClient for EndpointSynchronousProxy
Available on Fuchsia only.
impl FromClient for EndpointSynchronousProxy
Source§type Protocol = EndpointMarker
type Protocol = EndpointMarker
Source§fn from_client(value: ClientEnd<EndpointMarker>) -> Self
fn from_client(value: ClientEnd<EndpointMarker>) -> Self
Source§impl SynchronousProxy for EndpointSynchronousProxy
Available on Fuchsia only.
impl SynchronousProxy for EndpointSynchronousProxy
Source§type Proxy = EndpointProxy
type Proxy = EndpointProxy
Source§type Protocol = EndpointMarker
type Protocol = EndpointMarker
Proxy controls.