arch/arm64/boot/dts/freescale/imx8mp-dhcom-overlay-panel-clock.dtsi
Source file repositories/reference/linux-study-clean/arch/arm64/boot/dts/freescale/imx8mp-dhcom-overlay-panel-clock.dtsi
File Facts
- System
- Linux kernel
- Corpus path
arch/arm64/boot/dts/freescale/imx8mp-dhcom-overlay-panel-clock.dtsi- Extension
.dtsi- Size
- 947 bytes
- Lines
- 34
- Domain
- Architecture Layer
- Bucket
- arch/arm64
- 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
dt-bindings/clock/imx8mp-clock.h
Detected Declarations
- No top-level syscall, struct, function, initcall, or export declaration detected by the generator.
Annotated Snippet
// SPDX-License-Identifier: (GPL-2.0+ OR MIT)
/*
* Copyright (C) 2024-2026 Marek Vasut
*/
#include <dt-bindings/clock/imx8mp-clock.h>
&media_blk_ctrl {
/*
* Sys PLL3 supplies TC9595 RefClk
* Audio PLL2 supplies MEDIA_DISP1_PIX (DSI)
* Video PLL1 supplies MEDIA_DISP2_PIX (LVDS)
*/
assigned-clocks = <&clk IMX8MP_CLK_MEDIA_AXI>,
<&clk IMX8MP_CLK_MEDIA_APB>,
<&clk IMX8MP_CLK_MEDIA_DISP1_PIX>,
<&clk IMX8MP_CLK_MEDIA_DISP2_PIX>,
<&clk IMX8MP_AUDIO_PLL2>,
<&clk IMX8MP_VIDEO_PLL1>;
assigned-clock-parents = <&clk IMX8MP_SYS_PLL2_1000M>,
<&clk IMX8MP_SYS_PLL1_800M>,
<&clk IMX8MP_AUDIO_PLL2_OUT>,
<&clk IMX8MP_VIDEO_PLL1_OUT>;
assigned-clock-rates = <500000000>, <200000000>,
<0>, <0>, <0>, <0>;
};
&tc_bridge {
assigned-clocks = <&clk IMX8MP_CLK_CLKOUT2_SEL>,
<&clk IMX8MP_CLK_CLKOUT2>,
<&clk IMX8MP_SYS_PLL3_OUT>;
assigned-clock-parents = <&clk IMX8MP_SYS_PLL3_OUT>;
};
Annotation
- Immediate include surface: `dt-bindings/clock/imx8mp-clock.h`.
- Atlas domain: Architecture Layer / arch/arm64.
- 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.