Home
last modified time | relevance | path

Searched refs:milliseconds (Results 1 – 13 of 13) sorted by relevance

/linux-2.4.37.9/drivers/isdn/sc/
Dcard.h33 #define CHECKRESET_TIME milliseconds(4000)
38 #define CHECKSTAT_TIME milliseconds(8000)
44 #define SAR_TIMEOUT milliseconds(10000)
Dhardware.h108 #define milliseconds(x) (x/(1000/HZ)) macro
Dinit.c168 schedule_timeout(milliseconds(10000)); in sc_init()
/linux-2.4.37.9/include/acpi/
Dacpiosxf.h218 u32 milliseconds);
/linux-2.4.37.9/Documentation/input/
Djoystick-api.txt33 __u32 time; /* event timestamp in milliseconds */
118 in milliseconds since ... well, since sometime in the past. This eases the
/linux-2.4.37.9/Documentation/networking/
Dbonding.txt421 monitoring performed every 100 milliseconds, and one with ARP link
422 monitoring performed every 200 milliseconds, the /etc/conf.modules should
724 It takes an integer that represents the checking time in milliseconds. It
877 milliseconds, must be a multiple of miimon).
883 (in milliseconds, must be a multiple of miimon).
Dvortex.txt213 Sets the time duration (in milliseconds) after which the kernel
/linux-2.4.37.9/Documentation/usb/
Dphilips.txt83 (in milliseconds). One of the interesting things that you can do with
Dproc_usb_info.txt271 measured in microseconds rather than milliseconds.
/linux-2.4.37.9/Documentation/filesystems/
Dvfat.txt122 unsigned char ctime_ms; // Creation time, milliseconds
/linux-2.4.37.9/Documentation/
Dparport.txt181 timeslice The number of milliseconds that a device driver is
DConfigure.help8132 The number of milliseconds to delay after an initial bus reset.
8309 The number of milliseconds to delay after an initial bus reset.
/linux-2.4.37.9/drivers/scsi/
Dgdth.c416 static void gdth_delay(int milliseconds);
731 static void gdth_delay(int milliseconds) in gdth_delay() argument
733 if (milliseconds == 0) { in gdth_delay()
736 mdelay(milliseconds); in gdth_delay()