Searched refs:functional (Results 1 – 25 of 152) sorted by relevance
1234567
| /Linux-v5.4/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),
|
| /Linux-v5.4/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
|
| /Linux-v5.4/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.4/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.4/Documentation/devicetree/bindings/display/ |
| D | renesas,du.txt | 33 - R8A7779 uses a single functional clock. The clock doesn't need to be
35 - All other DU instances use one functional clock per channel The
36 functional clocks must be named "du.x" with "x" being the channel
38 - In addition to the functional clocks, all DU versions also support
|
| /Linux-v5.4/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.4/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
|
| /Linux-v5.4/tools/testing/selftests/futex/ |
| D | run.sh | 29 (cd functional; ./run.sh)
|
| D | Makefile | 2 SUBDIRS := functional
|
| /Linux-v5.4/Documentation/devicetree/bindings/interrupt-controller/ |
| D | renesas,intc-irqpin.txt | 31 - clocks: Must contain a reference to the functional clock. This property is
32 mandatory if the hardware implements a controllable functional clock for
|
| /Linux-v5.4/Documentation/ABI/testing/ |
| D | debugfs-hisi-zip | 18 Writing to this file has no functional effect, only enable or
48 Writing to this file has no functional effect, only enable or
|
| D | usb-uevent | 6 longer functional a uevent will be raised. The uevent will
|
| /Linux-v5.4/drivers/staging/octeon-usb/ |
| D | TODO | 1 This driver is functional and has been tested on EdgeRouter Lite,
|
| /Linux-v5.4/drivers/staging/octeon/ |
| D | TODO | 1 This driver is functional and supports Ethernet on OCTEON+/OCTEON2/OCTEON3
|
| /Linux-v5.4/Documentation/devicetree/bindings/i2c/ |
| D | i2c-rk3x.txt | 20 - There is one clock that's used both to derive the functional clock
23 - "i2c": This is used to derive the functional clock.
|
| /Linux-v5.4/Documentation/devicetree/bindings/timer/ |
| D | renesas,tpu.txt | 12 - clock-names: must contain "peripheral_clk" for the functional clock.
|
| D | renesas,16bit-timer.txt | 12 - clock-names: must contain "peripheral_clk" for the functional clock.
|
| D | renesas,8bit-timer.txt | 14 - clock-names: must contain "fck" for the functional clock.
|
| /Linux-v5.4/Documentation/devicetree/bindings/usb/ |
| D | brcm,bdc.txt | 19 - clocks: phandle to the functional clock of this block
|
| /Linux-v5.4/Documentation/devicetree/bindings/rng/ |
| D | ks-sa-rng.txt | 9 - clock-names: functional clock name. Should be set to "fck"
|
| /Linux-v5.4/Documentation/devicetree/bindings/ata/ |
| D | ahci-dm816.txt | 11 #clock-cells); two clocks must be specified: the functional
|
| /Linux-v5.4/Documentation/driver-api/ |
| D | interconnect.rst | 12 latency and priority between multiple interconnected devices or functional
19 components or functional blocks in chipsets. There can be multiple interconnects
|
| /Linux-v5.4/Documentation/openrisc/ |
| D | todo.rst | 5 The OpenRISC Linux port is fully functional and has been tracking upstream
|
| /Linux-v5.4/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
|
1234567
