Home
last modified time | relevance | path

Searched refs:signals (Results 1 – 25 of 50) sorted by relevance

12

/linux-2.4.37.9/Documentation/isdn/
DINTERFACE.fax72 ISDN_TTY_FAX_DR signals +FDR command to HL
74 ISDN_TTY_FAX_DT signals +FDT command to HL
76 ISDN_TTY_FAX_ET signals +FET command to HL
92 ISDN_TTY_FAX_ET signals end of data,
95 ISDN_TTY_FAX_FCON signals the established, outgoing connection,
98 ISDN_TTY_FAX_FCON_I signals the established, incoming connection,
103 ISDN_TTY_FAX_SENT signals that all data has been sent
107 ISDN_TTY_FAX_PTS signals a msg-confirmation (page sent successful),
114 ISDN_TTY_FAX_EOP signals end of data in receive mode,
DINTERFACE514 With this call, the HL-driver signals the availability of new data
527 With this call, the HL-driver signals an incoming call to the LL.
566 With this call, the HL-driver signals availability of the ISDN-card.
577 With this call, the HL-driver signals unavailability of the ISDN-card.
588 With this call, the HL-driver signals the successful establishment of
599 With this call, the HL-driver signals the successful establishment of
616 With this call, the HL-driver signals the shutdown of a
629 With this call, the HL-driver signals the shutdown of a
657 With this call, the HL-driver signals that it will be unloaded now. This
668 With this call the HL-driver signals the delivery of a data-packet.
[all …]
/linux-2.4.37.9/Documentation/arm/SA1100/
DPCMCIA59 - associate the given handler with any interrupt-generating signals
61 - set up any necessary edge detection for card ready signals
120 Regardless of how the various signals are routed to the SA-1100, the bits
131 A note about the BVD signals: if your board does not make both lines
133 standard interpretation of the BVD signals is:
143 interpretation of the VS signals (for a "low-voltage" socket) is:
322 bank 3 for the other signals, such as voltage sense or reset:
362 signals are routed through GPIO, with power and reset placed in a
DLART6 other StrongARM-gadgets. Almost all SA signals are directly accessible
/linux-2.4.37.9/kernel/
Dsignal.c352 static int signal_type(int sig, struct signal_struct *signals) in signal_type() argument
356 if (!signals) in signal_type()
359 handler = (unsigned long) signals->action[sig-1].sa.sa_handler; in signal_type()
442 static int send_signal(int sig, struct siginfo *info, struct sigpending *signals) in send_signal() argument
461 *signals->tail = q; in send_signal()
462 signals->tail = &q->next; in send_signal()
491 sigaddset(&signals->signal, sig); in send_signal()
/linux-2.4.37.9/include/linux/
Dcomstats.h67 unsigned long signals; member
Dcdk.h411 unsigned long signals; member
/linux-2.4.37.9/Documentation/
Ddnotify.txt10 being delivered using signals.
33 Preferably the application will choose one of the real time signals
Drtc.txt10 However it can also be used to generate signals from a slow 2Hz to a
11 relatively fast 8192Hz, in increments of powers of two. These signals
Dpcwd-watchdog.txt12 signals to it so it doesn't reset your computer ... at least during
/linux-2.4.37.9/arch/mips64/kernel/
Dentry.S44 mfc0 t0, CP0_STATUS # need_resched and signals atomic test
/linux-2.4.37.9/Documentation/sysctl/
Dkernel.txt195 of POSIX realtime (queued) signals that can be outstanding
198 Rtsig-nr shows the number of RT signals currently queued.
/linux-2.4.37.9/drivers/net/wan/
Dfarsync.c1132 int signals; in fst_intr_ctlchg() local
1134 signals = FST_RDL(card, v24DebouncedSts[port->index]); in fst_intr_ctlchg()
1136 if (signals & (((port->hwif == X21) || (port->hwif == X21D)) in fst_intr_ctlchg()
2168 int signals; in fst_openport() local
2189 signals = FST_RDL(port->card, v24DebouncedSts[port->index]); in fst_openport()
2190 if (signals & (((port->hwif == X21) || (port->hwif == X21D)) in fst_openport()
/linux-2.4.37.9/arch/mips/kernel/
Dentry.S42 mfc0 t0, CP0_STATUS # need_resched and signals atomic test
Dscall_o32.S66 mfc0 t0, CP0_STATUS # need_resched and signals atomic test
/linux-2.4.37.9/Documentation/video4linux/bttv/
DREADME.quirks24 The inter-nal GNT[0:1] signals are gated asynchronously with GNT and
/linux-2.4.37.9/drivers/scsi/
Datari_NCR5380.c531 signals[] = {{ SR_DBP, "PARITY"}, { SR_RST, "RST" }, { SR_BSY, "BSY" }, variable
567 for (i = 0; signals[i].mask ; ++i) in NCR5380_print()
568 if (status & signals[i].mask) in NCR5380_print()
569 printk(",%s", signals[i].name); in NCR5380_print()
Dmac_NCR5380.c554 signals[] = {{ SR_DBP, "PARITY"}, { SR_RST, "RST" }, { SR_BSY, "BSY" }, variable
590 for (i = 0; signals[i].mask ; ++i) in NCR5380_print()
591 if (status & signals[i].mask) in NCR5380_print()
592 printk(",%s", signals[i].name); in NCR5380_print()
Dsun3_NCR5380.c539 signals[] = {{ SR_DBP, "PARITY"}, { SR_RST, "RST" }, { SR_BSY, "BSY" }, variable
575 for (i = 0; signals[i].mask ; ++i) in NCR5380_print()
576 if (status & signals[i].mask) in NCR5380_print()
577 printk(",%s", signals[i].name); in NCR5380_print()
DNCR5380.c356 } signals[] = { variable
417 for (i = 0; signals[i].mask; ++i) in NCR5380_print()
418 if (status & signals[i].mask) in NCR5380_print()
419 printk(",%s", signals[i].name); in NCR5380_print()
/linux-2.4.37.9/drivers/char/
Distallion.c2636 (stli_comstats.signals & TIOCM_RTS) ? "|RTS" : "", in stli_portinfo()
2637 (stli_comstats.signals & TIOCM_CTS) ? "|CTS" : "", in stli_portinfo()
2638 (stli_comstats.signals & TIOCM_DTR) ? "|DTR" : "", in stli_portinfo()
2639 (stli_comstats.signals & TIOCM_CD) ? "|DCD" : "", in stli_portinfo()
2640 (stli_comstats.signals & TIOCM_DSR) ? "|DSR" : ""); in stli_portinfo()
5091 stli_comstats.signals = stli_mktiocm(stli_cdkstats.signals); in stli_portcmdstats()
/linux-2.4.37.9/Documentation/arm/nwfpe/
DREADME.FPE152 on signals. It is not strictly necessary to use the module.
/linux-2.4.37.9/arch/m68k/ifpsp060/
Diskeleton.S79 jne SYMBOL_NAME(ret_from_exception) | deliver signals,
/linux-2.4.37.9/arch/cris/kernel/
Dentry.S252 ba _ret_with_reschedule ; go back but check schedule and signals first
/linux-2.4.37.9/arch/x86_64/kernel/
Dentry.S233 # RED-PEN: can we lose signals here?

12