|
|
udi_gio_bind_ack(3udi)
Acknowledge a GIO binding
#include <udi.h>void udi_gio_bind_ack ( udi_gio_bind_cb_t *cb, udi_ubit32_t device_size_lo, udi_ubit32_t device_size_hi, udi_status_t status );ARGUMENTS cb is a pointer to a GIO bind control block.
device_size_lo is the least-significant 32 bits of the (logical) device size, in bytes. This affects the behavior of standard read/write operations; its effect on custom operations, if any, is defined by the GIO provider.
device_size_hi is the next-most-significant 32 bits of the (logical) device size, in bytes. This affects the behavior of standard read/write operations; its effect on custom operations, if any, is defined by the GIO provider.
status indicates whether or not the binding was successful.
TARGET CHANNEL The target channel for this operation is the bind channel connecting a GIO provider to a GIO client.
DESCRIPTION The udi_gio_bind_ack operation is used by a Generic I/O provider to acknowledge binding with a Generic I/O client (or failure to do so, as indicated by status), as requested by a udi_gio_bind_req operation.
If device_size_lo or device_size_hi are non-zero, the standard read/write operations, UDI_GIO_OP_READ and UDI_GIO_OP_WRITE, are treated as random-access operations; that is, the offset_lo and offset_hi members of udi_gio_rw_params_t indicate the starting device offset for each transfer and transfers may be sent to the provider in any order. The client must not send any such requests that would extend beyond the end of the device as indicated by device_size_lo and device_size_hi.
If device_size_lo and device_size_hi are both zero, and the client uses standard read/write operations, then it must send them to the provider in device order, and offset_lo and offset_hi must be ignored by the provider.
WARNINGS The control block must be the same control block as passed to the driver in the corresponding udi_gio_bind_req operation.