xref: /illumos-gate/usr/src/man/man9f/delay.9f (revision 8459c777fc1aaabb2f7dad05de1313aa169417cd)
te
Copyright (c) 2001, Sun Microsystems, Inc. All Rights Reserved.
Copyright 1989 AT&T
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]
DELAY 9F "Oct 15, 2001"
NAME
delay - delay execution for a specified number of clock ticks
SYNOPSIS

#include <sys/ddi.h>



void delay(clock_t ticks);
INTERFACE LEVEL

Architecture independent level 1 (DDI/DKI).

PARAMETERS
ticks

The number of clock cycles to delay.

DESCRIPTION

delay() provides a mechanism for a driver to delay its execution for a given period of time. Since the speed of the clock varies among systems, drivers should base their time values on microseconds and use drv_usectohz(9F) to convert microseconds into clock ticks.

delay() uses timeout(9F) to schedule an internal function to be called after the specified amount of time has elapsed. delay() then waits until the function is called. Because timeout() is subject to priority inversion, drivers waiting on behalf of processes with real-time constraints should use cv_timedwait(9F) rather than delay().

delay() does not busy-wait. If busy-waiting is required, use drv_usecwait(9F).

CONTEXT

delay() can be called from user and kernel contexts.

EXAMPLES

Example 1 delay() Example

Before a driver I/O routine allocates buffers and stores any user data in them, it checks the status of the device (line 12). If the device needs manual intervention (such as, needing to be refilled with paper), a message is displayed on the system console (line 14). The driver waits an allotted time (line 17) before repeating the procedure.

 1 struct device { /* layout of physical device registers */
 2 int control; /* physical device control word */
 3 int status; /* physical device status word */
 4 short xmit_char; /* transmit character to device */
 5 };
 6
 7
 ...
 9 /* get device registers */
10 register struct device *rp = ...
11
12 while (rp->status & NOPAPER) { /* while printer is out of paper */
13 /* display message and ring bell */
 /* on system console */
14 cmn_err(CE_WARN, "^\e007",
15 (getminor(dev) & 0xf));
16 /* wait one minute and try again */
17 delay(60 * drv_usectohz(1000000));
18 }
SEE ALSO

biodone(9F), biowait(9F), cv_timedwait(9F), ddi_in_panic(9F), drv_hztousec(9F), drv_usectohz(9F), drv_usecwait(9F), timeout(9F), untimeout(9F)

Writing Device Drivers