Documentation/devicetree/bindings/arm/intel-ixp4xx.yaml
Source file repositories/reference/linux-study-clean/Documentation/devicetree/bindings/arm/intel-ixp4xx.yaml
File Facts
- System
- Linux kernel
- Corpus path
Documentation/devicetree/bindings/arm/intel-ixp4xx.yaml- Extension
.yaml- Size
- 1125 bytes
- Lines
- 46
- Domain
- Support Tooling And Documentation
- Bucket
- Documentation
- Inferred role
- Support Tooling And Documentation: configuration, schema, or hardware description
- Status
- atlas-only
Why This File Exists
Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.
- Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.
Dependency Surface
- No C-style include directives detected by the generator.
Detected Declarations
- No top-level syscall, struct, function, initcall, or export declaration detected by the generator.
Annotated Snippet
# SPDX-License-Identifier: GPL-2.0
%YAML 1.2
---
$id: http://devicetree.org/schemas/arm/intel-ixp4xx.yaml#
$schema: http://devicetree.org/meta-schemas/core.yaml#
title: Intel IXP4xx
maintainers:
- Linus Walleij <linusw@kernel.org>
properties:
$nodename:
const: "/"
compatible:
oneOf:
- items:
- enum:
- actiontec,mi424wr-ac
- actiontec,mi424wr-d
- adieng,coyote
- arcom,vulcan
- dlink,dsm-g600-a
- freecom,fsg-3
- gateway,7001
- gateworks,gw2348
- goramo,multilink-router
- intel,ixdp425
- intel,ixdpg425
- iom,nas-100d
- linksys,nslu2
- netgear,wg302v1
- netgear,wg302v2
- usr,8200
- welltech,epbx100
- linksys,wrv54g
- gemtek,gtwx5715
- const: intel,ixp42x
- items:
- enum:
- gateworks,gw2358
- intel,kixrp435
- const: intel,ixp43x
additionalProperties: true
Annotation
- Atlas domain: Support Tooling And Documentation / Documentation.
- 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.