class WireSyncClientImpl

Allocates 88 bytes of message buffer on the stack. No heap allocation necessary.

Allocates 48 bytes of message buffer on the stack. No heap allocation necessary.

Allocates 48 bytes of message buffer on the stack. No heap allocation necessary.

Returns the value of the I/O Ready bit for this function in CCCR.

Allocates 48 bytes of message buffer on the stack. No heap allocation necessary.

Allocates 48 bytes of message buffer on the stack. No heap allocation necessary.

Allocates 48 bytes of message buffer on the stack. No heap allocation necessary.

Allocates 56 bytes of message buffer on the stack. No heap allocation necessary.

Allocates 48 bytes of message buffer on the stack. No heap allocation necessary.

Reads a byte from a register. If `suppress_error_messages` is true, the SDMMC stack will not

log error-severity messages.

Allocates 56 bytes of message buffer on the stack. No heap allocation necessary.

Writes a byte to a register. If `read_after_write` is true, the register is read after

writing and the value is returned, otherwise the original value is returned. If

`suppress_error_messages` is true, the write is expected to fail, and the SDMMC stack will

not log error-severity messages.

Allocates 56 bytes of message buffer on the stack. No heap allocation necessary.

Returns a virtual interrupt that will be triggered by the SDIO driver when the card signals

an interrupt corresponding to this function. No additional interrupts will be triggered

until `AckInBandIntr()` is called.

Allocates 48 bytes of message buffer on the stack. No heap allocation necessary.

See above. Clients should call `AckInBandIntr()` after starting to wait on the interrupt

object just in case there is already an in-band interrupt pending for this function.

Allocates 32 bytes of message buffer on the stack. No heap allocation necessary.

The following functions access the card common control registers (CCCR) on function 0.

Aborts an I/O operation occurring on the specified function.

Allocates 48 bytes of message buffer on the stack. No heap allocation necessary.

Returns true if an interrupt is pending for function fn_idx, false otherwise.

Allocates 48 bytes of message buffer on the stack. No heap allocation necessary.

Reads or writes to a vendor CCCR register. addr must be in [0xF0, 0xFF].

Allocates 56 bytes of message buffer on the stack. No heap allocation necessary.

Allocates 80 bytes of message buffer on the stack. No heap allocation necessary.

Allocates 56 bytes of message buffer on the stack. No heap allocation necessary.

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 DoRwTxn 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.

Allocates 32 bytes of response buffer on the stack. Request is heap-allocated.

Requests that the core driver hard reset the card and perform the SDIO initialization

sequence again. The callback will be called after the card has been re-initialized, and in

the meantime all IO calls from this client will return ZX_ERR_SHOULD_WAIT. If an error

occurs during initialization then all subsequent IO calls will return ZX_ERR_IO_NOT_PRESENT.

The only way to recover from this situation would be to call `RequestCardReset()` again.

The SDIO core driver will wait for all clients to call this method before performing the

reset and re-initialization. After the reset clients will have to perform their own

initialization steps again, such as calling `EnableFnIntr()` or `UpdateBlockSize()`.

VMO registration methods can always be called regardless of the reset state.

The specific method used to hard reset the card is platform- or board-specific; examples

include toggling a reset GPIO or power cycling the card.

Allocates 48 bytes of message buffer on the stack. No heap allocation necessary.

Perform tuning in the background. Clients can use this to update the host controller delay

settings in case the bus delay has changed due to temperature or other factors. For example,

clients could call this periodically, or only in response to data CRC errors. The amount of

time this call takes (and the amount of time that other requests are blocked for) is

controller-dependent.

Returns `ZX_ERR_ALREADY_BOUND` if another call to `PerformTuning()` is already pending.

Otherwise returns `ZX_OK` or an error value if the SDMMC driver's tuning process failed (see

the [SDMMC protocol](/sdk/banjo/fuchsia.hardware.sdmmc/sdmmc.fidl)).

Allocates 48 bytes of message buffer on the stack. No heap allocation necessary.