Searched full:naming (Results 1 – 25 of 99) sorted by relevance
1234
| /Documentation/devicetree/bindings/arm/samsung/ |
| D | samsung-soc.yaml | 7 title: Samsung S3C, S5P and Exynos SoC compatibles naming convention
30 - description: Preferred naming style for compatibles of SoC components
|
| /Documentation/ABI/removed/ |
| D | devfs | 6 races, contains a naming policy within the kernel that is
|
| /Documentation/arch/x86/ |
| D | cpuinfo.rst | 124 Naming of Flags
130 resulting x86_cap/bug_flags[] are used to populate /proc/cpuinfo. The naming
139 b: The naming can be overridden.
148 constant. If, for some reason, the naming of X86_FEATURE_<name> changes, one
149 shall override the new naming with the name already used in /proc/cpuinfo.
151 c: The naming override can be "", which means it will not appear in /proc/cpuinfo.
|
| /Documentation/devicetree/bindings/soc/renesas/ |
| D | renesas-soc.yaml | 7 title: Renesas SoC compatibles naming convention
38 # Preferred naming style for compatibles of SoC components
|
| /Documentation/driver-api/tty/ |
| D | moxa-smartio.rst | 14 3.2 Device naming convention
105 3.2 Device naming convention
110 Device naming when more than 2 boards installed
113 Naming convention for each Smartio/Industio multiport board is
|
| /Documentation/devicetree/bindings/arm/ |
| D | qcom-soc.yaml | 7 title: Qualcomm SoC compatibles naming convention
33 # Preferred naming style for compatibles of SoC components:
|
| D | secure.txt | 13 The general principle of the naming scheme for Secure world bindings
|
| /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
|
| /Documentation/leds/ |
| D | uleds.rst | 23 any valid sysfs device node name, but consider using the LED class naming
|
| /Documentation/userspace-api/netlink/ |
| D | c-code-gen.rst | 10 to control the naming.
67 If naming is desired ``enum-name`` can be used to specify the name.
|
| /Documentation/hwmon/ |
| D | powr1220.rst | 32 The input naming convention is as follows:
|
| /Documentation/networking/pse-pd/ |
| D | introduction.rst | 41 Kernel Naming Convention Recommendations
45 following naming conventions are recommended:
|
| /Documentation/networking/ |
| D | alias.rst | 19 Alias creation is done by 'magic' interface naming: eg. to create a
|
| /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/mmc/ |
| D | sdhci-omap.txt | 28 DMA specifiers listed in dmas. The string naming is to be "tx"
|
| /Documentation/rust/ |
| D | coding-guidelines.rst | 194 Naming chapter
197 Rust kernel code follows the usual Rust naming conventions:
199 https://rust-lang.github.io/api-guidelines/naming.html
207 Having said that, casing should be adjusted to follow the Rust naming
|
| /Documentation/devicetree/bindings/powerpc/fsl/ |
| D | mpc5200.txt | 7 Naming conventions
40 avoid naming conflicts with non-psc devices providing the same
50 board will have this node, and as such there is a common naming
|
| /Documentation/admin-guide/ |
| D | devices.rst | 36 and can use ``sysfs`` and ``udev`` (``systemd``) to handle the naming needs.
171 naming and use of the various types of TTYs. Note that the naming
262 the System V/Unix98 naming scheme for PTYs, which assigns a common
|
| /Documentation/virt/coco/ |
| D | tdx-guest.rst | 42 a new IOCTL CMD will be created to handle it. To keep the IOCTL naming
|
| /Documentation/crypto/ |
| D | intro.rst | 71 all the same naming conventions of crypto_alloc\*.
|
| /Documentation/devicetree/bindings/timer/ |
| D | arm,sp804.yaml | 69 # consistent naming used in the existing DTs. The primecell binding
|
| /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/interrupt-controller/ |
| D | brcm,bcm2835-armctrl-ic.txt | 6 as "armctrl" in the SoC documentation, hence naming of this binding.
|
| /Documentation/devicetree/bindings/soc/fsl/cpm_qe/qe/ |
| D | ucc.txt | 49 - phy-connection-type : a string naming the controller/PHY interface type,
|
| /Documentation/dev-tools/kunit/ |
| D | style.rst | 72 a way of categorizing test suites and naming modules which provides a
136 naming. It is a good idea to make your test functions `static` to avoid
|
1234