ddi_mem_getll(9f)

1ddi_mem_get8(9F)         Kernel Functions for Drivers         ddi_mem_get8(9F)
2
3
4

NAME

6       ddi_mem_get8,      ddi_mem_get16,     ddi_mem_get32,     ddi_mem_get64,
7       ddi_mem_getb, ddi_mem_getl, ddi_mem_getll,  ddi_mem_getw  -  read  data
8       from mapped device in the memory space or allocated DMA memory
9

SYNOPSIS

11       #include <sys/ddi.h>
12       #include <sys/sunddi.h>
13
14
15
16       uint8_t ddi_mem_get8(ddi_acc_handle_t handle, uint8_t *dev_addr);
17
18
19       uint16_t ddi_mem_get16(ddi_acc_handle_t handle, uint16_t * dev_addr);
20
21
22       uint32_t ddi_mem_get32(ddi_acc_handle_t handle, uint32_t *dev_addr);
23
24
25       uint64_t ddi_mem_get64(ddi_acc_handle_t handle, uint64_t *dev_addr);
26
27

INTERFACE LEVEL

29       Solaris    DDI    specific    (Solaris    DDI).   The   ddi_mem_get8(),
30       ddi_mem_get16(),  ddi_mem_get32(),   ddi_mem_get64(),   ddi_mem_getb(),
31       ddi_mem_getl(), ddi_mem_getll(), and ddi_mem_getw() functions are obso‐
32       lete.  The   ddi_get8(9F)   function   replaces   ddi_mem_get8().   The
33       ddi_get16(9F)  function  replaces  ddi_mem_get16().  The  ddi_get32(9F)
34       function replaces ddi_mem_get32(). The ddi_get64(9F) function  replaces
35       ddi_mem_get64(). The ddi_get8(9F) function replaces ddi_mem_getb(). The
36       ddi_get32(9F) function replaces ddi_mem_getl(). The ddi_get64(9F) func‐
37       tion  replaces  ddi_mem_getll().  The  ddi_get16(9F)  function replaces
38       ddi_mem_getw().
39

PARAMETERS

41       handle      The data access handle returned from setup calls,  such  as
42                   ddi_regs_map_setup(9F).
43
44
45       dev_addr    Base device address.
46
47

DESCRIPTION

49       These  routines  generate  a read of various sizes from memory space or
50       allocated    DMA   memory.   The    ddi_mem_get8(),    ddi_mem_get16(),
51       ddi_mem_get32(), and ddi_mem_get64() functions read 8 bits, 16 bits, 32
52       bits and 64 bits  of  data,  respectively,  from  the  device  address,
53       dev_addr, in memory space.
54
55
56       Each  individual  datum  will automatically be translated to maintain a
57       consistent view between the host and the device based  on  the  encoded
58       information  in  the  data  access  handle. The translation may involve
59       byte-swapping if the host and the device have incompatible endian char‐
60       acteristics.
61

CONTEXT

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

ATTRIBUTES

66       See attributes(5) for descriptions of the following attributes:
67
68
69
70
71       ┌─────────────────────────────┬─────────────────────────────┐
72       │      ATTRIBUTE TYPE         │      ATTRIBUTE VALUE        │
73       ├─────────────────────────────┼─────────────────────────────┤
74       │Interface Stability          │Obsolete                     │
75       └─────────────────────────────┴─────────────────────────────┘
76