Documentation/devicetree/bindings/mailbox/marvell,armada-3700-rwtm-mailbox.yaml

File Facts

System

Linux kernel

Corpus path

Documentation/devicetree/bindings/mailbox/marvell,armada-3700-rwtm-mailbox.yaml

Extension

.yaml

Size

826 bytes

Lines

43

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

• dt-bindings/interrupt-controller/arm-gic.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-only OR BSD-2-Clause)
%YAML 1.2
---
$id: http://devicetree.org/schemas/mailbox/marvell,armada-3700-rwtm-mailbox.yaml#
$schema: http://devicetree.org/meta-schemas/core.yaml#

title: Marvell Armada 3700 rWTM Mailbox

maintainers:
  - Marek Behún <kabel@kernel.org>

properties:
  compatible:
    const: marvell,armada-3700-rwtm-mailbox

  reg:
    maxItems: 1

  interrupts:
    maxItems: 1

  '#mbox-cells':
    const: 1

required:
  - compatible
  - reg
  - interrupts
  - '#mbox-cells'

additionalProperties: false

examples:
  - |
    #include <dt-bindings/interrupt-controller/arm-gic.h>

    mailbox@b0000 {
        compatible = "marvell,armada-3700-rwtm-mailbox";
        reg = <0xb0000 0x100>;
        interrupts = <GIC_SPI 18 IRQ_TYPE_LEVEL_HIGH>;
        #mbox-cells = <1>;
    };

Annotation

• Immediate include surface: `dt-bindings/interrupt-controller/arm-gic.h`.
• 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.