Crate fidl_next_fuchsia_hardware_i2c

Modules§

compat: Compatibility shims which mimic some API surfaces of the current Rust bindings.
data_transfer
device

Device: The type corresponding to the Device protocol.
DeviceGetNameResponse
DeviceTransferRequest
DeviceTransferResponse
Service: The type corresponding to the Service service.
ServiceConnector: A strongly-typed service connector for the Service service.
Transaction: data_transfer is mandatory, and specifies whether this transaction has a read or a write transfer (see above). stop is optional, and specifies whether this transaction is terminated by a stop condition (if true) or by a repeated-start (if false or unspecified). If this transaction is the last in the list then a stop condition is generated regardless of the value of stop.
WireDataTransfer: The wire type corresponding to DataTransfer.
WireDeviceGetNameResponse: The wire type corresponding to DeviceGetNameResponse.
WireDeviceTransferRequest: The wire type corresponding to DeviceTransferRequest.
WireDeviceTransferResponse: The wire type corresponding to DeviceTransferResponse.
WireOptionalDataTransfer
WireTransaction: The wire type corresponding to Transaction.

DataTransfer: If read_size is set: This is a read transfer, and read_size bytes will be read from the target. If write_data is set: This is a write transfer, and write_data will be written to the target.

MAX_COUNT_TRANSACTIONS: The maximum number of transactions that can be specified in a call to Transfer.
MAX_I2_C_NAME_LEN: Maximum length of the I2C Channel name.
MAX_TRANSFER_SIZE: Clients should be aware of the max channel message size when using large transfers or many transactions. It is possible to generate a message that uses values less than the limits below but is still too big for the channel.