summaryrefslogtreecommitdiff
path: root/dts/upstream/Bindings/spi/spi-peripheral-props.yaml
diff options
context:
space:
mode:
Diffstat (limited to 'dts/upstream/Bindings/spi/spi-peripheral-props.yaml')
-rw-r--r--dts/upstream/Bindings/spi/spi-peripheral-props.yaml13
1 files changed, 7 insertions, 6 deletions
diff --git a/dts/upstream/Bindings/spi/spi-peripheral-props.yaml b/dts/upstream/Bindings/spi/spi-peripheral-props.yaml
index 0bb443b8dec..8fc17e16efb 100644
--- a/dts/upstream/Bindings/spi/spi-peripheral-props.yaml
+++ b/dts/upstream/Bindings/spi/spi-peripheral-props.yaml
@@ -8,12 +8,13 @@ title: Peripheral-specific properties for a SPI bus.
description:
Many SPI controllers need to add properties to peripheral devices. They could
- be common properties like spi-max-frequency, spi-cpha, etc. or they could be
- controller specific like delay in clock or data lines, etc. These properties
- need to be defined in the peripheral node because they are per-peripheral and
- there can be multiple peripherals attached to a controller. All those
- properties are listed here. The controller specific properties should go in
- their own separate schema that should be referenced from here.
+ be common properties like spi-max-frequency, spi-cs-high, etc. or they could
+ be controller specific like delay in clock or data lines, etc. These
+ properties need to be defined in the peripheral node because they are
+ per-peripheral and there can be multiple peripherals attached to a
+ controller. All those properties are listed here. The controller specific
+ properties should go in their own separate schema that should be referenced
+ from here.
maintainers:
- Mark Brown <broonie@kernel.org>