Home
last modified time | relevance | path

Searched refs:routines (Results 1 – 25 of 138) sorted by relevance

123456

/linux/Documentation/driver-api/media/
H A Ddtv-common.rst16 Those routines implement ring buffers used to handle digital TV data and
21 1) For performance reasons read and write routines don't check buffer sizes
23 routines are called. For example:
/linux/arch/sh/lib/
H A Dudiv_qrnnd.S8 !! libgcc routines for the Renesas / SuperH SH CPUs.
12 !! ashiftrt_r4_x, ___ashrsi3, ___ashlsi3, ___lshrsi3 routines
H A Dashiftrt.S8 !! libgcc routines for the Renesas / SuperH SH CPUs.
12 !! ashiftrt_r4_x, ___ashrsi3, ___ashlsi3, ___lshrsi3 routines
H A Dlshrsi3.S8 !! libgcc routines for the Renesas / SuperH SH CPUs.
12 !! ashiftrt_r4_x, ___ashrsi3, ___ashlsi3, ___lshrsi3 routines
H A Dashlsi3.S8 !! libgcc routines for the Renesas / SuperH SH CPUs.
12 !! ashiftrt_r4_x, ___ashrsi3, ___ashlsi3, ___lshrsi3 routines
H A Dashrsi3.S8 !! libgcc routines for the Renesas / SuperH SH CPUs.
12 !! ashiftrt_r4_x, ___ashrsi3, ___ashlsi3, ___lshrsi3 routines
H A Dudivsi3.S8 !! libgcc routines for the Renesas / SuperH SH CPUs.
H A Dmovmem.S8 !! libgcc routines for the Renesas / SuperH SH CPUs.
12 !! ashiftrt_r4_x, ___ashrsi3, ___ashlsi3, ___lshrsi3 routines
/linux/Documentation/scheduler/
H A Dsched-arch.rst24 Your cpu_idle routines need to obey the following rules:
26 1. Preempt should now disabled over idle routines. Should only
51 5. TIF_POLLING_NRFLAG can be set by idle routines that do not
/linux/Documentation/crypto/
H A Ddescore-readme.rst43 3. Plug-compatible replacement for KERBEROS's low-level routines.
68 this has the quickest encryption/decryption routines i've seen.
73 provided my routines with little stub interfaces so they can be
110 of the optimizations which i did in my encryption routines.
114 speed up the key-setting routines with impressive results.
172 a while ago i wanted some des routines and the routines documented on sun's
174 and knew that it used des, so i figured i'd use its routines. but once
262 and other tricks, you can get reasonable routines for DesQuickCore... with
270 for the DesQuickCore... routines!
275 the en/decryption routines each use 6 necessary register variables,
[all …]
/linux/arch/m68k/ifpsp060/
H A Disp.doc63 This will allow calling routines to access the entry points
76 | | - example routines in iskeleton.s
91 the ISP routines to reference external functions that must be provided
100 The second section, the "Entry-point" section, is used by external routines
187 One other necessary action by the integrator is to supply the routines
191 If the "core" emulation routines of either "cas" or "cas2" perform some
H A DTEST.DOC49 This will allow the calling routines to access the entry points
77 routines to reference external printing functions that must be provided
87 The second section, the "Entry-point" section, is used by external routines
88 to access the test routines. Since the {i,f}test.sa hex files contain
H A Dfpsp.doc55 This will allow calling routines to access the entry points
68 | | - example routines in fskeleton.s
83 the FPSP routines to reference external functions that must be provided
92 The second section, the "Entry-point" section, is used by external routines
H A Dilsp.doc58 This will allow calling routines to access the entry points
75 fixed so that a program calling the routines will not have to be
110 The library routines also return the correct condition code
H A Dfplsp.doc34 68060SP Floating-Point Software Package. The routines
59 This will allow calling routines to access the entry points
76 fixed so that a program calling the routines will not have to be
/linux/Documentation/driver-api/
H A Dbasics.rst18 Delaying and scheduling routines
36 Time and timer routines
/linux/Documentation/driver-api/tty/
H A Dtty_driver.rst17 The allocation routines expect a number of devices the driver can handle at
80 The registration routines are documented as follows:
104 The linking routines are documented here:
/linux/drivers/net/ethernet/intel/libie/
H A DKconfig9 libeth and containing vendor-specific routines shared between several
/linux/drivers/net/ethernet/intel/libeth/
H A DKconfig8 libeth is a common library containing routines shared between several
/linux/Documentation/mm/
H A Dhugetlbfs_reserv.rst152 calls into routines that potentially allocate and adjust surplus page counts.
153 However, within those routines the code is simply checking to ensure there
257 information on these routines.
314 The routines hugepage_subpool_get/put_pages() are called when pages are
371 The following low level routines are used to make modifications to a
372 reservation map. Typically, these routines are not called directly. Rather,
374 routines. These low level routines are fairly well documented in the source
375 code (mm/hugetlb.c). These routines are::
456 Several helper routines exist to query and modify the reservation maps.
457 These routines are only interested with reservations for a specific huge
[all …]
/linux/Documentation/core-api/
H A Ddma-isa-lpc.rst22 The second contains the routines specific to ISA DMA transfers. Since
89 Before you use any ISA DMA routines you need to claim the DMA lock
106 transfer. Note that it's _bytes_. The DMA routines will do all the
/linux/drivers/ssb/
H A DKconfig24 # Common SPROM support routines
96 # ChipCommon and ExtIf serial support routines.
/linux/Documentation/infiniband/
H A Dtag_matching.rst46 to the MPI receive routines in the posted receive list and posts send messages
47 using the MPI send routines. The head of the posted receive list may be
/linux/Documentation/arch/arm/nwfpe/
H A Dtodo.rst21 and are handled by routines in libc. These are not implemented by the FPA11
26 method would be to use accurate table methods for these routines. I have
/linux/arch/m68k/fpsp040/
H A Dkernel_ex.S4 | This file contains routines to force exception status in the
130 | This entry point is used by all routines requiring unfl, inex2,

123456