Home
last modified time | relevance | path

Searched full:convention (Results 1 – 25 of 333) sorted by relevance

12345678910>>...14

/Linux-v5.10/Documentation/mips/
Dbooting.rst23 Legacy bootloaders do not use this convention, and they do not pass in a
27 This convention is defined for 32-bit systems only, as there are not
/Linux-v5.10/arch/arm/xen/
Dhypercall.S34 * 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.10/tools/lib/bpf/
DREADME.rst3 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.10/Documentation/bpf/
Dbpf_design_QA.rst26 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.10/arch/xtensa/include/uapi/asm/
Dswab.h47 * __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.10/include/linux/
Darm-smccc.h12 * This file provides common defines for ARM SMC Calling Convention as
177 * This function is used to make SMC calls following SMC Calling Convention.
195 * Convention. The content of the supplied param are copied to registers 0
326 * This macro is used to make SMC calls following SMC Calling Convention v1.1.
342 * This macro is used to make HVC calls following SMC Calling Convention v1.1.
Dcoresight-pmu.h30 * the common convention is to have data trace IDs be I(N) + 1, in coresight_get_trace_id()
Dmutex.h192 * NOTE: mutex_trylock() follows the spin_trylock() convention,
193 * not the down_trylock() convention!
/Linux-v5.10/arch/ia64/kernel/
Dpal.S43 * 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.10/drivers/accessibility/speakup/
Di18n.h51 MSG_START, /* A little confusing, given our convention. */
52 MSG_END, /* A little confusing, given our convention. */
/Linux-v5.10/Documentation/filesystems/
Dadfs.rst101 file type information, a file naming convention was devised (initially
104 naming convention is now also used by RISC OS emulators such as RPCEmu.
/Linux-v5.10/kernel/kcsan/
Datomic.h10 * common, however, the current convention is to not mark them; returns true if
/Linux-v5.10/Documentation/devicetree/bindings/powerpc/fsl/
Dmpc5200.txt31 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.10/arch/powerpc/include/uapi/asm/
Dtm.h6 * convention, bit0 is copied to TEXASR[56] (IBM bit 7) which is set if
/Linux-v5.10/Documentation/x86/
Dbooting-dt.rst9 supports one calling convention which is documented in
/Linux-v5.10/arch/x86/entry/
Dcalling.h12 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.10/drivers/tee/optee/
Doptee_smc.h19 * Function specified by SMC Calling convention.
40 * Function specified by SMC Calling convention
54 * Function specified by SMC Calling convention
/Linux-v5.10/Documentation/devicetree/bindings/serial/
Dnxp,lpc1850-uart.txt12 convention outlined in bindings/dma/dma.txt
/Linux-v5.10/arch/mips/include/uapi/asm/
Dsgidefs.h31 * Subprogram calling convention
/Linux-v5.10/include/uapi/linux/
Datmapi.h25 * Convention: NULL pointers are passed as a field of all zeroes.
/Linux-v5.10/tools/include/linux/
Dcoresight-pmu.h30 * the common convention is to have data trace IDs be I(N) + 1, in coresight_get_trace_id()
/Linux-v5.10/Documentation/devicetree/bindings/gpio/
Dnvidia,tegra186-gpio.txt30 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.10/arch/mips/kernel/
Dscall64-o32.S12 * 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.10/Documentation/leds/
Duleds.rst24 convention of "devicename:color:function".
/Linux-v5.10/drivers/net/ethernet/marvell/octeontx2/af/
Dptp.c116 * on every coprocessor clock cycle. Typical convention is that it in ptp_adjfine()
118 * convention compensation value is in 64 bit fixed-point in ptp_adjfine()

12345678910>>...14