arch/arm64/boot/dts/mediatek/mt8186-corsola-krabby.dtsi
Source file repositories/reference/linux-study-clean/arch/arm64/boot/dts/mediatek/mt8186-corsola-krabby.dtsi
File Facts
- System
- Linux kernel
- Corpus path
arch/arm64/boot/dts/mediatek/mt8186-corsola-krabby.dtsi- Extension
.dtsi- Size
- 2303 bytes
- Lines
- 130
- 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
mt8186-corsola.dtsidt-bindings/gpio/gpio.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 2022 Google LLC
*/
/dts-v1/;
#include "mt8186-corsola.dtsi"
#include <dt-bindings/gpio/gpio.h>
/ {
aliases {
i2c4 = &i2c4;
};
};
&dsi_out {
remote-endpoint = <&ps8640_in>;
};
&i2c0 {
clock-frequency = <400000>;
edp-bridge@8 {
compatible = "parade,ps8640";
reg = <0x8>;
pinctrl-names = "default";
pinctrl-0 = <&ps8640_pins>;
powerdown-gpios = <&pio 96 GPIO_ACTIVE_LOW>;
reset-gpios = <&pio 98 GPIO_ACTIVE_LOW>;
vdd12-supply = <&mt6366_vrf12_reg>;
vdd33-supply = <&mt6366_vcn33_reg>;
ports {
#address-cells = <1>;
#size-cells = <0>;
port@0 {
reg = <0>;
ps8640_in: endpoint {
remote-endpoint = <&dsi_out>;
};
};
port@1 {
reg = <1>;
ps8640_out: endpoint {
remote-endpoint = <&panel_in>;
};
};
};
aux-bus {
panel {
compatible = "edp-panel";
power-supply = <&pp3300_disp_x>;
backlight = <&backlight_lcd0>;
port {
panel_in: endpoint {
remote-endpoint = <&ps8640_out>;
};
};
};
};
};
};
&i2c1 {
Annotation
- Immediate include surface: `mt8186-corsola.dtsi`, `dt-bindings/gpio/gpio.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.