arch/arm64/boot/dts/qcom/msm8916-thwc-ufi001c.dts
Source file repositories/reference/linux-study-clean/arch/arm64/boot/dts/qcom/msm8916-thwc-ufi001c.dts
File Facts
- System
- Linux kernel
- Corpus path
arch/arm64/boot/dts/qcom/msm8916-thwc-ufi001c.dts- Extension
.dts- Size
- 1001 bytes
- Lines
- 67
- 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
msm8916-ufi.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
/dts-v1/;
#include "msm8916-ufi.dtsi"
/ {
model = "ufi-001c/ufi-001b 4G Modem Stick";
compatible = "thwc,ufi001c", "qcom,msm8916";
};
&button_restart {
gpios = <&tlmm 37 GPIO_ACTIVE_HIGH>;
};
&led_b {
gpios = <&tlmm 20 GPIO_ACTIVE_HIGH>;
};
&led_g {
gpios = <&tlmm 21 GPIO_ACTIVE_HIGH>;
};
&led_r {
gpios = <&tlmm 22 GPIO_ACTIVE_HIGH>;
};
&mpss {
pinctrl-0 = <&sim_ctrl_default>;
pinctrl-names = "default";
};
&button_default {
pins = "gpio37";
bias-pull-down;
};
&gpio_leds_default {
pins = "gpio20", "gpio21", "gpio22";
};
/* This selects the external SIM card slot by default */
&tlmm {
sim_ctrl_default: sim-ctrl-default-state {
esim-sel-pins {
pins = "gpio0", "gpio3";
function = "gpio";
bias-disable;
output-low;
};
sim-en-pins {
pins = "gpio1";
function = "gpio";
bias-disable;
output-low;
};
sim-sel-pins {
pins = "gpio2";
function = "gpio";
bias-disable;
output-high;
};
};
};
Annotation
- Immediate include surface: `msm8916-ufi.dtsi`.
- 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.