Documentation/devicetree/bindings/firmware/brcm,kona-smc.yaml
Source file repositories/reference/linux-study-clean/Documentation/devicetree/bindings/firmware/brcm,kona-smc.yaml
File Facts
- System
- Linux kernel
- Corpus path
Documentation/devicetree/bindings/firmware/brcm,kona-smc.yaml- Extension
.yaml- Size
- 801 bytes
- Lines
- 40
- 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/firmware/brcm,kona-smc.yaml#
$schema: http://devicetree.org/meta-schemas/core.yaml#
title: Broadcom Kona family Secure Monitor bounce buffer
description:
A bounce buffer used for non-secure to secure communications.
maintainers:
- Florian Fainelli <f.fainelli@gmail.com>
properties:
compatible:
items:
- enum:
- brcm,bcm11351-smc
- brcm,bcm21664-smc
- brcm,bcm23550-smc
- const: brcm,kona-smc
reg:
maxItems: 1
required:
- compatible
- reg
additionalProperties: false
examples:
- |
smc@3404c000 {
compatible = "brcm,bcm11351-smc", "brcm,kona-smc";
reg = <0x3404c000 0x400>; /* 1 KiB in SRAM */
};
...
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.