| /Linux-v5.4/arch/arm/boot/dts/ | 
| D | omap3xxx-clocks.dtsi | 3  * Device Tree Source for OMAP3 clock data9 		#clock-cells = <0>;
 10 		compatible = "fixed-clock";
 11 		clock-frequency = <16800000>;
 15 		#clock-cells = <0>;
 16 		compatible = "ti,mux-clock";
 22 		#clock-cells = <0>;
 23 		compatible = "ti,divider-clock";
 32 		#clock-cells = <0>;
 33 		compatible = "ti,gate-clock";
 [all …]
 
 | 
| D | am43xx-clocks.dtsi | 3  * Device Tree Source for AM43xx clock data9 		#clock-cells = <0>;
 10 		compatible = "ti,mux-clock";
 17 		#clock-cells = <0>;
 18 		compatible = "ti,mux-clock";
 25 		#clock-cells = <0>;
 26 		compatible = "ti,mux-clock";
 33 		#clock-cells = <0>;
 34 		compatible = "fixed-factor-clock";
 36 		clock-mult = <1>;
 [all …]
 
 | 
| D | omap24xx-clocks.dtsi | 3  * Device Tree Source for OMAP24xx clock data9 		#clock-cells = <0>;
 10 		compatible = "ti,composite-mux-clock";
 17 		#clock-cells = <0>;
 18 		compatible = "ti,composite-clock";
 23 		#clock-cells = <0>;
 24 		compatible = "ti,composite-mux-clock";
 31 		#clock-cells = <0>;
 32 		compatible = "ti,composite-clock";
 39 		#clock-cells = <0>;
 [all …]
 
 | 
| D | am33xx-clocks.dtsi | 3  * Device Tree Source for AM33xx clock data9 		#clock-cells = <0>;
 10 		compatible = "ti,mux-clock";
 17 		#clock-cells = <0>;
 18 		compatible = "fixed-factor-clock";
 20 		clock-mult = <1>;
 21 		clock-div = <1>;
 25 		#clock-cells = <0>;
 26 		compatible = "fixed-factor-clock";
 28 		clock-mult = <1>;
 [all …]
 
 | 
| D | dra7xx-clocks.dtsi | 3  * Device Tree Source for DRA7xx clock data9 		#clock-cells = <0>;
 10 		compatible = "ti,dra7-atl-clock";
 15 		#clock-cells = <0>;
 16 		compatible = "ti,dra7-atl-clock";
 21 		#clock-cells = <0>;
 22 		compatible = "ti,dra7-atl-clock";
 27 		#clock-cells = <0>;
 28 		compatible = "ti,dra7-atl-clock";
 33 		#clock-cells = <0>;
 [all …]
 
 | 
| D | keystone-clocks.dtsi | 3  * Device Tree Source for Keystone 2 clock tree14 		#clock-cells = <0>;
 15 		compatible = "ti,keystone,pll-mux-clock";
 20 		clock-output-names = "mainmuxclk";
 24 		#clock-cells = <0>;
 25 		compatible = "fixed-factor-clock";
 27 		clock-div = <1>;
 28 		clock-mult = <1>;
 29 		clock-output-names = "chipclk1";
 33 		#clock-cells = <0>;
 [all …]
 
 | 
| D | omap54xx-clocks.dtsi | 3  * Device Tree Source for OMAP5 clock data9 		#clock-cells = <0>;
 10 		compatible = "fixed-clock";
 11 		clock-frequency = <12000000>;
 15 		#clock-cells = <0>;
 16 		compatible = "ti,gate-clock";
 23 		#clock-cells = <0>;
 24 		compatible = "fixed-clock";
 25 		clock-frequency = <32768>;
 29 		#clock-cells = <0>;
 [all …]
 
 | 
| D | dm814x-clocks.dtsi | 10 		#clock-cells = <1>;11 		compatible = "ti,dm814-adpll-s-clock";
 14 		clock-names = "clkinp", "clkinpulow", "clkinphif";
 15 		clock-output-names = "481c5040.adpll.dcoclkldo",
 22 		#clock-cells = <1>;
 23 		compatible = "ti,dm814-adpll-lj-clock";
 26 		clock-names = "clkinp", "clkinpulow";
 27 		clock-output-names = "481c5080.adpll.dcoclkldo",
 33 		#clock-cells = <1>;
 34 		compatible = "ti,dm814-adpll-lj-clock";
 [all …]
 
 | 
| D | ste-nomadik-stn8815.dtsi | 41 		clock-names = "timclk", "apb_pclk";50 		clock-names = "timclk", "apb_pclk";
 199 			#clock-cells = <0>;
 200 			compatible = "fixed-clock";
 201 			clock-frequency = <19200000>;
 205 		 * The 2.4 MHz TIMCLK reference clock is active at
 207 		 * divided by 8. This clock is used by the timers and
 211 			#clock-cells = <0>;
 212 			compatible = "fixed-factor-clock";
 213 			clock-div = <8>;
 [all …]
 
 | 
| D | omap44xx-clocks.dtsi | 3  * Device Tree Source for OMAP4 clock data9 		#clock-cells = <0>;
 10 		compatible = "fixed-clock";
 11 		clock-frequency = <59000000>;
 15 		#clock-cells = <0>;
 16 		compatible = "fixed-clock";
 17 		clock-frequency = <12000000>;
 21 		#clock-cells = <0>;
 22 		compatible = "ti,gate-clock";
 29 		#clock-cells = <0>;
 [all …]
 
 | 
| D | keystone-k2hk-clocks.dtsi | 3  * Keystone 2 Kepler/Hawking SoC clock nodes10 		#clock-cells = <0>;
 11 		compatible = "ti,keystone,pll-clock";
 13 		clock-output-names = "arm-pll-clk";
 19 		#clock-cells = <0>;
 20 		compatible = "ti,keystone,main-pll-clock";
 27 		#clock-cells = <0>;
 28 		compatible = "ti,keystone,pll-clock";
 30 		clock-output-names = "papllclk";
 36 		#clock-cells = <0>;
 [all …]
 
 | 
| D | exynos5410.dtsi | 14 #include <dt-bindings/clock/exynos5410.h>15 #include <dt-bindings/clock/exynos-audss-clk.h>
 37 			clock-frequency = <1600000000>;
 44 			clock-frequency = <1600000000>;
 51 			clock-frequency = <1600000000>;
 58 			clock-frequency = <1600000000>;
 71 			clock-names = "clkout16";
 73 			#clock-cells = <1>;
 76 		clock: clock-controller@10010000 {  label
 77 			compatible = "samsung,exynos5410-clock";
 [all …]
 
 | 
| /Linux-v5.4/Documentation/devicetree/bindings/clock/ | 
| D | lpc1850-cgu.txt | 1 * NXP LPC1850 Clock Generation Unit (CGU)4 peripheral blocks of the LPC18xx. Each independent clock is called
 5 a base clock and itself is one of the inputs to the two Clock
 9 The CGU selects the inputs to the clock generators from multiple
 10 clock sources, controls the clock generation, and routes the outputs
 11 of the clock generators through the clock source bus to the output
 12 stages. Each output stage provides an independent clock source and
 18 This binding uses the common clock binding:
 19     Documentation/devicetree/bindings/clock/clock-bindings.txt
 26 	containing clock control registers
 [all …]
 
 | 
| D | mvebu-core-clock.txt | 1 * Core Clock bindings for Marvell MVEBU SoCs3 Marvell MVEBU SoCs usually allow to determine core clock frequencies by
 4 reading the Sample-At-Reset (SAR) register. The core clock consumer should
 5 specify the desired clock by having the clock ID in its "clocks" phandle cell.
 7 The following is a list of provided IDs and clock names on Armada 370/XP:
 8  0 = tclk    (Internal Bus clock)
 9  1 = cpuclk  (CPU clock)
 10  2 = nbclk   (L2 Cache clock)
 11  3 = hclk    (DRAM control clock)
 12  4 = dramclk (DDR clock)
 [all …]
 
 | 
| D | clock-bindings.txt | 4 Sources of clock signal can be represented by any node in the device5 tree.  Those nodes are designated as clock providers.  Clock consumer
 6 nodes use a phandle and clock specifier pair to connect clock provider
 7 outputs to clock inputs.  Similar to the gpio specifiers, a clock
 8 specifier is an array of zero, one or more cells identifying the clock
 9 output on a device.  The length of a clock specifier is defined by the
 10 value of a #clock-cells property in the clock provider node.
 14 ==Clock providers==
 17 #clock-cells:	   Number of cells in a clock specifier; Typically 0 for nodes
 18 		   with a single clock output and 1 for nodes with multiple
 [all …]
 
 | 
| D | exynos5260-clock.txt | 1 * Samsung Exynos5260 Clock Controller3 Exynos5260 has 13 clock controllers which are instantiated
 4 independently from the device-tree. These clock controllers
 8 Each clock is assigned an identifier and client nodes can use
 9 this identifier to specify the clock which they consume. All
 11 dt-bindings/clock/exynos5260-clk.h header and can be used in
 17 is expected that they are defined using standard clock bindings
 18 with following clock-output-names:
 20  - "fin_pll" - PLL input clock from XXTI
 21  - "xrtcxti" - input clock from XRTCXTI
 [all …]
 
 | 
| D | imx8mn-clock.yaml | 4 $id: http://devicetree.org/schemas/bindings/clock/imx8mn-clock.yaml#7 title: NXP i.MX8M Nano Clock Control Module Binding
 13   NXP i.MX8M Nano clock control module is an integrated clock controller, which
 27       - description: ext1 clock input
 28       - description: ext2 clock input
 29       - description: ext3 clock input
 30       - description: ext4 clock input
 32   clock-names:
 41   '#clock-cells':
 44       The clock consumer should specify the desired clock by having the clock
 [all …]
 
 | 
| D | exynos5433-clock.txt | 1 * Samsung Exynos5433 CMU (Clock Management Units)3 The Exynos5433 clock controller generates and supplies clock to various
 9   - "samsung,exynos5433-cmu-top"   - clock controller compatible for CMU_TOP
 12   - "samsung,exynos5433-cmu-cpif"  - clock controller compatible for CMU_CPIF
 14   - "samsung,exynos5433-cmu-mif"   - clock controller compatible for CMU_MIF
 16   - "samsung,exynos5433-cmu-peric" - clock controller compatible for CMU_PERIC
 18   - "samsung,exynos5433-cmu-peris" - clock controller compatible for CMU_PERIS
 20   - "samsung,exynos5433-cmu-fsys"  - clock controller compatible for CMU_FSYS
 22   - "samsung,exynos5433-cmu-g2d"   - clock controller compatible for CMU_G2D
 24   - "samsung,exynos5433-cmu-disp"  - clock controller compatible for CMU_DISP
 [all …]
 
 | 
| D | exynos4-clock.txt | 1 * Samsung Exynos4 Clock Controller3 The Exynos4 clock controller generates and supplies clock to various controllers
 4 within the Exynos4 SoC. The clock binding described here is applicable to all
 10   - "samsung,exynos4210-clock" - controller compatible with Exynos4210 SoC.
 11   - "samsung,exynos4412-clock" - controller compatible with Exynos4412 SoC.
 16 - #clock-cells: should be 1.
 18 Each clock is assigned an identifier and client nodes can use this identifier
 19 to specify the clock which they consume.
 22 dt-bindings/clock/exynos4.h header and can be used in device
 25 Example 1: An example of a clock controller node is listed below.
 [all …]
 
 | 
| D | xgene.txt | 1 Device Tree Clock bindings for APM X-Gene3 This binding uses the common clock binding[1].
 5 [1] Documentation/devicetree/bindings/clock/clock-bindings.txt
 9 	"apm,xgene-socpll-clock" - for a X-Gene SoC PLL clock
 10 	"apm,xgene-pcppll-clock" - for a X-Gene PCP PLL clock
 11 	"apm,xgene-pmd-clock" - for a X-Gene PMD clock
 12 	"apm,xgene-device-clock" - for a X-Gene device clock
 13 	"apm,xgene-socpll-v2-clock" - for a X-Gene SoC PLL v2 clock
 14 	"apm,xgene-pcppll-v2-clock" - for a X-Gene PCP PLL v2 clock
 17 - reg : shall be the physical PLL register address for the pll clock.
 [all …]
 
 | 
| D | pistachio-clock.txt | 1 Imagination Technologies Pistachio SoC clock controllers4 Pistachio has four clock controllers (core clock, peripheral clock, peripheral
 11 There are three external inputs to the clock controllers which should be
 12 defined with the following clock-output-names:
 14 - "audio_clk_in": Alternate audio reference clock (optional)
 15 - "enet_clk_in": Alternate ethernet PHY clock (optional)
 17 Core clock controller:
 20 The core clock controller generates clocks for the CPU, RPU (WiFi + BT
 25 - reg: Must contain the base address and length of the core clock controller.
 26 - #clock-cells: Must be 1.  The single cell is the clock identifier.
 [all …]
 
 | 
| D | nuvoton,npcm750-clk.txt | 1 * Nuvoton NPCM7XX Clock Controller3 Nuvoton Poleg BMC NPCM7XX contains an integrated clock controller, which
 10 clk_sysbypck are inputs to the clock controller.
 12 network. They are set on the device tree, but not used by the clock module. The
 17 dt-bindings/clock/nuvoton,npcm7xx-clock.h
 20 Required Properties of clock controller:
 22 	- compatible: "nuvoton,npcm750-clk" : for clock controller of Nuvoton
 25 	- reg: physical base address of the clock controller and length of
 28 	- #clock-cells: should be 1.
 30 Example: Clock controller node:
 [all …]
 
 | 
| D | samsung,s3c64xx-clock.txt | 1 * Samsung S3C64xx Clock Controller3 The S3C64xx clock controller generates and supplies clock to various controllers
 4 within the SoC. The clock binding described here is applicable to all SoCs in
 10   - "samsung,s3c6400-clock" - controller compatible with S3C6400 SoC.
 11   - "samsung,s3c6410-clock" - controller compatible with S3C6410 SoC.
 16 - #clock-cells: should be 1.
 18 Each clock is assigned an identifier and client nodes can use this identifier
 19 to specify the clock which they consume. Some of the clocks are available only
 23 dt-bindings/clock/samsung,s3c64xx-clock.h header and can be used in device
 29 that they are defined using standard clock bindings with following
 [all …]
 
 | 
| /Linux-v5.4/drivers/net/ethernet/mellanox/mlx5/core/lib/ | 
| D | clock.c | 38 #include "clock.h"71 	struct mlx5_clock *clock = container_of(cc, struct mlx5_clock, cycles);  in read_internal_timer()  local
 72 	struct mlx5_core_dev *mdev = container_of(clock, struct mlx5_core_dev,  in read_internal_timer()
 73 						  clock);  in read_internal_timer()
 81 	struct mlx5_clock *clock = &mdev->clock;  in mlx5_update_clock_info_page()  local
 91 	clock_info->cycles = clock->tc.cycle_last;  in mlx5_update_clock_info_page()
 92 	clock_info->mult   = clock->cycles.mult;  in mlx5_update_clock_info_page()
 93 	clock_info->nsec   = clock->tc.nsec;  in mlx5_update_clock_info_page()
 94 	clock_info->frac   = clock->tc.frac;  in mlx5_update_clock_info_page()
 104 	struct mlx5_clock *clock = container_of(pps_info, struct mlx5_clock,  in mlx5_pps_out()  local
 [all …]
 
 | 
| /Linux-v5.4/Documentation/devicetree/bindings/clock/ti/ | 
| D | gate.txt | 1 Binding for Texas Instruments gate clock.5 This binding uses the common clock binding[1]. This clock is
 6 quite much similar to the basic gate-clock [2], however,
 8 is provided for this clock, the code assumes that a clockdomain
 12 [1] Documentation/devicetree/bindings/clock/clock-bindings.txt
 13 [2] Documentation/devicetree/bindings/clock/gpio-gate-clock.txt
 14 [3] Documentation/devicetree/bindings/clock/ti/clockdomain.txt
 18   "ti,gate-clock" - basic gate clock
 19   "ti,wait-gate-clock" - gate clock which waits until clock is active before
 21   "ti,dss-gate-clock" - gate clock with DSS specific hardware handling
 [all …]
 
 |