Home
last modified time | relevance | path

Searched full:functional (Results 1 – 25 of 654) sorted by relevance

12345678910>>...27

/linux-6.12.1/Documentation/devicetree/bindings/display/
Drenesas,du.yaml114 - description: Functional clock
162 - description: Functional clock for DU0
163 - description: Functional clock for DU1
217 - description: Functional clock for DU0
218 - description: Functional clock for DU1
270 - description: Functional clock for DU0
271 - description: Functional clock for DU1
324 - description: Functional clock for DU0
325 - description: Functional clock for DU1
381 - description: Functional clock for DU0
[all …]
/linux-6.12.1/include/uapi/linux/usb/
Dcdc.h62 /* "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-6.12.1/include/linux/
Dnubus.h68 /* The functional resource ID */
77 /* Functional directory */
83 /* This is all NuBus functional resources (used to find devices later on) */
134 /* The root directory which contains the board and functional
141 /* The functional directory */
/linux-6.12.1/Documentation/usb/
Dfunctionfs-desc.rst30 DFU Functional Descriptor
34 is USB_SUBCLASS_DFU, a DFU functional descriptor can be provided.
35 The DFU functional descriptor is a described in the USB specification for
/linux-6.12.1/Documentation/arch/arm/
Dmarvell.rst24 …- Functional Errata: https://web.archive.org/web/20210704165540/https://www.digriz.org.uk/ts78xx/8…
52 …- Functional Spec: https://web.archive.org/web/20130730091033/http://www.marvell.com/embedded-proc…
57 …- Functional Spec: https://web.archive.org/web/20130730091033/http://www.marvell.com/embedded-proc…
63 …- Functional Spec: https://web.archive.org/web/20130730091033/http://www.marvell.com/embedded-proc…
71 …- Functional Spec: https://web.archive.org/web/20130730091033/http://www.marvell.com/embedded-proc…
94 …- Functional Spec: https://web.archive.org/web/20111110081125/http://www.marvell.com/embedded-proc…
99 …- Functional Spec: https://web.archive.org/web/20111110081125/http://www.marvell.com/embedded-proc…
105 …- Functional Spec: https://web.archive.org/web/20111110081125/http://www.marvell.com/embedded-proc…
130 …- Functional Spec: https://web.archive.org/web/20140617183701/http://www.marvell.com/embedded-proc…
145 …- Functional Spec: https://web.archive.org/web/20180829171131/http://www.marvell.com/embedded-proc…
[all …]
/linux-6.12.1/Documentation/networking/device_drivers/ethernet/marvell/
Docteontx2.rst22 resources from the network, crypto and other functional blocks into
23 PCI-compatible physical and virtual functions. Each functional block
27 and has privileges to provision RVU functional block's LFs to each of the
30 RVU managed networking functional blocks
37 RVU managed non-networking functional blocks
47 RVU functional blocks are highly configurable as per software requirements.
66 supports resource provisioning and configuration of functional blocks.
/linux-6.12.1/Documentation/devicetree/bindings/clock/ti/
Ddra7-atl.txt5 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-6.12.1/arch/arm/mach-omap2/
Dcm33xx.c27 * 0x0 func: Module is fully functional, including OCP
30 * 0x2 idle: Module is in Idle mode (only OCP part). It is functional if
31 * using separate functional clock
100 * *FUNCTIONAL or *INTERFACE_IDLE; false otherwise.
216 * Wait for the module IDLEST to be functional. If the idle state is in any
217 * the non functional state (trans, idle or disabled), module and thus the
Dcminst44xx.c42 * 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-6.12.1/Documentation/devicetree/bindings/crypto/
Domap-des.txt9 - clocks : A phandle to the functional clock node of the DES module
11 - clock-names : Name of the functional clock, should be "fck"
/linux-6.12.1/tools/testing/selftests/futex/
Drun.sh9 # Run all tests under the functional, performance, and stress directories.
29 (cd functional; ./run.sh)
/linux-6.12.1/Documentation/ABI/testing/
Dconfigfs-usb-gadget-uac136 p_fu_vol_name playback mute/volume functional unit name
40 c_fu_vol_name capture mute/volume functional unit name
/linux-6.12.1/Documentation/devicetree/bindings/clock/
Dti-clkctrl.txt4 interconnect target module. The clkctrl clock controller manages functional
6 gate one or more optional functional clocks for a module, and can have one
/linux-6.12.1/Documentation/devicetree/bindings/bus/
Drenesas,bsc.yaml19 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
Dsimple-pm-bus.yaml17 of a functional clock. Hence, the bus controller's PM domain and/or
45 # Functional clocks
/linux-6.12.1/Documentation/devicetree/bindings/rtc/
Drenesas,sh-rtc.yaml32 # The functional clock source for the RTC controller must be listed
39 # The functional clock must be labeled as "fck". Other clocks
/linux-6.12.1/Documentation/devicetree/bindings/pwm/
Dpwm-rockchip.yaml73 - description: Used to derive the functional clock for the device.
90 Used both to derive the functional clock
/linux-6.12.1/drivers/usb/typec/tcpm/
DKconfig34 Mediatek MT6360 is a multi-functional IC that includes
42 MediaTek MT6370 is a multi-functional IC that includes
/linux-6.12.1/arch/mips/dec/
Dwbflush.c5 * DECstation 3100 Desktop Workstation Functional Specification
6 * DECstation 5000/200 KN02 System Module Functional Specification
/linux-6.12.1/Documentation/devicetree/bindings/display/bridge/
Drenesas,dsi-csi2-tx.yaml28 - description: Functional clock
29 - description: DSI (and CSI-2) functional clock
/linux-6.12.1/Documentation/devicetree/bindings/regulator/
Dregulator.yaml140 is assumed still to be functional but approaching limit where it gets
161 is assumed still to be functional but approaching limit where it gets
183 hardware is assumed still to be functional but approaching limit where
211 hardware is assumed still to be functional but approaching limit where it
/linux-6.12.1/include/clocksource/
Dhyperv_timer.h6 * Level Functional Spec (TLFS).
50 * Top-Level Functional Specification ver. 3.0 and above. To get the in hv_read_tsc_page_tsc()
/linux-6.12.1/drivers/clk/
Dclk-twl6040.c3 * TWL6040 clock module driver for OMAP4 McPDM functional clock
159 MODULE_DESCRIPTION("TWL6040 clock driver for McPDM functional clock");
/linux-6.12.1/drivers/net/fddi/
Ddefxx.c333 * Functional Description:
516 * Functional Description:
704 * Functional Description:
866 * Functional Description:
928 * Functional Description:
1018 * Functional Description:
1235 * Functional Description:
1434 * Functional Description:
1523 * Functional Description:
1615 * Functional Description:
[all …]
/linux-6.12.1/Documentation/devicetree/bindings/i2c/
Di2c-rk3x.yaml57 there is one clock that is used both to derive the functional clock
60 the functional clock

12345678910>>...27