Searched full:convention (Results 1 – 25 of 89) sorted by relevance
1234
| /Documentation/arch/mips/ |
| D | booting.rst | 23 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
|
| /Documentation/bpf/standardization/ |
| D | abi.rst | 11 Registers and calling convention
17 The BPF calling convention is defined as:
|
| /Documentation/bpf/libbpf/ |
| D | libbpf_naming_convention.rst | 3 API naming convention
7 functions and types. Every group has its own naming convention
68 API documentation above. See API naming convention to choose the right
145 API documentation convention
151 convention in which these comments should be formatted.
|
| D | libbpf_overview.rst | 234 * `API naming convention <https://libbpf.readthedocs.io/en/latest/libbpf_naming_convention.html>`_
236 * `API documentation Convention <https://libbpf.readthedocs.io/en/latest/libbpf_naming_convention.h…
|
| /Documentation/arch/x86/ |
| D | booting-dt.rst | 9 supports one calling convention which is documented in
|
| /Documentation/leds/ |
| D | uleds.rst | 24 convention of "devicename:color:function".
|
| /Documentation/devicetree/bindings/arm/samsung/ |
| D | samsung-soc.yaml | 7 title: Samsung S3C, S5P and Exynos SoC compatibles naming convention
|
| /Documentation/devicetree/bindings/arm/firmware/ |
| D | sdei.txt | 13 Convention (ARM DEN 0028B):
|
| /Documentation/hwmon/ |
| D | powr1220.rst | 32 The input naming convention is as follows:
|
| /Documentation/devicetree/bindings/spi/ |
| D | microchip,spi-pic32.txt | 15 - dmas: Two or more DMA channel specifiers following the convention outlined
|
| D | spi-pl022.yaml | 58 Two or more DMA channel specifiers following the convention outlined
|
| /Documentation/ABI/stable/ |
| D | vdso | 14 (ex: powerpc) they are called with the same convention as system calls which
|
| /Documentation/driver-api/tty/ |
| D | moxa-smartio.rst | 14 3.2 Device naming convention
105 3.2 Device naming convention
113 Naming convention for each Smartio/Industio multiport board is
|
| /Documentation/bpf/ |
| D | classic_vs_extended.rst | 24 etc, and eBPF calling convention maps directly to ABIs used by the kernel on
61 - Introduces bpf_call insn and register passing convention for zero overhead
66 convention, then the interpreter will take them from registers and pass
71 instruction. This calling convention was picked to cover common call
189 them across the calls as defined by calling convention.
|
| D | bpf_design_QA.rst | 26 BPF is generic instruction set *with* C calling convention.
29 Q: Why C calling convention was chosen?
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?
|
| /Documentation/filesystems/ |
| D | adfs.rst | 101 file type information, a file naming convention was devised (initially
104 naming convention is now also used by RISC OS emulators such as RPCEmu.
|
| /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.
|
| /Documentation/devicetree/bindings/net/ |
| D | qcom,bam-dmux.yaml | 19 a firmware convention that combines several other hardware blocks (such as the
|
| /Documentation/virt/kvm/arm/ |
| D | hypercalls.rst | 10 Calling Convention (DEN0028/C):
28 | Calling convention: | HVC32 |
56 | Calling convention: | HVC64 |
85 | Calling convention: | HVC64 |
114 | Calling convention: | HVC64 |
142 | Calling convention: | HVC64 |
171 | Calling convention: | HVC64 |
245 | Calling convention: | HVC64 |
|
| /Documentation/devicetree/bindings/gpio/ |
| D | nvidia,tegra186-gpio.yaml | 41 Tegra HW documentation describes a unified naming convention for all GPIOs
55 that file, the naming convention for ports matches the HW documentation.
|
| /Documentation/devicetree/bindings/soc/renesas/ |
| D | renesas-soc.yaml | 7 title: Renesas SoC compatibles naming convention
|
| /Documentation/devicetree/bindings/arm/ |
| D | qcom-soc.yaml | 7 title: Qualcomm SoC compatibles naming convention
|
| /Documentation/trace/coresight/ |
| D | coresight-cpu-debug.rst | 44 registers naming convention is a bit different between them, AArch64 uses
47 use AArch64 naming convention.
|
| /Documentation/core-api/ |
| D | asm-annotations.rst | 28 *non-standard* calling convention. In contrast, ``ENDPROC`` should annotate
148 for interrupt handlers and similar where the calling convention is not the C
|
| /Documentation/filesystems/spufs/ |
| D | spu_create.rst | 111 convention, it gets mounted in /spu.
|
1234