arch/arm64/boot/dts/toshiba/tmpv7708-visrobo-vrc.dtsi
Source file repositories/reference/linux-study-clean/arch/arm64/boot/dts/toshiba/tmpv7708-visrobo-vrc.dtsi
File Facts
- System
- Linux kernel
- Corpus path
arch/arm64/boot/dts/toshiba/tmpv7708-visrobo-vrc.dtsi- Extension
.dtsi- Size
- 639 bytes
- Lines
- 41
- 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
tmpv7708.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)
/*
* Device Tree File for TMPV7708 VisROBO VRC SoM
*
* (C) Copyright 2020, 2021, Toshiba Corporation.
* (C) Copyright 2020, Nobuhiro Iwamatsu <nobuhiro1.iwamatsu@toshiba.co.jp>
*/
/dts-v1/;
#include "tmpv7708.dtsi"
#include <dt-bindings/gpio/gpio.h>
&wdt {
status = "okay";
};
&gpio {
status = "okay";
};
&spi0_pins {
groups = "spi0_grp", "spi0_cs0_grp";
};
&spi0 {
status = "okay";
mmc@0 {
compatible = "mmc-spi-slot";
reg = <0>;
gpios = <&gpio 15 GPIO_ACTIVE_LOW>;
voltage-ranges = <3200 3400>;
spi-max-frequency = <12000000>;
};
};
&i2c0 {
status = "okay";
};
Annotation
- Immediate include surface: `tmpv7708.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.