arch/arm/boot/dts/ti/omap/dra62x-clocks.dtsi

File Facts

System

Linux kernel

Corpus path

arch/arm/boot/dts/ti/omap/dra62x-clocks.dtsi

Extension

.dtsi

Size

920 bytes

Lines

46

Domain

Architecture Layer

Bucket

arch/arm

Inferred role

Architecture Layer: configuration, schema, or hardware description

Status

atlas-only

Why This File Exists

CPU and platform-specific kernel glue: boot entry, traps, syscall entry, interrupts, page tables, context switch, and low-level barriers.

• CPU and platform-specific kernel glue: boot entry, traps, syscall entry, interrupts, page tables, context switch, and low-level barriers.

Dependency Surface

• dm814x-clocks.dtsi

Detected Declarations

• No top-level syscall, struct, function, initcall, or export declaration detected by the generator.

Annotated Snippet

// SPDX-License-Identifier: GPL-2.0-only

#include "dm814x-clocks.dtsi"

/* Compared to dm814x, dra62x does not have hdic, l3 or dss PLLs */
&adpll_hdvic_ck {
	status = "disabled";
};

&adpll_l3_ck {
	status = "disabled";
};

&adpll_dss_ck {
	status = "disabled";
};

/* Compared to dm814x, dra62x has interconnect clocks on isp PLL */
&sysclk4_ck {
	clocks = <&adpll_isp_ck 1>;
};

&sysclk5_ck {
	clocks = <&adpll_isp_ck 1>;
};

&sysclk6_ck {
	clocks = <&adpll_isp_ck 1>;
};

/*
 * Compared to dm814x, dra62x has different shifts and more mux options.
 * Please add the extra options for ysclk_14 and 16 if really needed.
 */
&timer1_fck {
	clocks = <&sysclk18_ck &aud_clkin0_ck &aud_clkin1_ck
		  &aud_clkin2_ck &devosc_ck &auxosc_ck &tclkin_ck>;
	ti,bit-shift = <4>;
};

&timer2_fck {
	clocks = <&sysclk18_ck &aud_clkin0_ck &aud_clkin1_ck
		  &aud_clkin2_ck &devosc_ck &auxosc_ck &tclkin_ck>;
	ti,bit-shift = <8>;
};

Annotation

• Immediate include surface: `dm814x-clocks.dtsi`.
• Atlas domain: Architecture Layer / arch/arm.
• Implementation status: atlas-only.

Implementation Notes

• This generated page is the file-by-file coverage layer; curated subsystem chapters should link here when they synthesize a multi-file control flow.
• Core OS pages should be promoted from atlas-only to deep-reviewed when they explain data structures, invariants, locking, lifecycle, and C implementation snippets.
• Driver-family pages are intentionally pattern-oriented unless they are part of the selected PCIe/NVMe representative device path.