class Request

Defined at line 266 of file fidling/gen/sdk/fidl/fuchsia.hardware.sdmmc/fuchsia.hardware.sdmmc/cpp/fidl/fuchsia.hardware.sdmmc/cpp/markers.h

Perform the requests in order, atomically (i.e., no intervening requests). Furthermore,

calls are replied to in the order they are received. If an error occurs, abort any remaining

requests. Else, return the response of the last request.

The protocol implementation chooses whether or not to use DMA

depending on the properties of the request and the capabilities of the controller.

Clients are responsible for performing the following cache operations:

After read requests:

- Call zx_cache_flush with ZX_CACHE_FLUSH_DATA | ZX_CACHE_FLUSH_INVALIDATE on buffers that

have been mapped by the client.

- Call zx_vmo_op_range with ZX_VMO_OP_CACHE_CLEAN_INVALIDATE on all other buffers.

Note that writing to any portion of a buffer before Request has returned can corrupt the

received data.

Before write requests:

- Call zx_cache_flush with ZX_CACHE_FLUSH_DATA on buffers that have been mapped by the

client.

- Call zx_vmo_op_range with ZX_VMO_OP_CACHE_CLEAN on all other buffers.

Public Members

static const bool kHasClientToServer

static const bool kHasClientToServerBody

static const bool kHasServerToClient

static const bool kHasServerToClientBody

static const bool kHasNonEmptyUserFacingResponse

static const bool kHasDomainError

static const bool kHasFrameworkError

static const uint64_t kOrdinal