ddi_device_zero(9f) [opensolaris man page]

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

NAME

       ddi_device_zero - zero fill the device

SYNOPSIS

       #include <sys/ddi.h>
       #include <sys/sunddi.h>

       int ddi_device_zero(ddi_acc_handle_t handle, caddr_t dev_addr,
	    size_t bytecount, ssize_t dev_advcnt, uint_t dev_datasz);

INTERFACE LEVEL

       Solaris DDI specific (Solaris DDI).

PARAMETERS

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

       dev_addr       Beginning of the device address.

       bytecount      Number of bytes to zero.

       dev_advcnt     Number of  dev_datasz units to advance on every access.

       dev_datasz     The size of each data word. Possible values are defined as:

		      DDI_DATA_SZ01_ACC     1 byte data size

		      DDI_DATA_SZ02_ACC     2 bytes data size

		      DDI_DATA_SZ04_ACC     4 bytes data size

		      DDI_DATA_SZ08_ACC     8 bytes data size

DESCRIPTION

       ddi_device_zero() function fills the given, bytecount, number of byte of zeroes to the device register or memory.

       The   dev_advcnt  argument  determines  the value of the device address,  dev_addr, on each access.  A value of	0 will use the same device
       address,  dev_addr, on every  access. A positive value increments the device address in the next access while a negative  value	decrements
       the address. The device address is incremented and decremented in  dev_datasz units.

       The dev_datasz argument determines the size of data word on each access.

RETURN VALUES

       ddi_device_zero() returns:

       DDI_SUCCESS     Successfully zeroed the data.

       DDI_FAILURE     The byte count is not a multiple of  dev_datasz.

CONTEXT

       ddi_device_zero() can be called from user, kernel, or interrupt context.

SEE ALSO

       ddi_regs_map_free(9F), ddi_regs_map_setup(9F)

       Writing Device Drivers

SunOS 5.11							    25 Sep 1996 					       ddi_device_zero(9F)

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

NAME

       ddi_rep_put8,  ddi_rep_put16,  ddi_rep_put32,  ddi_rep_put64,  ddi_rep_putb,  ddi_rep_putw, ddi_rep_putl, ddi_rep_putll - write data to the
       mapped memory address, device register or allocated DMA memory address

SYNOPSIS

       #include <sys/ddi.h>
       #include <sys/sunddi.h>

       void ddi_rep_put8(ddi_acc_handle_t handle, uint8_t *host_addr, uint8_t *dev_addr, size_t repcount, uint_t flags);

       void ddi_rep_put16(ddi_acc_handle_t handle, uint16_t *host_addr, uint16_t *dev_addr, size_t repcount, uint_t flags);

       void ddi_rep_put32(ddi_acc_handle_t handle, uint32_t *host_addr, uint32_t *dev_addr, size_t repcount, uint_t flags);

       void ddi_rep_put64(ddi_acc_handle_t handle, uint64_t *host_addr, uint64_t *dev_addr, size_t repcount, uint_t flags);

INTERFACE LEVEL

       Solaris DDI specific (Solaris DDI).

PARAMETERS

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

       host_addr       Base host address.

       dev_addr        Base device address.

       repcount        Number of data accesses to perform.

       flags	       Device address flags:

		       DDI_DEV_AUTOINCR

			   Automatically increment the device address,	dev_addr, during data accesses.

		       DDI_DEV_NO_AUTOINCR

			   Do not advance the  device address,	dev_addr, during data accesses.

DESCRIPTION

       These routines generate multiple writes to the mapped memory or device register. repcount data is copied from the host address,	host_addr,
       to  the	device	address,  dev_addr. For each input datum, the  ddi_rep_put8(), ddi_rep_put16(), ddi_rep_put32(), and ddi_rep_put64() func-
       tions write 8 bits, 16 bits, 32 bits, and 64 bits of data, respectively,  to the device address, dev_addr. dev_addr and host_addr  must	be
       aligned to the datum boundary described by the function.

       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 char-
       acteristics.

       When  the  flags argument is set to  DDI_DEV_AUTOINCR, these functions treat the device address,  dev_addr, as a memory buffer location	on
       the device and increment its address on the next input datum.  However, when the  flags argument is set to  DDI_DEV_NO_AUTOINCR,  the  same
       device address will be used for every datum access. For example, this flag may be useful when writing to a data register.

CONTEXT

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

SEE ALSO

       ddi_get8(9F), ddi_put8(9F), ddi_regs_map_free(9F), ddi_regs_map_setup(9F), ddi_rep_get8(9F), ddi_device_acc_attr(9S)

NOTES

       The functions described in this manual page previously used symbolic  names which specified their data access size; the function names have
       been changed so they now specify a fixed-width data size.
	See the  following table for the new name equivalents:

       +------------------------------+----------------------------+
       |       Previous Name	      | 	New Name	   |
       |ddi_rep_putb		      |ddi_rep_put8		   |
       |ddi_rep_putw		      |ddi_rep_put16		   |
       |ddi_rep_putl		      |ddi_rep_put32		   |
       |ddi_rep_putll		      |ddi_rep_put64		   |
       +------------------------------+----------------------------+

SunOS 5.10							    10 Sep 1996 						  ddi_rep_put8(9F)