| /f-stack/freebsd/contrib/device-tree/Bindings/hwlock/ |
| H A D | hwlock.txt | 4 Generic bindings that are common to all the hwlock platform specific driver
7 Please also look through the individual platform specific hwlock binding
8 documentations for identifying any additional properties specific to that
16 specific lock.
21 Consumers that require specific hwlock(s) should specify them using the
34 use the hwlock-names to match and get a specific hwlock.
37 1. Example of a node using a single specific hwlock:
49 2. Example of a node using multiple specific hwlocks:
|
| /f-stack/freebsd/contrib/device-tree/Bindings/mmc/ |
| H A D | exynos-dw-mshc.txt | 1 * Samsung Exynos specific extensions to the Synopsys Designware Mobile
7 by synopsys-dw-mshc.txt and the properties used by the Samsung Exynos specific
14 specific extensions.
16 specific extensions.
18 specific extensions.
20 specific extensions.
22 specific extensions.
24 specific extensions having an SMU.
69 The MSHC controller node can be split into two portions, SoC specific and
70 board specific portions as listed below.
|
| H A D | k3-dw-mshc.txt | 1 * Hisilicon specific extensions to the Synopsys Designware Mobile
9 by synopsys-dw-mshc.txt and the properties used by the Hisilicon specific
15 - "hisilicon,hi3660-dw-mshc": for controllers with hi3660 specific extensions.
17 with hi3670 specific extensions.
18 - "hisilicon,hi4511-dw-mshc": for controllers with hi4511 specific extensions.
19 - "hisilicon,hi6220-dw-mshc": for controllers with hi6220 specific extensions.
|
| H A D | samsung-sdhci.txt | 30 Note: This example shows both SoC specific and board specific properties
32 into SoC specific node and board specific node.
|
| H A D | bluefield-dw-mshc.txt | 1 * Mellanox Bluefield SoC specific extensions to the Synopsys Designware
10 specific extensions to the Synopsys Designware Mobile Storage Host Controller.
16 specific extensions.
|
| /f-stack/freebsd/contrib/device-tree/Bindings/sifive/ |
| H A D | sifive-blocks-ip-versioning.txt | 9 IP block-specific DT compatible strings are contained within the HDL,
26 match on these IP block-specific compatible strings.
29 continue to specify an SoC-specific compatible string value, such as
30 "sifive,fu540-c000-uart". This way, if SoC-specific
31 integration-specific bug fixes or workarounds are needed, the kernel
33 IP block-specific compatible string (such as "sifive,uart0") should
|
| /f-stack/freebsd/contrib/device-tree/Bindings/clock/ti/ |
| H A D | interface.txt | 19 "ti,omap3-hsotgusb-interface-clock" - interface clock with USB specific HW
21 "ti,omap3-dss-interface-clock" - interface clock with DSS specific HW handling
22 "ti,omap3-ssi-interface-clock" - interface clock with SSI specific HW handling
23 "ti,am35xx-interface-clock" - interface clock with AM35xx specific HW handling
24 "ti,omap2430-interface-clock" - interface clock with OMAP2430 specific HW
|
| /f-stack/freebsd/contrib/device-tree/Bindings/arm/freescale/ |
| H A D | fsl,layerscape-scfg.txt | 3 SCFG is the supplemental configuration unit, that provides SoC specific
8 - compatible: Should contain a chip-specific compatible string,
9 Chip-specific strings are of the form "fsl,<chip>-scfg",
|
| /f-stack/freebsd/contrib/device-tree/Bindings/powerpc/fsl/ |
| H A D | mpic.txt | 39 specifiers do not contain the interrupt-type or type-specific
110 type-specific cell is undefined. The
123 the error interrupt. The type-specific
124 cell identifies the specific error
130 the MPIC IPI number. The type-specific
136 the MPIC timer number. The type-specific
139 <4th-cell> type-specific information
141 The type-specific cell is encoded as follows:
144 the type-specific cell contains the
223 * SoC interrupt number is 16 and the specific error
|
| /f-stack/dpdk/doc/guides/howto/ |
| H A D | vfd.rst | 178 for a specific VF port.
196 The IXGBE specific VFd functions
221 a specific VF::
233 specific VF::
247 a specific VF::
258 for a specific VF::
280 The I40E specific VFd functions
312 receiving for a specific VF::
321 promiscuous mode for a specific VF::
339 specific VF::
[all …]
|
| /f-stack/freebsd/contrib/device-tree/Bindings/net/nfc/ |
| H A D | nfcmrvl.txt | 9 Optional SoC specific properties:
15 Optional UART-based chip specific properties:
17 - break-control: Specifies that the chip needs specific break management.
19 Optional I2C-based chip specific properties:
|
| /f-stack/freebsd/contrib/device-tree/Bindings/arm/ |
| H A D | ste-u300.txt | 3 For various board the "board" node may contain specific properties
4 that pertain to this particular board, such as board-specific GPIOs
21 This contains the board-specific information.
|
| /f-stack/freebsd/contrib/device-tree/Bindings/usb/ |
| H A D | omap-usb.txt | 7 multipoint. This is a MUSB configuration-specific setting.
9 MUSB configuration-specific setting. Should be set to "16"
11 - interface-type : This is a board specific setting to describe the type of
27 SOC specific device node entry
39 Board specific device node entry
|
| /f-stack/dpdk/doc/guides/contributing/ |
| H A D | design.rst | 7 Environment or Architecture-specific Sources
11 As far as is possible, all such instances of architecture or env-specific code should be provided v…
13 By convention, a file is common if it is not located in a directory indicating that it is specific.
14 For instance, a file located in a subdir of "x86_64" directory is specific to this architecture.
15 A file located in a subdir of "linux" is specific to this execution environment.
20 The correct location for architecture or executive environment specific code is in the EAL.
22 When absolutely necessary, there are several ways to handle specific code:
36 …this case, the code is split into two separate files that are architecture or environment specific.
116 allocated/freed, number of occurrences for specific events, etc.
125 Library-level statistics counters can be relevant or not for specific
[all …]
|
| /f-stack/freebsd/contrib/device-tree/Bindings/clock/ |
| H A D | lpc1850-ccu.txt | 23 from the CGU to the specific CCU. See mapping of base clocks
27 from the CGU to the specific CCU. Valid CCU clock names:
36 specific LPC part. Check the user manual for your specific part.
|
| /f-stack/freebsd/contrib/device-tree/Bindings/i2c/ |
| H A D | i2c-opal.txt | 4 Most of the device node and properties layout is specific to the firmware and
12 - ibm,opal-id: Refers to a specific bus and used to identify it when calling
22 and depend on the specific hardware implementation. The example below depicts
|
| /f-stack/freebsd/contrib/device-tree/Bindings/power/supply/ab8500/ |
| H A D | btemp.txt | 7 - battery = Shall be battery specific information
15 For information on battery specific node, Ref:
|
| H A D | chargalg.txt | 7 - battery = Shall be battery specific information
15 For information on battery specific node, Ref:
|
| H A D | charger.txt | 5 - battery = Shall be battery specific information
24 For information on battery specific node, Ref:
|
| /f-stack/freebsd/contrib/device-tree/Bindings/pinctrl/ |
| H A D | pinctrl-mt8183.txt | 65 For I2C pins, there are existing generic driving setup and the specific
67 adjustment in generic driving setup. But in specific driving setup,
68 they can support 0.125/0.25/0.5/1mA adjustment. If we enable specific
70 disabled. For some special features, we need the I2C pins specific
71 driving setup. The specific driving setup is controlled by E1E0EN.
74 We can add "mediatek,drive-strength-adv = <XXX>;" to describe the specific
76 It is used to enable or disable the specific driving setup.
|
| /f-stack/freebsd/contrib/device-tree/Bindings/display/hisilicon/ |
| H A D | dw-dsi.txt | 17 A example of HiKey board hi6220 SoC and board specific DT entry:
20 SoC specific:
43 Board specific:
|
| /f-stack/freebsd/contrib/device-tree/Bindings/display/bridge/ |
| H A D | analogix_dp.txt | 5 platform specific such as:
30 -port@[X]: SoC specific port nodes with endpoint definitions as defined
32 please refer to the SoC specific binding document:
|
| /f-stack/dpdk/doc/guides/freebsd_gsg/ |
| H A D | freebsd_eal_parameters.rst | 17 FreeBSD-specific EAL parameters
20 There are currently no FreeBSD-specific EAL command-line parameters available.
|
| /f-stack/dpdk/doc/guides/sample_app_ug/ |
| H A D | ip_pipeline.rst | 414 Display statistics for specific pipeline input port, output port
421 Enable given input port for specific pipeline instance ::
425 Disable given input port for specific pipeline instance ::
429 Add default rule to table for specific pipeline instance ::
441 Add rule to table for specific pipeline instance ::
505 Add bulk rules to table for specific pipeline instance ::
513 Delete table rule for specific pipeline instance ::
518 Delete default table rule for specific pipeline instance ::
524 Add meter profile to the table for specific pipeline instance ::
550 Enable given pipeline instance for specific data plane thread ::
[all …]
|
| /f-stack/dpdk/doc/guides/prog_guide/ |
| H A D | power_man.rst | 86 * **Freq up**: Prompt the kernel to scale up the frequency of the specific lcore.
88 * **Freq down**: Prompt the kernel to scale down the frequency of the specific lcore.
90 * **Freq max**: Prompt the kernel to scale up the frequency of the specific lcore to the maximum.
92 * **Freq min**: Prompt the kernel to scale down the frequency of the specific lcore to the minimu…
94 * **Get available freqs**: Read the available frequencies of the specific lcore from the sys file.
96 * **Freq get**: Get the current frequency of the specific lcore.
98 * **Freq set**: Prompt the kernel to set the frequency for the specific lcore.
100 * **Enable turbo**: Prompt the kernel to enable Turbo Boost for the specific lcore.
102 * **Disable turbo**: Prompt the kernel to disable Turbo Boost for the specific lcore.
|