Documentation/devicetree/bindings/power/supply/x-powers,axp20x-ac-power-supply.yaml

File Facts

System

Linux kernel

Corpus path

Documentation/devicetree/bindings/power/supply/x-powers,axp20x-ac-power-supply.yaml

Extension

.yaml

Size

967 bytes

Lines

36

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/power/supply/x-powers,axp20x-ac-power-supply.yaml#
$schema: http://devicetree.org/meta-schemas/core.yaml#

title: AXP20x AC power-supply

description: |
  The AXP20X can read the current current and voltage supplied by AC by
  reading ADC channels from the AXP20X ADC. The AXP22X is only able to
  tell if an AC power supply is present and usable. AXP813/AXP803 are
  able to limit current and supply voltage

maintainers:
  - Chen-Yu Tsai <wens@csie.org>
  - Sebastian Reichel <sre@kernel.org>

allOf:
  - $ref: power-supply.yaml#

properties:
  compatible:
    oneOf:
      - const: x-powers,axp202-ac-power-supply
      - const: x-powers,axp221-ac-power-supply
      - items:
          - const: x-powers,axp803-ac-power-supply
          - const: x-powers,axp813-ac-power-supply
      - const: x-powers,axp813-ac-power-supply

required:
  - compatible

additionalProperties: false

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.