Home
last modified time | relevance | path

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

123

/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
/Documentation/x86/
Dbooting-dt.rst9 supports one calling convention which is documented in
/Documentation/devicetree/bindings/serial/
Dnxp,lpc1850-uart.txt12 convention outlined in bindings/dma/dma.txt
/Documentation/bpf/
Dbpf_design_QA.rst26 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/leds/
Duleds.rst24 convention of "devicename:color:function".
/Documentation/devicetree/bindings/spi/
Dmicrochip,spi-pic32.txt15 - dmas: Two or more DMA channel specifiers following the convention outlined
Dqcom,spi-qup.txt36 - dmas: Two DMA channel specifiers following the convention outlined
Dspi-samsung.txt21 - dmas : Two or more DMA channel specifiers following the convention outlined
Dspi-pl022.yaml59 Two or more DMA channel specifiers following the convention outlined
/Documentation/devicetree/bindings/arm/firmware/
Dsdei.txt13 Convention (ARM DEN 0028B):
/Documentation/hwmon/
Dpowr1220.rst32 The input naming convention is as follows:
Dntc_thermistor.rst39 Using the following convention::
/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.
/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.
/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
/Documentation/
Dasm-annotations.rst28 *non-standard* calling convention. In contrast, ``ENDPROC`` should annotate
148 for interrupt handlers and similar where the calling convention is not the C
/Documentation/virt/kvm/
Ds390-diag.rst11 Note that bits are numbered as by the usual s390 convention (most significant
/Documentation/trace/coresight/
Dcoresight-cpu-debug.rst44 registers naming convention is a bit different between them, AArch64 uses
47 use AArch64 naming convention.
/Documentation/driver-api/serial/
Dmoxa-smartio.rst21 3.3 Device naming convention
162 3.3 Device naming convention
175 which is named "ttyMxx". For callout port, the naming convention
181 Naming convention for each Smartio/Industio multiport board is
459 convention, all you have to do is to modify the internal code
/Documentation/userspace-api/ioctl/
Dioctl-number.rst45 convention at all.
47 Following this convention is good because:
60 this convention is used to define the ioctl numbers.
62 (5) When following the convention, the driver code can use generic
/Documentation/filesystems/spufs/
Dspu_create.rst111 convention, it gets mounted in /spu.
/Documentation/ABI/testing/
Dsysfs-firmware-qemu_fw_cfg65 convention on the blobs registered in the file directory,
/Documentation/riscv/
Dpmu.rst47 various methods according to perf's internal convention and PMU-specific
237 convention of all other architectures.
/Documentation/driver-api/media/drivers/
Dsh_mobile_ceu_camera.rst121 "...specification does not define an origin or units. However by convention
/Documentation/virt/kvm/arm/
Dpvtime.rst20 These are only available in the SMC64/HVC64 calling convention as

123