arch/arm/boot/dts/ti/omap/omap3-gta04a3.dts
Source file repositories/reference/linux-study-clean/arch/arm/boot/dts/ti/omap/omap3-gta04a3.dts
File Facts
- System
- Linux kernel
- Corpus path
arch/arm/boot/dts/ti/omap/omap3-gta04a3.dts- Extension
.dts- Size
- 990 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
omap3-gta04.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
/*
* Copyright (C) 2014 H. Nikolaus Schaller <hns@goldelico.com>
*/
#include "omap3-gta04.dtsi"
/ {
model = "Goldelico GTA04A3/Letux 2804";
};
&i2c2 {
/* alternate accelerometer that might be installed on some GTA04A3 boards */
lis302@1d {
compatible = "st,lis331dlh", "st,lis3lv02d";
reg = <0x1d>;
interrupt-parent = <&gpio3>;
interrupts = <18 (IRQ_TYPE_LEVEL_HIGH | IRQ_TYPE_EDGE_RISING)>;
Vdd-supply = <&vaux2>;
Vdd_IO-supply = <&vaux2>;
st,click-single-x;
st,click-single-y;
st,click-single-z;
st,click-thresh-x = <8>;
st,click-thresh-y = <8>;
st,click-thresh-z = <10>;
st,click-click-time-limit = <9>;
st,click-latency = <50>;
st,irq1-click;
st,wakeup-x-lo;
st,wakeup-x-hi;
st,wakeup-y-lo;
st,wakeup-y-hi;
st,wakeup-z-lo;
st,wakeup-z-hi;
st,min-limit-x = <32>;
st,min-limit-y = <3>;
st,min-limit-z = <3>;
st,max-limit-x = <3>;
st,max-limit-y = <32>;
st,max-limit-z = <32>;
};
};
Annotation
- Immediate include surface: `omap3-gta04.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.