| /f-stack/freebsd/contrib/device-tree/Bindings/spi/ |
| H A D | omap-spi.txt | 19 1:1 with the DMA specifiers listed in dmas. The string naming
|
| /f-stack/freebsd/contrib/device-tree/Bindings/mmc/ |
| H A D | sdhci-omap.txt | 24 DMA specifiers listed in dmas. The string naming is to be "tx"
|
| H A D | renesas,sdhi.txt | 52 "core" and "cd". If the controller only has 1 clock, naming is not
|
| H A D | ti-omap-hsmmc.txt | 51 The string naming is to be "rx" and "tx" for
|
| /f-stack/freebsd/contrib/device-tree/src/arm64/actions/ |
| H A D | s900-bubblegum-96.dts | 82 * When the 96Boards naming of a line and the schematic name of
87 * naming has been preferred. This is only for the informational
|
| /f-stack/freebsd/contrib/device-tree/Bindings/interrupt-controller/ |
| H A D | brcm,bcm2835-armctrl-ic.txt | 6 as "armctrl" in the SoC documentation, hence naming of this binding.
|
| /f-stack/freebsd/contrib/device-tree/Bindings/pinctrl/ |
| H A D | ingenic,pinctrl.txt | 10 naming scheme "PxN" where x is a character identifying the GPIO port with
|
| H A D | ingenic,pinctrl.yaml | 17 naming scheme "PxN" where x is a character identifying the GPIO port with
|
| H A D | pinmux-node.yaml | 46 pin controller instances, naming each pin and function can easily become
|
| /f-stack/freebsd/contrib/device-tree/Bindings/gpio/ |
| H A 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
|
| /f-stack/freebsd/contrib/device-tree/Bindings/soc/fsl/cpm_qe/qe/ |
| H A D | ucc.txt | 49 - phy-connection-type : a string naming the controller/PHY interface type,
|
| /f-stack/freebsd/contrib/device-tree/src/arm64/bitmain/ |
| H A D | bm1880-sophon-edge.dts | 26 * When the 96Board naming of a line and the schematic name of
|
| /f-stack/freebsd/contrib/device-tree/Bindings/arm/ |
| H A D | secure.txt | 13 The general principle of the naming scheme for Secure world bindings
|
| /f-stack/freebsd/contrib/device-tree/Bindings/leds/ |
| H A D | leds-lp55xx.txt | 20 - label: Used for naming LEDs
|
| /f-stack/freebsd/contrib/device-tree/Bindings/powerpc/fsl/ |
| H A D | mpc5200.txt | 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
|
| /f-stack/freebsd/contrib/device-tree/Bindings/mtd/ |
| H A D | partition.txt | 9 the geometry and naming/purpose of each functional region. It is also possible
|
| /f-stack/dpdk/doc/guides/prog_guide/ |
| H A D | trace_lib.rst | 73 ``rte_<library_name>_trace_[<domain>_]<name>`` naming convention must be
113 However, it is recommended to have a similar name for a better naming
|
| /f-stack/freebsd/contrib/device-tree/Bindings/cpu/ |
| H A 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
|
| /f-stack/dpdk/doc/guides/linux_gsg/ |
| H A D | nic_perf_intel_platform.rst | 93 …wing are some recommendations on BIOS settings. Different platforms will have different BIOS naming
|
| /f-stack/freebsd/contrib/device-tree/src/arm64/hisilicon/ |
| H A D | hi3670-hikey970.dts | 90 * When the 96Board naming of a line and the schematic name of
|
| H A D | hi6220-hikey.dts | 363 * When the 96Board naming of a line and the schematic name of
|
| /f-stack/app/redis-5.0.5/deps/jemalloc/include/jemalloc/internal/ |
| H A D | jemalloc_internal_defs.h.in | 26 * from being exported, but for static libraries, naming collisions are a real
|
| /f-stack/freebsd/contrib/device-tree/src/arm/ |
| H A D | ste-snowball.dts | 385 * while later naming "GPIO4" as "PM_GPIO4".
|
| H A D | dra76x-mmc-iodelay.dtsi | 21 * to curb naming creativity and achieve consistency.
|
| /f-stack/dpdk/doc/guides/rel_notes/ |
| H A D | release_16_11.rst | 233 * The driver naming convention has been changed to make them more
269 * Device naming functions have been generalized from ethdev and cryptodev
|