xref: /titanic_52/usr/src/man/man9f/csx_Put8.9f (revision 6a1af1a67532df169a657cce07140be64bdea084)
te
Copyright (c) 1996, Sun Microsystems, Inc. All Rights Reserved
The contents of this file are subject to the terms of the Common Development and Distribution License (the "License"). You may not use this file except in compliance with the License.
You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing. See the License for the specific language governing permissions and limitations under the License.
When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE. If applicable, add the following below this CDDL HEADER, with the fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner]
csx_Put8 9F "19 Jul 1996" "SunOS 5.11" "Kernel Functions for Drivers"
NAME
csx_Put8, csx_Put16, csx_Put32, csx_Put64 - write to device register
SYNOPSIS

#include <sys/pccard.h>



void csx_Put8(acc_handle_t handle, uint32_t offset, uint8_t value);

void csx_Put16(acc_handle_t handle, uint32_t offset, uint16_t value);

void csx_Put32(acc_handle_t handle, uint32_t offset, uint32_t value);

void csx_Put64(acc_handle_t handle, uint32_t offset, uint64_t value);
INTERFACE LEVEL

Solaris DDI Specific (Solaris DDI)

PARAMETERS

handle

The access handle returned from csx_RequestIO(9F), csx_RequestWindow(9F), or csx_DupHandle(9F).

offset

The offset in bytes from the base of the mapped resource.

value

The data to be written to the device.

DESCRIPTION

These functions generate a write of various sizes to the mapped memory or device register.

The csx_Put8(), csx_Put16(), csx_Put32(), and csx_Put64() functions write 8 bits, 16 bits, 32 bits, and 64 bits of data, respectively, to the device address represented by the handle, handle, at an offset in bytes represented by the offset, offset.

Data that consists of more than one byte 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.

CONTEXT

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

SEE ALSO

csx_DupHandle(9F), csx_Get8(9F), csx_GetMappedAddr(9F), csx_RepGet8(9F), csx_RepPut8(9F), csx_RequestIO(9F), csx_RequestWindow(9F)

PC Card 95 Standard, PCMCIA/JEIDA