Documentation/devicetree/bindings/gpio/st,spear-spics-gpio.yaml
Source file repositories/reference/linux-study-clean/Documentation/devicetree/bindings/gpio/st,spear-spics-gpio.yaml
File Facts
- System
- Linux kernel
- Corpus path
Documentation/devicetree/bindings/gpio/st,spear-spics-gpio.yaml- Extension
.yaml- Size
- 2478 bytes
- Lines
- 83
- 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/gpio/st,spear-spics-gpio.yaml#
$schema: http://devicetree.org/meta-schemas/core.yaml#
title: ST Microelectronics SPEAr SPI CS GPIO Controller
maintainers:
- Viresh Kumar <vireshk@kernel.org>
description: >
SPEAr platform provides a provision to control chipselects of ARM PL022 Prime
Cell spi controller through its system registers, which otherwise remains
under PL022 control. If chipselect remain under PL022 control then they would
be released as soon as transfer is over and TxFIFO becomes empty. This is not
desired by some of the device protocols above spi which expect (multiple)
transfers without releasing their chipselects.
Chipselects can be controlled by software by turning them as GPIOs. SPEAr
provides another interface through system registers through which software can
directly control each PL022 chipselect. Hence, it is natural for SPEAr to
export the control of this interface as gpio.
properties:
compatible:
const: st,spear-spics-gpio
reg:
maxItems: 1
gpio-controller: true
'#gpio-cells':
const: 2
st-spics,peripcfg-reg:
description: Offset of the peripcfg register.
$ref: /schemas/types.yaml#/definitions/uint32
st-spics,sw-enable-bit:
description: Bit offset to enable software chipselect control.
$ref: /schemas/types.yaml#/definitions/uint32
st-spics,cs-value-bit:
description: Bit offset to drive chipselect low or high.
$ref: /schemas/types.yaml#/definitions/uint32
st-spics,cs-enable-mask:
description: Bitmask selecting which chipselects to enable.
$ref: /schemas/types.yaml#/definitions/uint32
st-spics,cs-enable-shift:
description: Bit shift for programming chipselect number.
$ref: /schemas/types.yaml#/definitions/uint32
required:
- compatible
- reg
- gpio-controller
- '#gpio-cells'
- st-spics,peripcfg-reg
- st-spics,sw-enable-bit
- st-spics,cs-value-bit
- st-spics,cs-enable-mask
- st-spics,cs-enable-shift
additionalProperties: false
examples:
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.