DDI_GET8(9F) Kernel Functions for Drivers DDI_GET8(9F)

ddi_get8, ddi_get16, ddi_get32, ddi_get64, - read data from the mapped memory address, device register or allocated DMA memory address

#include <sys/ddi.h>
#include <sys/sunddi.h>
uint8_t ddi_get8(ddi_acc_handle_t handle, uint8_t *dev_addr);

uint16_t ddi_get16(ddi_acc_handle_t handle, uint16_t *dev_addr);

uint32_t ddi_get32(ddi_acc_handle_t handle, uint32_t *dev_addr);

uint64_t ddi_get64(ddi_acc_handle_t handle, uint64_t *dev_addr);

illumos DDI specific (illumos DDI). The ddi_getb(), ddi_getl(), ddi_getll(), and ddi_getw() functions are obsolete. The ddi_get8() function replaces ddi_getb(). The ddi_get32() function replaces ddi_getl(). The ddi_get64() function replaces ddi_getll(). The ddi_get16() function replaces ddi_getw().

The data access handle returned from setup calls, such as ddi_regs_map_setup(9F).


Base device address.

The ddi_get8(), ddi_get16(), ddi_get32(), and ddi_get64() functions read 8 bits, 16 bits, 32 bits and 64 bits of data, respectively, from the device address, dev_addr.

Each individual datum will automatically be translated to maintain a consistent view between the host and the device based on the encoded information in the data access handle. The translation may involve byte-swapping if the host and the device have incompatible endian characteristics.

For certain bus types, you can call these DDI functions from a high-interrupt context. These types include ISA and SBus buses. See sysbus(5), isa(5), and sbus(5) for details. For the PCI bus, you can, under certain conditions, call these DDI functions from a high-interrupt context. See pci(5).

These functions return the value read from the mapped address.

These functions can be called from user, kernel, or interrupt context.

See attributes(7) for descriptions of the following attributes:

Interface Stability Committed

ddi_put8(9F), ddi_regs_map_free(9F), ddi_regs_map_setup(9F), ddi_rep_get8(9F), ddi_rep_put8(9F)
November 1, 2005 OmniOS