arch/arm64/boot/dts/qcom/msm8916-samsung-rossa-common.dtsi
Source file repositories/reference/linux-study-clean/arch/arm64/boot/dts/qcom/msm8916-samsung-rossa-common.dtsi
File Facts
- System
- Linux kernel
- Corpus path
arch/arm64/boot/dts/qcom/msm8916-samsung-rossa-common.dtsi- Extension
.dtsi- Size
- 881 bytes
- Lines
- 48
- 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-samsung-fortuna-common.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 "msm8916-samsung-fortuna-common.dtsi"
/* IST3038 instead of Zinitix BT541 */
/delete-node/ &touchscreen;
&blsp_i2c5 {
touchscreen: touchscreen@50 {
compatible = "imagis,ist3038";
reg = <0x50>;
interrupts-extended = <&tlmm 13 IRQ_TYPE_EDGE_FALLING>;
touchscreen-size-x = <480>;
touchscreen-size-y = <800>;
vdd-supply = <®_vdd_tsp_a>;
vddio-supply = <&pm8916_l6>;
pinctrl-0 = <&tsp_int_default>;
pinctrl-names = "default";
linux,keycodes = <KEY_APPSELECT KEY_BACK>;
};
};
/* On rossa backlight is controlled with MIPI DCS commands */
&clk_pwm {
status = "disabled";
};
&clk_pwm_backlight {
status = "disabled";
};
&s3fwrn5_nfc {
status = "okay";
};
&st_accel {
compatible = "st,lis2hh12";
mount-matrix = "1", "0", "0",
"0", "-1", "0",
"0", "0", "1";
status = "okay";
};
Annotation
- Immediate include surface: `msm8916-samsung-fortuna-common.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.