Documentation/devicetree/bindings/mmc/mmc-slot.yaml
Source file repositories/reference/linux-study-clean/Documentation/devicetree/bindings/mmc/mmc-slot.yaml
File Facts
- System
- Linux kernel
- Corpus path
Documentation/devicetree/bindings/mmc/mmc-slot.yaml- Extension
.yaml- Size
- 879 bytes
- Lines
- 49
- 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-only OR BSD-2-Clause)
%YAML 1.2
---
$id: http://devicetree.org/schemas/mmc/mmc-slot.yaml#
$schema: http://devicetree.org/meta-schemas/core.yaml#
title: MMC slot properties
maintainers:
- Ulf Hansson <ulf.hansson@linaro.org>
description:
These properties defines slot properties for MMC controlers that
have multiple slots or ports provided by the same controller and
sharing the same resources.
$ref: mmc-controller-common.yaml#
properties:
$nodename:
pattern: "^slot(@.*)?$"
compatible:
const: mmc-slot
reg:
description:
the slot (or "port") ID
maxItems: 1
required:
- reg
unevaluatedProperties: false
examples:
- |
mmc {
#address-cells = <1>;
#size-cells = <0>;
slot@0 {
compatible = "mmc-slot";
reg = <0>;
bus-width = <4>;
};
};
...
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.