Searched full:convention (Results 1 – 25 of 70) sorted by relevance
123
/Documentation/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/x86/ |
D | booting-dt.rst | 9 supports one calling convention which is documented in
|
/Documentation/devicetree/bindings/serial/ |
D | nxp,lpc1850-uart.txt | 12 convention outlined in bindings/dma/dma.txt
|
/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? 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/ |
D | uleds.rst | 24 convention of "devicename:color:function".
|
/Documentation/devicetree/bindings/spi/ |
D | microchip,spi-pic32.txt | 15 - dmas: Two or more DMA channel specifiers following the convention outlined
|
D | qcom,spi-qup.txt | 36 - dmas: Two DMA channel specifiers following the convention outlined
|
D | spi-samsung.txt | 21 - dmas : Two or more DMA channel specifiers following the convention outlined
|
D | spi-pl022.yaml | 59 Two or more DMA channel specifiers following the convention outlined
|
/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:
|
D | ntc_thermistor.rst | 39 Using the following convention::
|
/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/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
|
/Documentation/ |
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/virt/kvm/ |
D | s390-diag.rst | 11 Note that bits are numbered as by the usual s390 convention (most significant
|
/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/driver-api/serial/ |
D | moxa-smartio.rst | 21 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/ |
D | ioctl-number.rst | 45 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/ |
D | spu_create.rst | 111 convention, it gets mounted in /spu.
|
/Documentation/ABI/testing/ |
D | sysfs-firmware-qemu_fw_cfg | 65 convention on the blobs registered in the file directory,
|
/Documentation/riscv/ |
D | pmu.rst | 47 various methods according to perf's internal convention and PMU-specific 237 convention of all other architectures.
|
/Documentation/driver-api/media/drivers/ |
D | sh_mobile_ceu_camera.rst | 121 "...specification does not define an origin or units. However by convention
|
/Documentation/virt/kvm/arm/ |
D | pvtime.rst | 20 These are only available in the SMC64/HVC64 calling convention as
|
123