Searched full:convention (Results 1 – 25 of 67) sorted by relevance
123
| /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.
|
| /Documentation/devicetree/bindings/serial/ |
| D | nxp,lpc1850-uart.txt | 12 convention outlined in bindings/dma/dma.txt
|
| /Documentation/leds/ |
| D | uleds.rst | 24 convention of "devicename:color:function".
|
| /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/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/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/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/virt/kvm/ |
| D | s390-diag.txt | 8 Note that bits are numbered as by the usual s390 convention (most significant
|
| /Documentation/ABI/testing/ |
| D | sysfs-firmware-qemu_fw_cfg | 63 convention on the blobs registered in the file directory,
|
| /Documentation/trace/ |
| D | coresight-cpu-debug.rst | 44 registers naming convention is a bit different between them, AArch64 uses
47 use AArch64 naming convention.
|
| D | tracepoints.rst | 112 The naming scheme "subsys_event" is suggested here as a 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/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/riscv/ |
| D | pmu.rst | 47 various methods according to perf's internal convention and PMU-specific
237 convention of all other architectures.
|
| /Documentation/media/v4l-drivers/ |
| D | sh_mobile_ceu_camera.rst | 121 "...specification does not define an origin or units. However by convention
|
| /Documentation/ |
| D | tee.txt | 63 Convention (SMCCC) [2], which is the foundation for OP-TEE's SMC interface
|
| /Documentation/filesystems/nfs/ |
| D | exporting.rst | 96 convention of ->lookup.
|
| /Documentation/media/uapi/v4l/ |
| D | field-order.rst | 49 Whether the older field contains the top or bottom lines is a convention
|
| /Documentation/devicetree/bindings/cpu/ |
| D | cpu-topology.txt | 82 2.1 - cpu-map child nodes naming convention
85 cpu-map child nodes must follow a naming convention where the node name
|
123