Documentation/devicetree/bindings/sound/linux,bt-sco.yaml

File Facts

System

Linux kernel

Corpus path

Documentation/devicetree/bindings/sound/linux,bt-sco.yaml

Extension

.yaml

Size

633 bytes

Lines

42

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/sound/linux,bt-sco.yaml#
$schema: http://devicetree.org/meta-schemas/core.yaml#

title: Bluetooth SCO Audio Codec

maintainers:
  - Mark Brown <broonie@kernel.org>

allOf:
  - $ref: dai-common.yaml#

properties:
  '#sound-dai-cells':
    enum:
      - 0

      # For Wideband PCM
      - 1

  compatible:
    enum:
      - delta,dfbmcs320
      - linux,bt-sco

required:
  - '#sound-dai-cells'
  - compatible

unevaluatedProperties: false

examples:
  - |
    codec {
        #sound-dai-cells = <0>;
        compatible = "linux,bt-sco";
    };

...

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.