Searched full:convention (Results 1 – 25 of 315) sorted by relevance
12345678910>>...13
| /Linux-v5.4/arch/arm/xen/ |
| D | hypercall.S | 34 * The Xen hypercall calling convention is very similar to the ARM
35 * procedure calling convention: the first paramter is passed in r0, the
38 * in r4, differently from the procedure calling convention of using the
|
| /Linux-v5.4/include/linux/ |
| D | arm-smccc.h | 11 * This file provides common defines for ARM SMC Calling Convention as
113 * This function is used to make SMC calls following SMC Calling Convention.
131 * Convention. The content of the supplied param are copied to registers 0
277 * This macro is used to make SMC calls following SMC Calling Convention v1.1.
293 * This macro is used to make HVC calls following SMC Calling Convention v1.1.
|
| D | mutex.h | 178 * NOTE: mutex_trylock() follows the spin_trylock() convention,
179 * not the down_trylock() convention!
|
| D | coresight-pmu.h | 30 * the common convention is to have data trace IDs be I(N) + 1, in coresight_get_trace_id()
|
| /Linux-v5.4/tools/lib/bpf/ |
| D | README.rst | 3 libbpf API naming convention
7 functions and types. Every group has its own naming convention
85 API documentation above. See API naming convention to choose the right
|
| /Linux-v5.4/arch/xtensa/include/uapi/asm/ |
| D | swab.h | 47 * __asm__ macro follows convention that the upper 16 bits of an in __arch_swab16()
49 * follow convention; indeed, it leaves garbage in the upport 16 in __arch_swab16()
|
| /Linux-v5.4/Documentation/bpf/ |
| D | bpf_design_QA.rst | 26 BPF is generic instruction set *with* C calling convention.
29 Q: Why C calling convention was chosen? argument
36 defines calling convention that is compatible with C calling
37 convention of the linux kernel on those architectures.
45 A: NO. BPF calling convention only allows registers R1-R5 to be used
62 Q: Does C-calling convention diminishes possible use cases?
|
| /Linux-v5.4/arch/ia64/kernel/ |
| D | pal.S | 43 * uses the static calling convention, i.e., the RSE may not be used and
52 * Make a PAL call using the static calling convention.
95 * Make a PAL call using the stacked registers calling convention.
131 * Make a physical mode PAL call using the static registers calling convention.
|
| /Linux-v5.4/arch/x86/boot/compressed/ |
| D | efi_stub_32.S | 20 * In gcc calling convention, EBX, ESP, EBP, ESI and EDI are all callee save.
23 * service functions will comply with gcc calling convention, too.
|
| /Linux-v5.4/arch/x86/platform/efi/ |
| D | efi_stub_32.S | 18 * In gcc calling convention, EBX, ESP, EBP, ESI and EDI are all callee save.
21 * service functions will comply with gcc calling convention, too.
|
| /Linux-v5.4/Documentation/filesystems/ |
| D | adfs.txt | 68 file type information, a file naming convention was devised (initially
71 naming convention is now also used by RISC OS emulators such as RPCEmu.
|
| /Linux-v5.4/drivers/staging/speakup/ |
| D | i18n.h | 51 MSG_START, /* A little confusing, given our convention. */
52 MSG_END, /* A little confusing, given our convention. */
|
| /Linux-v5.4/Documentation/devicetree/bindings/powerpc/fsl/ |
| D | mpc5200.txt | 31 It is *strongly* recommended that 5200B device trees follow this convention
39 "fsl,mpc5200-psc-i2s", not "fsl,mpc5200-i2s". This convention is chosen to
51 convention for SOC devices.
|
| /Linux-v5.4/arch/powerpc/include/uapi/asm/ |
| D | tm.h | 6 * convention, bit0 is copied to TEXASR[56] (IBM bit 7) which is set if
|
| /Linux-v5.4/drivers/tee/optee/ |
| D | optee_smc.h | 19 * Function specified by SMC Calling convention.
40 * Function specified by SMC Calling convention
54 * Function specified by SMC Calling convention
|
| /Linux-v5.4/arch/x86/entry/ |
| D | calling.h | 12 x86 function call convention, 64-bit:
25 [**] for struct return values wider than 64 bits the return convention is a
36 x86 function calling convention, 32-bit:
|
| /Linux-v5.4/include/uapi/linux/ |
| D | atmapi.h | 25 * Convention: NULL pointers are passed as a field of all zeroes.
|
| /Linux-v5.4/tools/include/linux/ |
| D | coresight-pmu.h | 30 * the common convention is to have data trace IDs be I(N) + 1, in coresight_get_trace_id()
|
| /Linux-v5.4/arch/mips/include/uapi/asm/ |
| D | sgidefs.h | 31 * Subprogram calling convention
|
| /Linux-v5.4/Documentation/devicetree/bindings/serial/ |
| D | nxp,lpc1850-uart.txt | 12 convention outlined in bindings/dma/dma.txt
|
| /Linux-v5.4/arch/mips/kernel/ |
| D | scall64-o32.S | 12 * convention than the kernel, so we have to translate things from o32
13 * to ABI64 calling convention. 64-bit syscalls are also processed
|
| /Linux-v5.4/Documentation/devicetree/bindings/gpio/ |
| D | nvidia,tegra186-gpio.txt | 30 Tegra HW documentation describes a unified naming convention for all GPIOs
43 describes the port-level mapping. In that file, the naming convention for ports
|
| /Linux-v5.4/Documentation/leds/ |
| D | uleds.rst | 24 convention of "devicename:color:function".
|
| /Linux-v5.4/arch/x86/include/asm/ |
| D | syscalls.h | 23 * different syscall calling convention
|
| /Linux-v5.4/Documentation/devicetree/bindings/arm/firmware/ |
| D | sdei.txt | 13 Convention (ARM DEN 0028B):
|
12345678910>>...13
