Home
last modified time | relevance | path

Searched refs:functional (Results 1 – 25 of 172) sorted by relevance

1234567

/linux/Documentation/devicetree/bindings/crypto/
A 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/Documentation/devicetree/bindings/clock/ti/
A 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/Documentation/devicetree/bindings/rtc/
A 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/Documentation/devicetree/bindings/pwm/
A Dpwm-rockchip.yaml68 - description: Used to derive the functional clock for the device.
85 Used both to derive the functional clock
/linux/Documentation/networking/device_drivers/ethernet/marvell/
A Docteontx2.rst21 resources from the network, crypto and other functional blocks into
22 PCI-compatible physical and virtual functions. Each functional block
26 and has privileges to provision RVU functional block's LFs to each of the
29 RVU managed networking functional blocks
36 RVU managed non-networking functional blocks
46 RVU functional blocks are highly configurable as per software requirements.
65 supports resource provisioning and configuration of functional blocks.
/linux/Documentation/devicetree/bindings/bus/
A 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
/linux/Documentation/devicetree/bindings/mtd/
A Dpartition.txt4 Flash devices can be partitioned into one or more functional ranges (e.g. "boot
9 the geometry and naming/purpose of each functional region. It is also possible
/linux/Documentation/devicetree/bindings/net/
A Dbrcm,systemport.txt23 - 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
A Dbrcm,bcmgenet.txt19 - clocks: When provided, must be two phandles to the functional clocks nodes
22 - clock-names: When provided, names of the functional clock phandles, first
/linux/Documentation/devicetree/bindings/clock/
A 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/tools/testing/selftests/futex/
A Drun.sh29 (cd functional; ./run.sh)
A DMakefile2 SUBDIRS := functional
/linux/drivers/staging/octeon-usb/
A DTODO1 This driver is functional and has been tested on EdgeRouter Lite,
/linux/drivers/staging/octeon/
A DTODO1 This driver is functional and supports Ethernet on OCTEON+/OCTEON2/OCTEON3
/linux/Documentation/devicetree/bindings/i2c/
A Di2c-rk3x.yaml53 there is one clock that is used both to derive the functional clock
56 the functional clock
/linux/Documentation/openrisc/
A Dopenrisc_port.rst105 fully functional sash-3.6 in default initrd.
110 ethernet support, functional http and telnet servers.
A Dtodo.rst5 The OpenRISC Linux port is fully functional and has been tracking upstream
/linux/Documentation/devicetree/bindings/thermal/
A Dexynos-thermal.txt35 -- 3. optional special clock for functional operation
40 -- "tmu_sclk" clock for functional operation of the current TMU
/linux/Documentation/devicetree/bindings/timer/
A Drenesas,16bit-timer.txt12 - clock-names: must contain "peripheral_clk" for the functional clock.
A Drenesas,8bit-timer.txt14 - clock-names: must contain "fck" for the functional clock.
/linux/Documentation/devicetree/bindings/ata/
A Dahci-dm816.txt11 #clock-cells); two clocks must be specified: the functional
/linux/Documentation/devicetree/bindings/rng/
A Dks-sa-rng.txt9 - clock-names: functional clock name. Should be set to "fck"
/linux/Documentation/devicetree/bindings/usb/
A Dbrcm,bdc.txt19 - clocks: phandle to the functional clock of this block
/linux/Documentation/ABI/testing/
A Dusb-uevent6 longer functional a uevent will be raised. The uevent will
/linux/Documentation/driver-api/
A Dinterconnect.rst12 latency and priority between multiple interconnected devices or functional
19 components or functional blocks in chipsets. There can be multiple interconnects

Completed in 9 milliseconds

1234567