Searched full:spaces (Results 1 – 25 of 95) sorted by relevance
1234
| /Documentation/devicetree/bindings/ |
| D | .yamllint | 10 min-spaces-inside: 0
11 max-spaces-inside: 1
12 min-spaces-inside-empty: 0
13 max-spaces-inside-empty: 0
15 min-spaces-inside: 0
16 max-spaces-inside: 1
17 min-spaces-inside-empty: 0
18 max-spaces-inside-empty: 0
19 colons: {max-spaces-before: 0, max-spaces-after: 1}
20 commas: {min-spaces-after: 1, max-spaces-after: 1}
[all …]
|
| /Documentation/devicetree/bindings/display/ti/ |
| D | ti,dra7-dss.txt | 12 - reg: address and length of the register spaces for 'dss'
23 - reg: address and length of the register spaces for 'pll1_clkctrl',
60 - reg: addresses and lengths of the register spaces for 'wp', 'pll', 'phy',
|
| D | ti,omap5-dss.txt | 64 - reg: addresses and lengths of the register spaces for 'proto', 'phy' and 'pll'
86 - reg: addresses and lengths of the register spaces for 'wp', 'pll', 'phy',
|
| D | ti,omap4-dss.txt | 83 - reg: addresses and lengths of the register spaces for 'proto', 'phy' and 'pll'
105 - reg: addresses and lengths of the register spaces for 'wp', 'pll', 'phy',
|
| D | ti,omap3-dss.txt | 77 - reg: addresses and lengths of the register spaces for 'proto', 'phy' and 'pll'
|
| /Documentation/process/ |
| D | code-of-conduct.rst | 57 This Code of Conduct applies both within project spaces and in public spaces
|
| D | email-clients.rst | 35 or spaces, even at the beginning or end of lines.
52 because tabs are converted to spaces. Using xclipboard, xclip, and/or
321 Gmail web client converts tabs to spaces automatically.
|
| /Documentation/devicetree/bindings/clock/ |
| D | marvell,pxa168.txt | 13 "mpmu", "apmu", "apbc". So three reg spaces need to be defined.
|
| D | marvell,pxa910.txt | 13 "mpmu", "apmu", "apbc", "apbcp". So four reg spaces need to be defined.
|
| /Documentation/vm/ |
| D | active_mm.rst | 26 - we have "real address spaces" and "anonymous address spaces". The
|
| /Documentation/x86/x86_64/ |
| D | fsgs.rst | 145 Named Address Spaces. GCC implements the following address space
154 address spaces are supported. Code which implements fallback modes should
181 address spaces via an attribute based mechanism in Clang 2.6 and newer
192 In case the compiler does not support address spaces, inline assembly can
|
| /Documentation/userspace-api/media/rc/ |
| D | lirc-set-send-carrier.rst | 34 Set send carrier used to modulate IR PWM pulses and spaces.
|
| D | lirc-set-rec-carrier.rst | 34 Set receive carrier used to modulate IR PWM pulses and spaces.
|
| D | lirc-write.rst | 48 the chardev is a pulse/space sequence of integer values. Pulses and spaces
|
| /Documentation/devicetree/bindings/net/can/ |
| D | ti_hecc.txt | 9 - reg: addresses and lengths of the register spaces for 'hecc', 'hecc-ram'
|
| /Documentation/ABI/testing/ |
| D | debugfs-cec-error-inj | 12 Leading spaces/tabs are ignored. If the next character is a '#' or the
|
| /Documentation/admin-guide/ |
| D | kernel-parameters.rst | 38 Double-quotes can be used to protect spaces in values, e.g.::
40 param="spaces in here"
197 complete command line (parameters including spaces etc.) is limited to
|
| /Documentation/i2c/busses/ |
| D | i2c-ali1535.rst | 37 just enable the SMB alone. The SMB and the ACPI have separate I/O spaces.
|
| /Documentation/devicetree/bindings/pci/ |
| D | host-generic-pci.yaml | 19 Configuration Spaces.
69 that cover all config, MMIO and I/O spaces in a [mostly] ECAM
|
| /Documentation/gpu/ |
| D | msm-crash-dump.rst | 12 and all the contents of a section will be indented two spaces from the header.
|
| /Documentation/devicetree/bindings/usb/ |
| D | da8xx-usb.txt | 33 - reg: offset and length of the following register spaces: CPPI DMA Controller,
|
| /Documentation/driver-api/ |
| D | vme.rst | 65 split into the VME address spaces that need to be accessed in 'aspace' and VME
97 address spaces, transfer widths and cycle types are the same as described
128 The address spaces, transfer widths and cycle types are the same as described
|
| /Documentation/kbuild/ |
| D | kconfig-macro-language.rst | 155 trick to start the first parameter with spaces. For example, if you want
168 of leading spaces may matter depending on the function. The same applies to
|
| /Documentation/filesystems/nfs/ |
| D | rpc-cache.rst | 210 Fields within the record should be separated by spaces, normally one.
211 If spaces, newlines, or nul characters are needed in a field they
|
| /Documentation/devicetree/bindings/arm/ |
| D | secure.txt | 3 ARM CPUs with TrustZone support have two distinct address spaces,
|
1234