arch/arm/boot/dts/ti/omap/motorola-mapphone-mz607-mz617.dtsi
Source file repositories/reference/linux-study-clean/arch/arm/boot/dts/ti/omap/motorola-mapphone-mz607-mz617.dtsi
File Facts
- System
- Linux kernel
- Corpus path
arch/arm/boot/dts/ti/omap/motorola-mapphone-mz607-mz617.dtsi- Extension
.dtsi- Size
- 529 bytes
- Lines
- 22
- 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
motorola-mapphone-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
/dts-v1/;
#include "motorola-mapphone-common.dtsi"
&keypad {
keypad,num-rows = <8>;
keypad,num-columns = <8>;
linux,keymap = <MATRIX_KEY(5, 0, KEY_VOLUMEUP)>,
<MATRIX_KEY(3, 0, KEY_VOLUMEDOWN)>;
};
/*
* On tablets, mmc1 regulator is vsimcard instead of vwlan2 in the stock kernel
* dtb. The regulator may not be wired even if a MMC cage is added though.
*/
&mmc1 {
vmmc-supply = <&vsimcard>;
bus-width = <4>;
cd-gpios = <&gpio6 16 GPIO_ACTIVE_LOW>; /* gpio_176 */
};
Annotation
- Immediate include surface: `motorola-mapphone-common.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.