Searched full:functional (Results 1 – 25 of 1020) sorted by relevance
12345678910>>...41
| /kernel/linux/linux-4.19/include/uapi/linux/usb/ |
| D | cdc.h | 62 /* "Header Functional Descriptor" from CDC spec 5.2.3.1 */
100 /* "Union Functional Descriptor" from CDC spec 5.2.3.8 */
111 /* "Country Selection Functional Descriptor" from CDC spec 5.2.3.9 */
122 /* "Network Channel Terminal Functional Descriptor" from CDC spec 5.2.3.11 */
134 /* "Ethernet Networking Functional Descriptor" from CDC spec 5.2.3.16 */
147 /* "Telephone Control Model Functional Descriptor" from CDC WMC spec 6.3..3 */
156 /* "MDLM Functional Descriptor" from CDC WMC spec 6.7.2.3 */
166 /* "MDLM Detail Functional Descriptor" from CDC WMC spec 6.7.2.4 */
177 /* "OBEX Control Model Functional Descriptor" */
186 /* "NCM Control Model Functional Descriptor" */
[all …]
|
| /kernel/linux/linux-5.10/include/uapi/linux/usb/ |
| D | cdc.h | 62 /* "Header Functional Descriptor" from CDC spec 5.2.3.1 */
100 /* "Union Functional Descriptor" from CDC spec 5.2.3.8 */
111 /* "Country Selection Functional Descriptor" from CDC spec 5.2.3.9 */
122 /* "Network Channel Terminal Functional Descriptor" from CDC spec 5.2.3.11 */
134 /* "Ethernet Networking Functional Descriptor" from CDC spec 5.2.3.16 */
147 /* "Telephone Control Model Functional Descriptor" from CDC WMC spec 6.3..3 */
156 /* "MDLM Functional Descriptor" from CDC WMC spec 6.7.2.3 */
166 /* "MDLM Detail Functional Descriptor" from CDC WMC spec 6.7.2.4 */
177 /* "OBEX Control Model Functional Descriptor" */
186 /* "NCM Control Model Functional Descriptor" */
[all …]
|
| /kernel/linux/linux-5.10/Documentation/networking/device_drivers/ethernet/marvell/ |
| D | octeontx2.rst | 20 resources from the network, crypto and other functional blocks into
21 PCI-compatible physical and virtual functions. Each functional block
25 and has privileges to provision RVU functional block's LFs to each of the
28 RVU managed networking functional blocks
35 RVU managed non-networking functional blocks
45 RVU functional blocks are highly configurable as per software requirements.
64 supports resource provisioning and configuration of functional blocks.
|
| /kernel/linux/linux-4.19/Documentation/arm/Marvell/ |
| D | README | 40 …Functional Spec: http://www.marvell.com/embedded-processors/kirkwood/assets/FS_88F6180_9x_6281_Ope…
44 …Functional Spec: http://www.marvell.com/embedded-processors/kirkwood/assets/FS_88F6180_9x_6281_Ope…
49 …Functional Spec: http://www.marvell.com/embedded-processors/kirkwood/assets/FS_88F6180_9x_6281_Ope…
53 …Functional Spec: http://www.marvell.com/embedded-processors/kirkwood/assets/FS_88F6180_9x_6281_Ope…
66 …Functional Spec: http://www.marvell.com/embedded-processors/discovery-innovation/assets/FS_MV76100…
70 …Functional Spec: http://www.marvell.com/embedded-processors/discovery-innovation/assets/FS_MV76100…
88 …Functional Spec: http://www.marvell.com/embedded-processors/armada-300/assets/ARMADA370-Functional…
101 … Functional Spec: https://marvellcorp.wufoo.com/forms/marvell-armada-38x-functional-specifications/
116 …Functional Spec: http://www.marvell.com/embedded-processors/armada-xp/assets/ARMADA-XP-Functional-…
191 …Functional Spec : http://www.marvell.com/application-processors/armada-500/assets/Armada-510-Funct…
|
| /kernel/linux/linux-5.10/include/linux/ |
| D | nubus.h | 68 /* The functional resource ID */
77 /* Functional directory */
83 /* This is all NuBus functional resources (used to find devices later on) */
135 /* The root directory which contains the board and functional
142 /* The functional directory */
|
| /kernel/linux/linux-4.19/include/linux/ |
| D | nubus.h | 68 /* The functional resource ID */
77 /* Functional directory */
83 /* This is all NuBus functional resources (used to find devices later on) */
135 /* The root directory which contains the board and functional
142 /* The functional directory */
|
| /kernel/linux/linux-5.10/Documentation/arm/ |
| D | marvel.rst | 49 …- Functional Spec: http://www.marvell.com/embedded-processors/kirkwood/assets/FS_88F6180_9x_6281_O…
54 …- Functional Spec: http://www.marvell.com/embedded-processors/kirkwood/assets/FS_88F6180_9x_6281_O…
60 …- Functional Spec: http://www.marvell.com/embedded-processors/kirkwood/assets/FS_88F6180_9x_6281_O…
65 …- Functional Spec: http://www.marvell.com/embedded-processors/kirkwood/assets/FS_88F6180_9x_6281_O…
83 …- Functional Spec: http://www.marvell.com/embedded-processors/discovery-innovation/assets/FS_MV761…
88 …- Functional Spec: http://www.marvell.com/embedded-processors/discovery-innovation/assets/FS_MV761…
111 …- Functional Spec: http://www.marvell.com/embedded-processors/armada-300/assets/ARMADA370-Function…
130 …- Functional Spec: https://marvellcorp.wufoo.com/forms/marvell-armada-38x-functional-specification…
155 Functional Spec:
156 http://www.marvell.com/embedded-processors/armada-xp/assets/ARMADA-XP-Functional-SpecDatasheet.pdf
[all …]
|
| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/bus/ |
| D | renesas,bsc.txt | 10 domain, and may have a gateable functional clock.
12 containing the BSC must be powered on, and the functional clock
30 - clocks: Must contain a reference to the functional clock, if available.
|
| D | simple-pm-bus.txt | 8 functional clock. Hence, the bus controller's PM domain and/or clock must be
26 - clocks: Must contain a reference to the functional clock(s),
|
| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/display/ |
| D | renesas,du.txt | 27 - R8A7779 uses a single functional clock. The clock doesn't need to be
29 - All other DU instances use one functional clock per channel The
30 functional clocks must be named "du.x" with "x" being the channel
32 - In addition to the functional clocks, all DU versions also support
|
| /kernel/linux/linux-5.10/arch/arm/mach-mmp/ |
| D | regs-apbc.h | 13 #define APBC_FNCLK (1 << 1) /* Functional Clock Enable */
16 /* Functional Clock Selection Mask */
|
| /kernel/linux/linux-4.19/arch/arm/mach-mmp/ |
| D | regs-apbc.h | 16 #define APBC_FNCLK (1 << 1) /* Functional Clock Enable */
19 /* Functional Clock Selection Mask */
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/clock/ti/ |
| D | dra7-atl.txt | 5 functional clock but can be configured to provide different clocks.
25 - clocks : link phandles to functional clock of ATL
35 - clocks : link phandles to functional clock of ATL
|
| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/clock/ti/ |
| D | dra7-atl.txt | 5 functional clock but can be configured to provide different clocks.
25 - clocks : link phandles to functional clock of ATL
35 - clocks : link phandles to functional clock of ATL
|
| /kernel/linux/linux-5.10/arch/arm/mach-omap2/ |
| D | cm33xx.c | 35 * 0x0 func: Module is fully functional, including OCP
38 * 0x2 idle: Module is in Idle mode (only OCP part). It is functional if
39 * using separate functional clock
108 * *FUNCTIONAL or *INTERFACE_IDLE; false otherwise.
224 * Wait for the module IDLEST to be functional. If the idle state is in any
225 * the non functional state (trans, idle or disabled), module and thus the
|
| /kernel/linux/linux-4.19/arch/arm/mach-omap2/ |
| D | cm33xx.c | 35 * 0x0 func: Module is fully functional, including OCP
38 * 0x2 idle: Module is in Idle mode (only OCP part). It is functional if
39 * using separate functional clock
108 * *FUNCTIONAL or *INTERFACE_IDLE; false otherwise.
224 * Wait for the module IDLEST to be functional. If the idle state is in any
225 * the non functional state (trans, idle or disabled), module and thus the
|
| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/crypto/ |
| D | omap-des.txt | 9 - clocks : A phandle to the functional clock node of the DES module
11 - clock-names : Name of the functional clock, should be "fck"
|
| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/rtc/ |
| D | rtc-sh.txt | 10 - clocks: The functional clock source for the RTC controller must be listed
13 - clock-names: The functional clock must be labeled as "fck". Other clocks
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/crypto/ |
| D | omap-des.txt | 9 - clocks : A phandle to the functional clock node of the DES module
11 - clock-names : Name of the functional clock, should be "fck"
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/pwm/ |
| D | pwm-rockchip.txt | 12 - There is one clock that's used both to derive the functional clock
15 - "pwm": This is used to derive the functional clock.
|
| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/pwm/ |
| D | pwm-rockchip.txt | 12 - There is one clock that's used both to derive the functional clock
15 - "pwm": This is used to derive the functional clock.
|
| /kernel/linux/linux-5.10/tools/testing/selftests/futex/ |
| D | run.sh | 9 # Run all tests under the functional, performance, and stress directories.
29 (cd functional; ./run.sh)
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/display/ |
| D | renesas,du.txt | 37 - R8A7779 uses a single functional clock. The clock doesn't need to be
39 - All other DU instances use one functional clock per channel The
40 functional clocks must be named "du.x" with "x" being the channel
42 - In addition to the functional clocks, all DU versions also support
|
| /kernel/linux/linux-4.19/tools/testing/selftests/futex/ |
| D | run.sh | 13 # Run all tests under the functional, performance, and stress directories.
33 (cd functional; ./run.sh)
|
| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/clock/ |
| D | ti-clkctrl.txt | 4 interconnect target module. The clkctrl clock controller manages functional
6 gate one or more optional functional clocks for a module, and can have one
|
12345678910>>...41