Searched full:functional (Results 1 – 25 of 536) sorted by relevance
12345678910>>...22
| /Linux-v5.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 …]
|
| /Linux-v5.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.
|
| /Linux-v5.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 …]
|
| /Linux-v5.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 */
|
| D | posix-clock.h | 19 * struct posix_clock_operations - functional interface to the clock
70 * @ops: Functional interface to the clock
|
| /Linux-v5.10/arch/arm/mach-mmp/ |
| D | regs-apbc.h | 13 #define APBC_FNCLK (1 << 1) /* Functional Clock Enable */
16 /* Functional Clock Selection Mask */
|
| /Linux-v5.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
|
| /Linux-v5.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
|
| D | cminst44xx.c | 42 * 0x0 func: Module is fully functional, including OCP
45 * 0x2 idle: Module is in Idle mode (only OCP part). It is functional if
46 * using separate functional clock
100 * *FUNCTIONAL or *INTERFACE_IDLE; false otherwise.
269 * Wait for the module IDLEST to be functional. If the idle state is in any
270 * the non functional state (trans, idle or disabled), module and thus the
|
| /Linux-v5.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"
|
| /Linux-v5.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.
|
| /Linux-v5.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
|
| /Linux-v5.10/tools/testing/selftests/futex/ |
| D | run.sh | 9 # Run all tests under the functional, performance, and stress directories.
29 (cd functional; ./run.sh)
|
| /Linux-v5.10/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
|
| D | renesas,rcar-usb2-clock-sel.txt | 43 - The functional clock of USB 2.0 host side must be "ehci_ohci"
44 - The functional clock of HS-USB side must be "hs-usb-if"
|
| /Linux-v5.10/Documentation/devicetree/bindings/bus/ |
| D | renesas,bsc.yaml | 19 PM domain, and may have a gateable functional clock. Before a device
21 must be powered on, and the functional clock driving the BSC must be
|
| D | simple-pm-bus.yaml | 17 of a functional clock. Hence, the bus controller's PM domain and/or
45 # Functional clocks
|
| /Linux-v5.10/Documentation/devicetree/bindings/net/ |
| D | brcm,systemport.txt | 23 - clocks: When provided, must be two phandles to the functional clocks nodes of
26 - clock-names: When provided, names of the functional clock phandles, first
|
| /Linux-v5.10/Documentation/devicetree/bindings/rtc/ |
| D | renesas,sh-rtc.yaml | 32 # The functional clock source for the RTC controller must be listed
39 # The functional clock must be labeled as "fck". Other clocks
|
| /Linux-v5.10/arch/mips/dec/ |
| D | wbflush.c | 5 * DECstation 3100 Desktop Workstation Functional Specification
6 * DECstation 5000/200 KN02 System Module Functional Specification
|
| /Linux-v5.10/Documentation/admin-guide/media/ |
| D | davinci-vpbe.rst | 6 Functional partitioning
64 A fully functional working version of the V4L2 driver is available. This
|
| /Linux-v5.10/include/clocksource/ |
| D | hyperv_timer.h | 6 * Level Functional Spec (TLFS).
46 * Top-Level Functional Specification ver. 3.0 and above. To get the in hv_read_tsc_page_tsc()
|
| /Linux-v5.10/Documentation/devicetree/bindings/thermal/ |
| D | exynos-thermal.txt | 35 -- 3. optional special clock for functional operation
40 -- "tmu_sclk" clock for functional operation of the current TMU
|
| /Linux-v5.10/drivers/clk/ |
| D | clk-twl6040.c | 3 * TWL6040 clock module driver for OMAP4 McPDM functional clock
159 MODULE_DESCRIPTION("TWL6040 clock driver for McPDM functional clock");
|
| /Linux-v5.10/Documentation/devicetree/bindings/i2c/ |
| D | i2c-rk3x.yaml | 52 there is one clock that is used both to derive the functional clock
55 the functional clock
|
12345678910>>...22
