class Completion
Defined at line 488 of file fidling/gen/sdk/fidl/fuchsia.hardware.usb.endpoint/fuchsia.hardware.usb.endpoint/cpp/fidl/fuchsia.hardware.usb.endpoint/cpp/natural_types.h
Completion
Public Methods
void Completion (Storage_ storage)void Completion ()Defined at line 494 of file fidling/gen/sdk/fidl/fuchsia.hardware.usb.endpoint/fuchsia.hardware.usb.endpoint/cpp/fidl/fuchsia.hardware.usb.endpoint/cpp/natural_types.h
void Completion (Completion && )Defined at line 495 of file fidling/gen/sdk/fidl/fuchsia.hardware.usb.endpoint/fuchsia.hardware.usb.endpoint/cpp/fidl/fuchsia.hardware.usb.endpoint/cpp/natural_types.h
bool IsEmpty ()Completion & operator= (Completion && )Defined at line 496 of file fidling/gen/sdk/fidl/fuchsia.hardware.usb.endpoint/fuchsia.hardware.usb.endpoint/cpp/fidl/fuchsia.hardware.usb.endpoint/cpp/natural_types.h
const std::optional< ::fuchsia_hardware_usb_request::Request> & request ()Request completed.
::std::optional< ::fuchsia_hardware_usb_request::Request> & request ()Request completed.
Completion & request (std::optional< ::fuchsia_hardware_usb_request::Request> value)Request completed.
const std::optional<int32_t> & status ()Completion status. Common return status codes include:
- `ZX_OK`: Success.
- `ZX_ERR_NOT_SUPPORTED`: The requested operation or feature is unsupported (e.g. the
request requires scatter-gather on an endpoint where `supports_scatter_gather` is
false, such as spanning non-contiguous physical pages or multiple buffer regions).
- `ZX_ERR_IO_NOT_PRESENT`: The device is no longer present (e.g. physically
disconnected or powered off). When received, callers should terminate
transfer loops without re-queuing.
- `ZX_ERR_INVALID_ARGS`: Invalid request parameters.
- `ZX_ERR_BAD_STATE`: Driver is in an invalid state.
- `ZX_ERR_IO_REFUSED`: The device or controller refused or halted the
transfer (e.g. the endpoint was halted/stalled by host
`SET_FEATURE(ENDPOINT_HALT)` or hardware transfer abort). Buffers may be
re-queued/recycled once the halt condition is cleared.
- `ZX_ERR_CANCELED`: The transfer was explicitly canceled by client software
(e.g. via `CancelAll`).
- `ZX_ERR_NO_MEMORY`: Memory allocation failed.
- `ZX_ERR_INTERNAL`: Internal driver error.
- `ZX_ERR_IO_MISSED_DEADLINE`: The transfer missed its deadline.
- `ZX_ERR_IO`: General I/O error.
- `ZX_ERR_IO_INVALID`: Invalid I/O operation.
::std::optional<int32_t> & status ()Completion status. Common return status codes include:
- `ZX_OK`: Success.
- `ZX_ERR_NOT_SUPPORTED`: The requested operation or feature is unsupported (e.g. the
request requires scatter-gather on an endpoint where `supports_scatter_gather` is
false, such as spanning non-contiguous physical pages or multiple buffer regions).
- `ZX_ERR_IO_NOT_PRESENT`: The device is no longer present (e.g. physically
disconnected or powered off). When received, callers should terminate
transfer loops without re-queuing.
- `ZX_ERR_INVALID_ARGS`: Invalid request parameters.
- `ZX_ERR_BAD_STATE`: Driver is in an invalid state.
- `ZX_ERR_IO_REFUSED`: The device or controller refused or halted the
transfer (e.g. the endpoint was halted/stalled by host
`SET_FEATURE(ENDPOINT_HALT)` or hardware transfer abort). Buffers may be
re-queued/recycled once the halt condition is cleared.
- `ZX_ERR_CANCELED`: The transfer was explicitly canceled by client software
(e.g. via `CancelAll`).
- `ZX_ERR_NO_MEMORY`: Memory allocation failed.
- `ZX_ERR_INTERNAL`: Internal driver error.
- `ZX_ERR_IO_MISSED_DEADLINE`: The transfer missed its deadline.
- `ZX_ERR_IO`: General I/O error.
- `ZX_ERR_IO_INVALID`: Invalid I/O operation.
Completion & status (std::optional<int32_t> value)Completion status. Common return status codes include:
- `ZX_OK`: Success.
- `ZX_ERR_NOT_SUPPORTED`: The requested operation or feature is unsupported (e.g. the
request requires scatter-gather on an endpoint where `supports_scatter_gather` is
false, such as spanning non-contiguous physical pages or multiple buffer regions).
- `ZX_ERR_IO_NOT_PRESENT`: The device is no longer present (e.g. physically
disconnected or powered off). When received, callers should terminate
transfer loops without re-queuing.
- `ZX_ERR_INVALID_ARGS`: Invalid request parameters.
- `ZX_ERR_BAD_STATE`: Driver is in an invalid state.
- `ZX_ERR_IO_REFUSED`: The device or controller refused or halted the
transfer (e.g. the endpoint was halted/stalled by host
`SET_FEATURE(ENDPOINT_HALT)` or hardware transfer abort). Buffers may be
re-queued/recycled once the halt condition is cleared.
- `ZX_ERR_CANCELED`: The transfer was explicitly canceled by client software
(e.g. via `CancelAll`).
- `ZX_ERR_NO_MEMORY`: Memory allocation failed.
- `ZX_ERR_INTERNAL`: Internal driver error.
- `ZX_ERR_IO_MISSED_DEADLINE`: The transfer missed its deadline.
- `ZX_ERR_IO`: General I/O error.
- `ZX_ERR_IO_INVALID`: Invalid I/O operation.
const std::optional<uint64_t> & transfer_size ()Bytes successfully transferred.
::std::optional<uint64_t> & transfer_size ()Bytes successfully transferred.
Completion & transfer_size (std::optional<uint64_t> value)Bytes successfully transferred.
const std::optional< ::zx::eventpair> & wake_lease ()Wake lease if this completion took the system out of suspend.
::std::optional< ::zx::eventpair> & wake_lease ()Wake lease if this completion took the system out of suspend.
Completion & wake_lease (std::optional< ::zx::eventpair> value)Wake lease if this completion took the system out of suspend.
void Completion (::fidl::internal::DefaultConstructPossiblyInvalidObjectTag )Friends
class MemberVisitorclass NaturalTableCodingTraits